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:
new: {'python3-debconf': '1.5.65', 'libnss-systemd:amd64': '235-3ubuntu2',
'linux-headers-4.13.0-17-generic': '4.13.0-17.20', 'libharfbuzz0b:amd64':
'1.7.2-1', 'libicu-le-hb0:amd64': '1.0.3+git161113-4', 'libntfs-3g88':
'1:2017.3.23-2', 'linux-headers-4.13.0-17': '4.13.0-17.20',
'libgraphite2-3:amd64': '1.3.10-8'}
removed: {'linux-headers-4.13.0-16-generic': '4.13.0-16.19', 'libntfs-3g872':
'1:2016.2.22AR.2-2', 'linux-headers-4.13.0-16': '4.13.0-16.19'}
changed: ['apport', 'bsdutils', 'busybox-initramfs', 'busybox-static', 'byobu',
'cloud-init', 'cpio', 'debconf', 'debconf-i18n', 'fdisk', 'gcc-7-base:amd64',
'gdisk', 'grub-common', 'grub-legacy-ec2', 'grub-pc', 'grub-pc-bin',
'grub2-common', 'iproute2', 'less', 'libassuan0:amd64', 'libblkid1:amd64',
'libcap2-bin', 'libcap2:amd64', 'libexpat1:amd64', 'libfdisk1:amd64',
'libgcc1:amd64', 'libicu60:amd64', 'libmount1:amd64', 'libpam-cap:amd64',
'libpam-systemd:amd64', 'libpcre3:amd64', 'libperl5.26:amd64', 'libpsl5:amd64',
'libpython3.6-minimal:amd64', 'libpython3.6-stdlib:amd64',
'libpython3.6:amd64', 'libsmartcols1:amd64', 'libssl1.0.0:amd64',
'libstdc++6:amd64', 'libsystemd0:amd64', 'libudev1:amd64', 'libuuid1:amd64',
'linux-headers-generic', 'linux-headers-virtual',
'linux-image-4.13.0-17-generic', 'linux-image-virtual', 'linux-virtual',
'man-db', 'mount', 'nano', 'netcat-openbsd', 'ntfs-3g', 'openssl', 'perl',
'perl-base', 'perl-modules-5.26', 'python3-apport', 'python3-gi',
'python3-problem-report', 'python3.6', 'python3.6-minimal', 'snapd',
'sosreport', 'sudo', 'systemd', 'systemd-sysv', 'udev', 'util-linux',
'uuid-runtime', 'xauth']
Could you try bisecting with the interim serials to see if we can get a
slightly smaller list of packages to consider?
--
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:
Cloud-init seems not run on today's bionic images (20171211)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1737704/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
