The fix for bug 1731868 left a interim change in ds-identify referencing
an undeclared variable.
That code path would be hit if you attached an ISO filesystem to a device other
than a cdrom.
For example:
qemu-system-x86_64 -enable-kvm \
-device virtio-net-pci,netdev=net00 \
-netdev type=user
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737704
Title:
smoser was able to reproduce (without uvt btw) and found up to 20171208 working.
The manifest diff then is much smaller.
Essentially:
+cloud-init 17.1-53-ga5dc0f42-0ubuntu1
+grub-legacy-ec217.1-53-ga5dc0f42-0ubuntu1
+libassuan0:amd64 2.5.1-1
Of those only the first seems related
The testing we perform before a daily makes it out in to the world
includes some basic cloud-init validation (basically "touch /some/file"
in user-data, and checking that happened after boot), so it isn't
failing in all cases.
Diffing the two manifests gives a pretty substantial set of changes:
n
** Also affects: cloud-init
Importance: Undecided
Status: New
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737704
Since I can't log into the guest due to the lack of proper init in the
bad case I copied and mounted both daily images to check how they start
fresh.
I see different cloud-init versions:
good: 17.1-41-g76243487-0ubuntu1
bad: 17.1-53-ga5dc0f42-0ubuntu1
I see status and clean commands got added, bu
