Hello Nick, and thank you for your feedback. > * This is a hardware enablement SRU.
The debsums test is a cert-blocker the in Desktop Certification Suite. Any machine that would require a certification run on noble will get encounter this problem. My particular situation is enabling Nvidia N1X-based machines, the first one being named Spark https://www.nvidia.com/en-us/products/workstations/dgx-spark/ About the changes, I assumed that running `debsums -c` would be a 100% sure way to confirm that the cloud-init.service file has the expected lines in it. As for if this "expected state" actually is a functionnal one, I can say that - The test plan covers an autoinstall configuration to make sure it works correctly. That should cover the conditions you mentioned. If you'd like that, I can also add in the test plan a test with cloud-init disabled. - The server image, who is not impacted by this bug, already has this "expected state", and works correctly. Unfortunately I am not familiar enough with livecd-rootfs codebase to give you more confidence. I hope that @Dan knows a bit more, since he was involved in the original fix in Oracular? (and also can confirm or precise what I just said?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069391 Title: debsums reports file changed /usr/lib/systemd/system/cloud- init.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2069391/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
