I updated bug the description to mention bug 1725067 which was a
regression that is shown with the recreate above.
** Description changed:
=== Begin SRU Template ===
[Impact]
Growing the root partition would fail in either of two cases:
a.) if the device /dev/root existed
- This
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
for xenial you need to download the '-uefi1.img' in order to get
a disk that is partitioned with a GPT table.
Given a small modification to get-proposed-cloudimg:
--- get-proposed-cloudimg.dist 2017-05-16 13:56:05.0 +
+++ get-proposed-cloudimg 2017-05-16 13:52:49.192688492
Validated yakkety and zesty:
$ raw=yakkety-server-cloudimg-amd64.raw
$ yakkety-server-cloudimg-amd64.raw
yakkety-server-cloudimg-amd64.raw: command not found
$ sfdisk --part-uuid $raw 1
F9E1FDF2-234A-4732-AEF8-A75B86313FAD
$ ptuuid=$(sfdisk --part-uuid $raw 1)
$ ptuuid=$(echo "$ptuuid" | tr
Hello Scott, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello Scott, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
The test case now explicitly uses upper case uuids, so we are testing
that part of the fix on xenial. The /dev/root fix will be tested for
yakkety only (though it will also ultimately benefit xenial users w/ the
rolling kernel).
** Changed in: cloud-init (Ubuntu Xenial)
Status: Incomplete
** Description changed:
=== Begin SRU Template ===
[Impact]
Growing the root partition would fail in either of two cases:
a.) if the device /dev/root existed
+ This occurs on yakkety systems.
+
b.) the kernel command line had upper case letters in PARTUUID=
+ This can be
** Description changed:
=== Begin SRU Template ===
[Impact]
Growing the root partition would fail in either of two cases:
a.) if the device /dev/root existed
b.) the kernel command line had upper case letters in PARTUUID=
[Test Case]
get-proposed-image is
I don't think this is a correct test case for xenial; since the standard
kvm images use the release kernel, which is 4.4, rather than the hwe-
rolling kernel (4.8), the behavior will match the other 4.4-based image
I already tested. We need a test case that will actually fail with the
current
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided =>
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Artful)
Importance: Medium
Status: Fix Released
** Also affects:
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- nova-lxd: read product_name from environment, not platform.
(LP: #1685810)
- Fix yum repo config
** Description changed:
=== Begin SRU Template ===
[Impact]
Growing the root partition would fail in either of two cases:
a.) if the device /dev/root existed
b.) the kernel command line had upper case letters in PARTUUID=
[Test Case]
get-proposed-image is
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/322875
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684869
Title:
growing root partition does not
** Description changed:
+ http://pad.lv/1684869
+ https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1684869
+
+ === Begin SRU Template ===
+ [Impact]
+ Growing the root partition would fail in either of two cases:
+ a.) if the device /dev/root existed
+ b.) the kernel command line
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Confirmed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
20 matches
Mail list logo
