a) non-dracut
> * Upstream bug fix and additional testing on Noble to ensure there isn't
> regression potential if this
> were released to non-dracut images
> https://github.com/canonical/cloud-init/pull/6921
I think resolute can still be configured to use the previous non-dracut
initial ramdisk, so I think the test plan should cover that as well to
make sure we didn't regress that method.
b) stonking?
I quickly checked the release in stonking, and it seems to have the same fix.
Could you please confirm and change the stonking task accordingly, if it's
indeed fixed?
** Also affects: cloud-init (Ubuntu Stonking)
Importance: High
Status: In Progress
** Also affects: cloud-init (Ubuntu Resolute)
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/2161665
Title:
resolute: Oracle 100 minute boot/reboot delay due to ISCSI root not
detected on dracut-based images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2161665/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
