This bug is awaiting verification that the linux-intel/6.14.0-1008.8 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-plucky-linux-intel' to 'verification-done- plucky-linux-intel'. If the problem still exists, change the tag 'verification-needed-plucky-linux-intel' to 'verification-failed-plucky- linux-intel'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-plucky-linux-intel-v2 verification-needed-plucky-linux-intel -- 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: Fix Committed Status in linux-base source package in Jammy: Invalid Status in linux-meta source package in Jammy: Fix Committed Status in linux-base source package in Noble: Invalid Status in linux-meta source package in Noble: Fix Committed Status in linux-base source package in Plucky: Invalid Status in linux-meta source package in Plucky: Fix Committed Bug description: SRU Justification: [Impact] 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 seems to affect both minimal cloud images as well as generic arm64 kernels. [Fix] Enable the SYM53C8XX_2 driver in generic arm64 kernels. This allows the drive to be successfully mounted. [Test Plan] To reproduce: register and launch an arm64 minimal cloud image in openstack configured to use a block disk bus and verify that cloud init can mount the config drive. ---------- (original bug description below) 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 : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
