This is behavior that wasn't noticed until cloud-init changed to prevent falling back to a openstacklocal datasource in environments where config_drive was passed.
Block configurations could never mount the config drive, but they used to fall back to the other datasource. With the new cloud-init, they can't do that -- they need to be able to mount the config drive. Thus the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2118499 Title: minimal kernel lacks modules for blk disk in arm64 openstack environments where config_drive is required Status in linux-base package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Incomplete Bug description: Cloud images using the arm64 minimal kernel cannot detect config drive cloud-init datasources in openstack. This seems to be due to openstack environments using or emulating a sym53c8xx scsi controller for the config drive. This doesn't work for initrd-less boot, as in the case of minimal cloud images. To reproduce: register and launch an arm64 minimal questing cloud image [1] in openstack configured to use a block disk bus and verify that cloud init cannot mount the config drive. 1. https://cloud-images.ubuntu.com/minimal/daily/questing/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/2118499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
