[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
block-proposed-noble tag removed now as the other Noble livecd-rootfs bugs have been fix-released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
@sdeziel exactly yes. We will try get the other livecd-rootfs Noble bugs released now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
** Tags removed: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
I have verified again - using livecd-rootfs 24.04.72 which is currently in -proposed. I built test image on launchpad and created a VM in Hyper-V manager. I went through oem-config, the desktop environment started. I could update and install package. The machine also rebooted successfully. Marking as verification-done. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
From ubuntu-server daily live image build 20240628 @ https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/20240628/ with amd64 build @ https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/642557 with these changes and I can confirm: * from the build log that 24.04.72 was used. * from the log @ that `/usr/local/sbin/unminimize` is now being called in `01-unminimize.chroot_early` as expected. * Build was successful * Ubuntu Server (minimized) install of server resulted in the following test results https://pastebin.ubuntu.com/p/CF783fb7H9/ * Ubuntu Server install of server resulted in the following test results https://pastebin.ubuntu.com/p/ztwHFR2Ysf/ * LXD is not preseeded. * Layers/install targets are as expected with recommends packages only present in the non minimized install. Marking verified. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069828] Re: Revert removal of unminimize call in server builds
From ubuntu-server daily live image build 20240628 @ https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/20240628/ with amd64 build @ https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/ubuntu-server-live/+build/642557 with these changes and I can confirm: * from the build log that 24.04.72 was used. * from the log @ that `/usr/local/sbin/unminimize` is now being called in `01-unminimize.chroot_early` as expected. * Build was successful * Ubuntu Server (minimized) install of server resulted in the following test results https://pastebin.ubuntu.com/p/CF783fb7H9/ * Ubuntu Server install of server resulted in the following test results https://pastebin.ubuntu.com/p/ztwHFR2Ysf/ * LXD is not preseeded. * Layers/install targets are as expected with recommends packages only present in the non minimized install. Marking verified. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069828 Title: Revert removal of unminimize call in server builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063203] Re: Build ubuntu-core-desktop images
Based on vorlon's comments above and so as not to delay SRU I am marking this as verified ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063203 Title: Build ubuntu-core-desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
LP: #2069828 (https://bugs.launchpad.net/ubuntu/+source/livecd- rootfs/+bug/2069828) was created to track the regression. The fix to LP: #2069828 is now in version 24.04.72 which is now in -proposed and will be verified. As such I am removing `block-proposed-noble` tag as lack of verification of 24.04.72 will block. ** Tags removed: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
I have marked Oracular "Invalid" as this is specific to the releases prior to Noble where preseeding of LXD was still supported ** Changed in: livecd-rootfs (Ubuntu Oracular) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
I have marked Oracular "Invalid" as this is specific to the 6.5 which is not available in oracular ** Changed in: livecd-rootfs (Ubuntu Oracular) Status: New => Won't Fix ** Changed in: livecd-rootfs (Ubuntu Oracular) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Mantic) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Jammy) Assignee: (unassigned) => Ankush Pathak (ankushpathak) ** Changed in: livecd-rootfs (Ubuntu Mantic) Assignee: (unassigned) => Ankush Pathak (ankushpathak) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069828] Re: Revert removal of unminimize call in server builds
** Summary changed: - Revert removal of yes /usr/local/sbin/unminimize call in server builds + Revert removal of unminimize call in server builds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069828 Title: Revert removal of unminimize call in server builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069828] [NEW] Revert removal of yes /usr/local/sbin/unminimize call in server builds
Public bug reported: There was a change made by me in https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/466388 as part of LP: #2066905 to remove references to LXD in the unminimize scripts but I also removed the calls to `unminimize` in error. This still needs to run but without any references to LXD which no longer needs to be `unminimized` via snap installation. [ Impact ] The server images no longer have a non minimized layer as it is never unminimized. [ Test Plan ] * Successfully build server daily image and ensure that the multiple layers are present. [ Where problems could occur ] * If the server image does not build, if LXD snap continues to be installed or if the unminimized layer is not as expected. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Oracular) 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/2069828 Title: Revert removal of yes /usr/local/sbin/unminimize call in server builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
Adding `block-proposed-noble` tag as the changes in https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/466388 actually remove all of unminimize calls - not just the lxd specific changes. I will create bug to track this. ** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
I have created a test noble minimal cloud image with the -proposed livecd-rootfs 24.04.71 and also successfully confirmed that `unminimize` no longer attempts to install the LXD snap. I built the cloud image in launchpad and tested using qemu. Marking as verification-done ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063203] Re: Build ubuntu-core-desktop images
Based on vorlon's comments above and so as not to delay SRU I am marking this as verified ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063203 Title: Build ubuntu-core-desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following shim 15.8 update
** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: cloud-images Assignee: (unassigned) => Gauthier Jolly (gjolly) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following shim 15.8 update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
Now in noble unapproved queue https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
Now in noble unapproved queue https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066903] Re: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize
** Description changed: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble + + [ Impact ] + + Attempting to install LXD snap on unminimize when this is no longer + required. + + [ Test Plan ] + + * Build cloud minimal image and confirm unminimize does not install LXD + snap + + [ Where problems could occur ] + + * If LXD snap continues to be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066903 Title: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unminimize/+bug/2066903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
** Description changed: The LXD snap is no longer seeded in any images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live- build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble [ Impact ] Attempting to install LXD snap on unminimize when this is no longer required. Due to how daily server image builds upgrade to packages from -proposed this is also causing server image build failures - see https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017 - [ Test Plan ] - * Successfully build server daily image - * Build cloud minimal image and confirm unminimize does not install LXD snap - + * Successfully build server daily image + * Build cloud minimal image and confirm unminimize does not install LXD snap [ Where problems could occur ] - * If the server image built does not build or if LXD snap continues to - be seeded + * If the server image built does not build or if LXD snap continues to + be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
** Description changed: The LXD snap is no longer seeded in any images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live- build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble + + [ Impact ] + + Attempting to install LXD snap on unminimize when this is no longer + required. + + Due to how daily server image builds upgrade to packages from -proposed + this is also causing server image build failures - see + https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017 + + + [ Test Plan ] + + * Successfully build server daily image + * Build cloud minimal image and confirm unminimize does not install LXD snap + + + [ Where problems could occur ] + + * If the server image built does not build or if LXD snap continues to + be seeded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
For context the image @jibel tested was https://partner- images.canonical.com/hyper-v/desktop/oracular/20240522/ @jibel I will start SRU to noble now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] [NEW] LXD snap no longer seeded in non any images so does not need special handling in unminimize logic
Public bug reported: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic in https://git.launchpad.net/livecd- rootfs/tree/live-build/auto/build?h=ubuntu/noble#n290 and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - LXD snap no longer seeded in non minimal images so does not need special handling in unminimize logic + LXD snap no longer seeded in non any images so does not need special handling in unminimize logic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066905 Title: LXD snap no longer seeded in non any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066903] [NEW] Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize
Public bug reported: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. This applies for Noble+ so requires SRU back to Noble ** Affects: unminimize (Ubuntu) Importance: Undecided Status: New ** Affects: unminimize (Ubuntu Noble) Importance: Undecided Status: New ** Affects: unminimize (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: unminimize (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: unminimize (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: The LXD snap is no longer seeded in non minimal images since Noble+ so the unminimize logic related to LXD snap @ https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108 is no longer required. lxd-installer can remain installed. + + This applies for Noble+ so requires SRU back to Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066903 Title: Noble+ no longer seed LXD snap so this does not need to be installed when running unminimize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unminimize/+bug/2066903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
@sdeziel thank you for debugging. +1 on moving to `/usr/sbin/lxd` instead of `/sbin/lxd` if possible thus removing the need for any livecd-rootfs changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
Jammy livecd-rootfs 2.765.42 has now been uploaded to SRU queue @ https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Re: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel
Mantic livecd-rootfs 23.10.60 has now been uploaded to SRU queue @ https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
Full failing build log @ https://launchpadlibrarian.net/731241044/buildlog_ubuntu_noble_amd64_ubuntu- server-live_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed
The changes proposed here in Noble lxd-installer 4ubuntu0.1 have caused server builds to fail ``` Invoking LXD so that it can be installed by the lxd-installer's script.. Unable to trigger the installation of the LXD snap. Please make sure you're a member of the 'lxd' system group. ``` This is being triggered during build @ https://git.launchpad.net/livecd- rootfs/tree/live-build/auto/build?h=ubuntu/noble#n291 I have added `block-proposed-noble` to this bug until resolved. ** Tags added: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061017 Title: lxd-installer: permission error not handled and lxd snap not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
** Changed in: livecd-rootfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] Re: Please update the package to 20240320.00
The xenial and bionic target is the ESM repos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] [NEW] Please update the package to 20240320.00
Public bug reported: Following on from previous similar package update requests @ LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update the google-osconfig-agent to the upstream version `20240320.00` @ https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20240320.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#google-osconfig-agent including an ageing exception detailed @ https://wiki.ubuntu.com/google- osconfig-agent-Updates There is some urgency in landing these changes to accommodate planned infrastructure changes on the Google Compute Platform. [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/google-osconfig-agent-Updates The updated package is not built for armhf and riscv64 due to upstream regressions but the package is not used on those architectures thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is OK since it is not used on powerpc either. ** Affects: google-osconfig-agent (Ubuntu) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Focal) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Noble) Importance: Undecided Status: New ** Affects: google-osconfig-agent (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: google-osconfig-agent (Ubuntu Mantic) 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/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] [NEW] Hyperv desktop images no longer building in Noble
Public bug reported: We have not built Hyperv desktop images since Jammy and with the re- introduction of HyperV for Noble we have encountered build issues caused by refactoring and removals of code assumed to be redundant but the HyperV desktop images were actually using these code paths. In bbedffe6 we split the building of cloud images and non cloud to using an ddisk-image-uefi.binary and disk-image-uefi-non-cloud.binary respectively. In e38264ca there was a change which meant that any attempt to build hyperv images would result in incorrect disk size and incorrect disk label. A change in 76d79466 changed the logic of how the image size for amd64 images were being set. This overrode the sizes set for the desktop images incorrectly. A change in 8fb21808 also removed many of the dependencies that the hyperv images require. This removal has been restored in this commit by adding them expliciltly in the hyperv hook. With Ubutnu 24.04+ cloud-init was introduced to desktop images. This is not required for HyperV images and can be disabled. This bug is to track the work to restore functioning Hyperv desktop image builds [ Impact ] Unable to build HyperV Desktop image. [ Test Plan ] * Successfully build image * Launch through Windows HyperV manager successfully without any errors or warning. [ Where problems could occur ] * If the image built does not launch in hyperv manager or has errors or warnings. [ Other Info ] * There is work required to migrate oem-config to the new provisioning stack but this is out of scope of this bug. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Assignee: Philip Roche (philroche) Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
Verification done for Mantic now. * Successfully built image with LXD preseeded with these changes * confirmed LXD is preseeded/installed and works as expected. * Confirmed that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic ** Also affects: livecd-rootfs (Ubuntu Oracular) 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/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
This issue affects Oracular/24.10 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063442] [NEW] needrestart on Ubuntu 24.04 is restarting google-guest-agent startup and shutdown scrips on reinstall but they should not be restarted
Public bug reported:
The recent change in Ubuntu 24.04 and needrestart which results in
services being restarted automatically , details @
https://discourse.ubuntu.com/t/noble-numbat-release-
notes/39890#services-restart-on-unattended-upgrade-26, has resulted in
unexpected behaviour on Google GCE ubuntu 24.04 images where if the
google-guest-agent package is reinstalled then needrestart will restart
the `google-startup-scripts.service` and `google-shutdown-
scripts.service` but these should only be run during the lifetime of the
instance and should not be restarted.
It can be worked around by setting `NEEDRESTART_SUSPEND=1` prior to any
re-install as per the needrestart man pages @
https://manpages.ubuntu.com/manpages/noble/man1/needrestart.1.html?&_ga=2.32620542.1557010342.1713949275-1490161839.1713949275#environment
or by appending to the needrestart configuration `echo
"\$nrconf{override_rc}{qr(^google-(shutdown|startup)-scripts\.service$)}
= 0;" >> /etc/needrestart/conf.d/google-guest-agent.conf` which will
disable this behaviour for any future google-guest-agent upgrade or
reinstall.
This bug is to track the work of getting this added to the packaged
`/etc/needrestart/needrestart.conf` configuration.
Similar to the work done for cloud-init @
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2059337
** Affects: needrestart (Ubuntu)
Importance: Undecided
Status: New
** Affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Noble)
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/2063442
Title:
needrestart on Ubuntu 24.04 is restarting google-guest-agent startup
and shutdown scrips on reinstall but they should not be restarted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2063442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE
** Also affects: linux-gcp (Ubuntu Noble) 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/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features
** Changed in: snapd (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-gcp (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-ibm (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-oracle (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following snapd 2.62 update
I have removed references to desktop FDE from the description. Thank you for testing. ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - There are reports that this is affecting desktop TPM backed FDE too. + ~~ There are reports that this is affecting desktop TPM backed FDE too. + ~~ ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - ~~ There are reports that this is affecting desktop TPM backed FDE too. - ~~ + ~~There are reports that this is affecting desktop TPM backed FDE too.~~ ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. - - ~~There are reports that this is affecting desktop TPM backed FDE too.~~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following snapd 2.62 update
This is a 24.04 release blocking bug as it is a regression and results in a failure to boot for TPM backed FDE instances. ** Description changed: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. + This has caused a regression and TPM backed FDE instances no longer boot + as expected. - This has caused a regression and TPM backed FDE instances no longer boot as expected. + There are reports that this is affecting desktop TPM backed FDE too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] [NEW] 24.04 TPM backed FDE regression following snapd 2.62 update
Public bug reported: Azure testing has reported an issue following update of the nullboot package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed included the vendoring of snapd 2.62. This has caused a regression and TPM backed FDE instances no longer boot as expected. There are reports that this is affecting desktop TPM backed FDE too. ** Affects: nullboot (Ubuntu) Importance: Undecided Status: New ** Affects: shim (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: nullboot (Ubuntu Noble) Importance: Undecided Status: New ** Affects: shim (Ubuntu Noble) Importance: Undecided Status: New ** Affects: snapd (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: nullboot (Ubuntu) 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/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062024] Re: armhf doesn't build disk-image-uefi
** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062024 Title: armhf doesn't build disk-image-uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu) 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/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: chrony (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Noble) 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/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061851] [NEW] linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
Public bug reported: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: snapd (Ubuntu Noble) Importance: Undecided Status: New ** Tags: block-proposed block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] Re: Mantic preseeding of LXD using incorrect track/channel
This does not affect Noble as we no longer preseed LXD in >=Noble ** Also affects: livecd-rootfs (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Mantic) Assignee: (unassigned) => Philip Roche (philroche) ** Description changed: Recent Mantic cloud image builds fail - see https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087 build log for an example. ``` + UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download --cohort=MSAqIDE3MTI5MDgwNDcgNWIzNmM3MmIwYjVmNDIyMjQ5Y2NmY2JhNjA4MjAyNTliYzAyNjA4NWYzMjA1MWNlN2U3Y2Y3NjE5NzgwMmZkMQ== --channel=stable/ubuntu-23.10 lxd Fetching snap "lxd" store_download.go:142: no host system xdelta3 available to use deltas error: cannot download snap "lxd": no snap revision available as specified ``` The was due to the default track now pointing to "5.21" instead of "latest". That change was made 20240411 which corresponds to when we started seeing failures. - The long term solution is to pressed from "latest/" for all snaps and no + The long term solution is to preseed from "latest/" for all snaps and no longer assume that "latest/" is the default. - [ Impact ] All image with preseeding of the LXD snap will fail [ Test Plan ] - * Successfully build image with LXD preseeded with these changes - * confirm LXD is preseeded/installed and works as expected. - * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. + * Successfully build image with LXD preseeded with these changes + * confirm LXD is preseeded/installed and works as expected. + * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. [ Where problems could occur ] - * If other snaps are also preseeded they might not be preseeded as + * If other snaps are also preseeded they might not be preseeded as expected. This is covered in the test plan. [ Other Info ] - * A temporary workaround has been made to point + * A temporary workaround has been made to point 5.21/stable/ubuntu-23.10 to the 5.19 LXD snap but this will expire in one month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061121] [NEW] Mantic preseeding of LXD using incorrect track/channel
Public bug reported: Recent Mantic cloud image builds fail - see https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087 build log for an example. ``` + UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download --cohort=MSAqIDE3MTI5MDgwNDcgNWIzNmM3MmIwYjVmNDIyMjQ5Y2NmY2JhNjA4MjAyNTliYzAyNjA4NWYzMjA1MWNlN2U3Y2Y3NjE5NzgwMmZkMQ== --channel=stable/ubuntu-23.10 lxd Fetching snap "lxd" store_download.go:142: no host system xdelta3 available to use deltas error: cannot download snap "lxd": no snap revision available as specified ``` The was due to the default track now pointing to "5.21" instead of "latest". That change was made 20240411 which corresponds to when we started seeing failures. The long term solution is to pressed from "latest/" for all snaps and no longer assume that "latest/" is the default. [ Impact ] All image with preseeding of the LXD snap will fail [ Test Plan ] * Successfully build image with LXD preseeded with these changes * confirm LXD is preseeded/installed and works as expected. * Confirm that preseeding other snap like google-cloud-cli for example in the GCE images continues to preseed as expected. [ Where problems could occur ] * If other snaps are also preseeded they might not be preseeded as expected. This is covered in the test plan. [ Other Info ] * A temporary workaround has been made to point 5.21/stable/ubuntu-23.10 to the 5.19 LXD snap but this will expire in one month. ** Affects: livecd-rootfs (Ubuntu) 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/2061121 Title: Mantic preseeding of LXD using incorrect track/channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060558] [NEW] AppArmor profile `unconfined_restrictions` missing for noble 6.8 kernel
Public bug reported: A recent update to the Noble introduced AppArmor new profile `unconfined_restrictions` [1]. This is not reflected in the snap preseeding code and need to be updated. Currently any snaps preseeded are not seeded correctly resulting in a longer boot time. [1] https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626/2 ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: Catherine Redfield (catred) Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Assignee: Catherine Redfield (catred) Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: (unassigned) => Philip Roche (philroche) ** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: Philip Roche (philroche) => Catherine Redfield (catred) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060558 Title: AppArmor profile `unconfined_restrictions` missing for noble 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2060558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
Verified Focal: This exact proposed version of livecd-rootfs has been used in cloud image build for many weeks now and has met all of the steps listed in the test plan. GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405`` being one such image with snaps and built using this version of livecd- rootfs. Steps: 1. Launch `daily-ubuntu-minimal-2004-focal-v20240405` from project `ubuntu-os-cloud-devel` in GCE ``` gcloud compute instances create $(petname) --zone=europe-west1-d --image=daily-ubuntu-minimal-2004-focal-v20240405 --image-project=ubuntu-os-cloud-devel ``` 4. logged in and ran `sudo snap debug seeding` ``` ubuntu@usable-mullet:~$ sudo snap debug seeding seeded: true preseeded: true image-preseeding: 5.744s seed-completion: 3.278s ``` 5. and just to double check, yes there are snaps ``` ubuntu@usable-mullet:~$ snap list Name Version Rev Tracking Publisher Notes core20 20240111 2182 latest/stable canonical✓ base google-cloud-cli 471.0.0 229 latest/stable/… google-cloud-sdk✓ classic snapd 2.61.2 21184 latest/stable canonical✓ snapd ``` ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Verified Focal: This exact proposed version of livecd-rootfs has been used in cloud image build for many weeks now and has met all of the steps listed in the test plan. GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405`` being one such image with snaps and built using this version of livecd- rootfs. Steps: 1. Launch `daily-ubuntu-minimal-2004-focal-v20240405` from project `ubuntu-os-cloud-devel` in GCE ``` gcloud compute instances create $(petname) --zone=europe-west1-d --image=daily-ubuntu-minimal-2004-focal-v20240405 --image-project=ubuntu-os-cloud-devel ``` 4. logged in and ran `sudo snap debug seeding` ``` ubuntu@usable-mullet:~$ sudo snap debug seeding seeded:true preseeded: true image-preseeding: 5.744s seed-completion: 3.278s ``` 5. and just to double check, yes there are snaps ``` ubuntu@usable-mullet:~$ snap list Name Version RevTracking Publisher Notes core2020240111 2182 latest/stablecanonical✓ base google-cloud-cli 471.0.0 229latest/stable/… google-cloud-sdk✓ classic snapd 2.61.221184 latest/stablecanonical✓ snapd ``` ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
MP with catred's proposed changes @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/463488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] Re: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
MP with catred's proposed changes @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/463488 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059730 Title: Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Now uploaded to Jammy queue @ https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup
** Also affects: google-guest-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: google-guest-agent (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: google-guest-agent (Ubuntu Xenial) 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/2057965 Title: google-startup-scripts runs before cloud-init finished network setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup
@holmanb > google-startup-scripts.service starts well after the network is online You are correct. I have updated the bug description now. > due to configuration via cloud-init not being fully completed, apt sources for example, when startup scripts are run ** Description changed: - New GCP dailies are failing startup-script tests, due to network not - being fully set up when startup scripts are run. The failure can be - reproduced as follows: + New GCP dailies are failing startup-script tests, due to configuration + via cloud-init not being fully completed, apt sources for example, when + startup scripts are run. The failure can be reproduced as follows: Using startup_script.sh: #!/bin/bash cp /etc/apt/sources.list /tmp/startup-sources.list - $ gcloud compute instances create startup-test --image daily-ubuntu-2204-jammy-v20240314 --image-project ubuntu-os-cloud-devel --metadata-from-file=startup-script=startup_script.sh [...] $ ssh [INSTANCE IP] > diff /tmp/startup-sources.list /etc/apt/sources.list 0a1,8 > ## Note, this file is written by cloud-init on first boot of an instance > ## modifications made here will not survive a re-bundle. > ## if you wish to make changes you can: > ## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg > ## or do the same in user-data > ## b.) add sources in /etc/apt/sources.list.d > ## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl - > + > 3,4c11,12 < deb http://archive.ubuntu.com/ubuntu/ jammy main restricted < # deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted --- > deb http://us-central1.gce.archive.ubuntu.com/ubuntu/ jammy main restricted > # deb-src http://us-central1.gce.archive.ubuntu.com/ubuntu/ jammy main restricted 8,9c16,17 < deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted < # deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted --- [...] - - On earlier images (such as ubuntu-2204-jammy-v20240307 in ubuntu-os-cloud) do not show this behaviour. The change is due to a change in ubuntu-pro 31 (see https://github.com/canonical/ubuntu-pro-client/blob/dfe1f1ed4678c50240d4e251f41d33bb4034135e/debian/changelog#L40 for details) that removes a systemd ordering on cloud-config.service. As side effect of this change was the removal of cloud-config.service (and ubuntu-advantage.service) from systemd's critical chain. + On earlier images (such as ubuntu-2204-jammy-v20240307 in ubuntu-os- + cloud) do not show this behaviour. The change is due to a change in + ubuntu-pro 31 (see https://github.com/canonical/ubuntu-pro- + client/blob/dfe1f1ed4678c50240d4e251f41d33bb4034135e/debian/changelog#L40 + for details) that removes a systemd ordering on cloud-config.service. + As side effect of this change was the removal of cloud-config.service + (and ubuntu-advantage.service) from systemd's critical chain. On v20240307 (startup scripts execute correctly): catred@startup-test-control:~$ systemd-analyze critical-chain google-startup-scripts.service The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. google-startup-scripts.service +18.262s └─multi-user.target @28.480s - └─ubuntu-advantage.service @28.480s - └─cloud-config.service @27.372s +1.095s - └─snapd.seeded.service @20.048s +7.312s - └─snapd.service @12.469s +7.555s - └─basic.target @11.558s - └─sockets.target @11.540s - └─snap.lxd.daemon.unix.socket @24.376s - └─sysinit.target @10.825s - └─cloud-init.service @8.432s +2.267s - └─systemd-networkd-wait-online.service @6.467s +1.935s - └─systemd-networkd.service @6.347s +112ms - └─network-pre.target @6.328s - └─cloud-init-local.service @4.309s +2.006s - └─systemd-remount-fs.service @1.829s +68ms - └─systemd-fsck-root.service @1.587s +160ms - └─systemd-journald.socket @1.292s - └─system.slice @1.068s - └─-.slice @1.068s - + └─ubuntu-advantage.service @28.480s + └─cloud-config.service @27.372s +1.095s + └─snapd.seeded.service @20.048s +7.312s + └─snapd.service @12.469s +7.555s + └─basic.target @11.558s + └─sockets.target @11.540s + └─snap.lxd.daemon.unix.socket @24.376s + └─sysinit.target @10.825s + └─cloud-init.service @8.432s +2.267s + └─systemd-networkd-wait-online.service @6.467s +1.935s + └─systemd-networkd.service @6.347s +112ms + └─network-pre.target @6.328s +
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Test plan updated for Jammy too ** Description changed: After the kernel roll to linux-gcp-5.15 to version 5.15.0-1051.59_20.04.1 the public cloud team pre publication test were failing on our snap_preseed_optimized test which checks to ensure that snaps are preseeded correctly This test checks the output of `snap debug seeding` to assert `seed- completion` is present and not empty. `` ❯ snap debug seeding seeded:true preseeded: true image-preseeding: 39.367s seed-completion: 1.335s ``` If `/var/lib/snapd/seed/seed.yaml` exists it also asserts that `preseeded` is present and not empty. With the recent kernel update this test is failing which indicates a kernel feature mismatch between the running kernel and the feature set hard-coded in livecd-rootfs for this image. Boot will be slowed by ~200ms until this is resolved in livecd-rootfs. This solution is to add a 5.15 apparmor configuration to the focal branch of livecd-rootfs The issue is also present with the recent 5.15 kernels in Jammy. Related bugs LP: #2031943 and LP: #2045384 [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] - * build any focal cloud image with HWE 5.15 kernel + * for focal build any cloud image with preseeded snaps with HWE 5.15 kernel + * for jammy build any cloud image with preseeded snaps with up to date 5.15 kernel * boot * run `snap debug preseed` * assert the test described above passes [ Where problems could occur ] * Similar patches already exist for later releases 6.2, 6.5 kernel etc. and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057559] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: update-manager (Ubuntu Noble) Importance: Wishlist Assignee: Calvin Mwadime Makokha (calvinmwadime) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057559 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2057559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057651] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: wsl-pro-service (Ubuntu Noble) 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/2057651 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2057651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057671] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: software-properties (Ubuntu Noble) 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/2057671 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2057671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057674] Re: Rename the ubuntu-advantage-tools package
Subscribing ubuntu-release as per FFE policy. This bug affects noble cloud image release ** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Noble) 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/2057674 Title: Rename the ubuntu-advantage-tools package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/2057674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056078] Re: 6.8 Kernel AppArmor Feature Missing on Noble
Subscribing ubuntu-release as per FFE policy. This bug will block noble cloud image release ** Also affects: livecd-rootfs (Ubuntu Noble) 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/2056078 Title: 6.8 Kernel AppArmor Feature Missing on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2056078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055194] [NEW] Invalid version: 'None' when re-installing/upgrading python-apt using pip when wheel module installed
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
incorrect
* This applies to the Mantic, Jammy and earlier versions. It has been
fixed in Noble
[ Test Plan ]
* Attempt re-install of python-apt
[ Where problems could occur ]
* Being unable to install python-apt
* Being unable to upgrade python-apt
* Being unable to re-install python-apt
[ Other Info ]
* This been resolved upstream @ https://salsa.debian.org/apt-
team/python-apt/-/commit/765772fad2d3611b952b6ad416c6b765739a902a and in
`2.4.y` branch @ https://salsa.debian.org/apt-team/python-
apt/-/tree/2.4.y?ref_type=heads
* You can workaround this too by setting environment variable
`DEBVER=2.4.11`
* Reproducer
```
❯ python3 -m venv venv
❯ source venv/bin/activate
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
setuptools 68.1.2
❯ python3 -m pip install --upgrade
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Collecting
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Cloning ssh://git.launchpad.net/ubuntu/+source/python-apt (to revision
ubuntu/jammy-updates) to ./pip-req-build-t7t8vnsu
Running command git clone --filter=blob:none --quiet
ssh://git.launchpad.net/ubuntu/+source/python-apt /tmp/pip-req-build-t7t8vnsu
warning: filtering not recognized by server, ignoring
warning: filtering not recognized by server, ignoring
Running command git checkout -b ubuntu/jammy-updates --track
origin/ubuntu/jammy-updates
Switched to a new branch 'ubuntu/jammy-updates'
branch 'ubuntu/jammy-updates' set up to track 'origin/ubuntu/jammy-updates'.
Resolved ssh://git.launchpad.net/ubuntu/+source/python-apt to commit
f043e6bd4d2842d6693d48e0c68c7a63bd3be9ac
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: python-apt
Building wheel for python-apt (pyproject.toml) ... done
Created wheel for python-apt:
filename=python_apt-0.0.0-cp311-cp311-linux_x86_64.whl size=1808770
sha256=472ff7d9bcdad50912dc42499d68bc5e958b9843c355c157ccf920021728c205
Stored in directory:
/tmp/pip-ephem-wheel-cache-nyc3gs5x/wheels/c7/db/d7/21a72eaa5719ab3ab1ca242d5d0e08aca4aa67eaddb3c9b8fa
Successfully built python-apt
Installing collected packages: python-apt
Successfully installed python-apt-0.0.0
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
python-apt 0.0.0
setuptools 68.1.2
# install wheel
❯ python3 -m pip install wheel
Collecting wheel
Obtaining dependency information for wheel from
https://files.pythonhosted.org/packages/c7/c3/55076fc728723ef927521abaa1955213d094933dc36d4a2008d5101e1af5/wheel-0.42.0-py3-none-any.whl.metadata
Using cached wheel-0.42.0-py3-none-any.whl.metadata (2.2 kB)
Using cached wheel-0.42.0-py3-none-any.whl (65 kB)
Installing collected packages: wheel
Successfully installed wheel-0.42.0
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
python-apt 0.0.0
setuptools 68.1.2
wheel 0.42.0
# Now try re-install
❯ python3 -m pip install --upgrade
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Collecting
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Cloning ssh://git.launchpad.net/ubuntu/+source/python-apt (to revision
ubuntu/jammy-updates) to ./pip-req-build-lk856i6s
Running command git clone --filter=blob:none --quiet
ssh://git.launchpad.net/ubuntu/+source/python-apt /tmp/pip-req-build-lk856i6s
warning: filtering not recognized by server, ignoring
warning: filtering not recognized by server, ignoring
Running command git checkout -b ubuntu/jammy-updates --track
origin/ubuntu/jammy-updates
Switched to a new branch 'ubuntu/jammy-updates'
branch 'ubuntu/jammy-updates' set up to track 'origin/ubuntu/jammy-updates'.
Resolved ssh://git.launchpad.net/ubuntu/+source/python-apt to commit
f043e6bd4d2842d6693d48e0c68c7a63bd3be9ac
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [34 lines of output]
Traceback (most recent call last):
File
"/tmp/venv/lib/python3.11/site-packages/setuptools/_normalization.py", line 59,
in safe_version
return str(packaging.version.Version(v))
File
"/tmp/venv/lib/python3.11/site-packages/setuptools/_vendor/packaging/version.py",
line 198, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version:
'None'
During handling of the above exception,
[Bug 2052789] Re: AppArmor profiles missing in kernel 5.15.0-1051+ release
Jammy fix is still awaiting review @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd- rootfs/+merge/460929 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
As verification I have successfully built and published Ubuntu 21.10 Impish armhf cloud images with this patch applied as in -proposed. http://cloud-images.ubuntu.com/impish/20211208.1/ Note that armhf downloads are present and have passed all available testing. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
** Description changed: [Impact] - * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left + * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left on device' errors. See attached build log snippet for details on the disk space errors. - * The fix has landed upstream in the livecd-rootsfs master branch + * The fix has landed upstream in the livecd-rootsfs master branch https://git.launchpad.net/livecd- rootfs/commit/?id=1a7e9ca8c9c7db434e02efad38ca270eca779339 [Test Plan] - * Test plan is to build armhf image with a patched livecd-rootfs + * Test plan is to build armhf image with a patched livecd-rootfs + +1. Build without this patch and observe failing build due to disk space error +2. Apply patch and build and observe a successful build. + + I have verified successfuly build in private build https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665 + + This build is private as built using the Canonical CPC tooling. + [Where problems could occur] - * The only downside I can think of is a bigger disk image. Since + * The only downside I can think of is a bigger disk image. Since landing upstream in the master branch we have seen no issues with the disk size in the 22.04 image builds. [Other Info] - - * I will create MP against livecd-rootfs:ubuntu/impish branch. + + * I will create MP against livecd-rootfs:ubuntu/impish branch. ** Attachment added: "successful-tmpdrgs_w0o-snippet.buildlog" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+attachment/5546245/+files/successful-tmpdrgs_w0o-snippet.buildlog ** Description changed: [Impact] * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left on device' errors. See attached build log snippet for details on the disk space errors. * The fix has landed upstream in the livecd-rootsfs master branch https://git.launchpad.net/livecd- rootfs/commit/?id=1a7e9ca8c9c7db434e02efad38ca270eca779339 [Test Plan] * Test plan is to build armhf image with a patched livecd-rootfs -1. Build without this patch and observe failing build due to disk space error -2. Apply patch and build and observe a successful build. + 1. Build without this patch and observe failing build due to disk space error + 2. Apply patch and build and observe a successful build. - I have verified successfuly build in private build https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665 - - This build is private as built using the Canonical CPC tooling. - + I have verified successfuly build in private build + https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665 + + This build is private as built using the Canonical CPC tooling. + Successful build log snippet for the failing section attached @ successful-tmpdrgs_w0o-snippet.buildlog. [Where problems could occur] * The only downside I can think of is a bigger disk image. Since landing upstream in the master branch we have seen no issues with the disk size in the 22.04 image builds. [Other Info] * I will create MP against livecd-rootfs:ubuntu/impish branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
Test build with this patch was successful - see private build https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
MP now created https://code.launchpad.net/~philroche/livecd- rootfs/+git/livecd-rootfs/+merge/412892 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] [NEW] [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
Public bug reported: [Impact] * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left on device' errors. See attached build log snippet for details on the disk space errors. * The fix has landed upstream in the livecd-rootsfs master branch https://git.launchpad.net/livecd- rootfs/commit/?id=1a7e9ca8c9c7db434e02efad38ca270eca779339 [Test Plan] * Test plan is to build armhf image with a patched livecd-rootfs [Where problems could occur] * The only downside I can think of is a bigger disk image. Since landing upstream in the master branch we have seen no issues with the disk size in the 22.04 image builds. [Other Info] * I will create MP against livecd-rootfs:ubuntu/impish branch. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Build log snippet showing disk space error" https://bugs.launchpad.net/bugs/1953609/+attachment/5546223/+files/tmpdrgs_w0o-snippet.buildlog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928040] Re: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set
@sil2100 We have now successfully tested reboot with grub-efi- amd64-signed 1.167~16.04.2+2.04-1ubuntu44 from xenial-proposed with image ubuntu-1604-xenial-v20200429 in GCE And I confirmed the bug with grub-efi-amd64-signed 1.66.23+2.02~beta2-36ubuntu3.23 prior to testing Marking verification-done and verification-done-xenial ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928040 Title: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1928040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
I also verified the fix with a python2 virtualenv. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
I have verified fix in amd64 xenial VM. Test case: * `sudo apt install python3-virtualenv virtualenv python-virtualenv` * Confirm that any `pip` operations fail as per bug description * `virtualenv -p /usr/bin/python3 venv/py3 --verbose` * `source ./venv/py3/bin/activate` * `pip list` * Enable proposed as per https://wiki.ubuntu.com/Testing/EnableProposed * Upgrade packages using `sudo apt install python3-virtualenv virtualenv python-virtualenv` * Confirm that any `pip` operations succeed * `virtualenv -p /usr/bin/python3 venv/py3-verification --verbose` * I also confirm here that the pip and setup tools were being pinned here > Installing setuptools < 51.3, pkg_resources, pip < 21, wheel... * `source ./venv/py3-verification/bin/activate` * `pip list` Tags added verification-done-xenial verification-done ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
@stefanor Thanks for the explanation. I have a one liner workaround now: ``` virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-download && . venv/py3/bin/activate && python3 -m pip install --upgrade 'setuptools; python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and python_version >= "3.0"' pip wheel && python3 -m pip list ``` Which uses the bundled pip, wheel and setuptools initially but then upgrades pip, wheel and setuptools using environment markers to ensure the supported version is installed. I do question the EOL argument. Xenial 16.04 is nearly at the end of standard support yes, but there will be many users continuing to use Xenial 16.04 with ESM for another five years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
I have found the following workaround on Ubuntu 16.04 Xenial Do not install setuptools on virtualenv creation: `virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-setuptools` Install a supported setuptools version after virtualenv creation and activation: `python3 -m pip install --upgrade 'setuptools; python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and python_version >= "3.0"'` > Ignoring setuptools: markers 'python_version >= "3.6"' don't match your > environment > Ignoring setuptools: markers 'python_version < "3.0"' don't match your > environment > Collecting setuptools<51.3.0 > Using cached setuptools-50.3.2-py3-none-any.whl (785 kB) > Installing collected packages: setuptools > Successfully installed setuptools-50.3.2 or by adding the following to your requirements.txt ``` setuptools; python_version >= "3.6" setuptools<51.3.0; python_version < "3.6" and python_version >= "3.0" ``` This results in `python3 -m pip list`: > pip20.3.3 > setuptools 50.3.2 > wheel 0.36.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
This is being tracked in setuptools upstream too https://github.com/pypa/setuptools/issues/2541 The cause is that python-virtualenv is pulling in setuptools 51.3.3 `virtualenv -p /usr/bin/python3 venv/py3 --verbose` ``` snip... Installing setuptools, pkg_resources, pip, wheel... Collecting setuptools Using cached https://files.pythonhosted.org/packages/b2/81/509db0082c0d2ca2af307c6652ea422865de1f83c14b1e1f3549e415cfac/setuptools-51.3.3-py3-none-any.whl Collecting pkg_resources Collecting pip Using cached https://files.pythonhosted.org/packages/54/eb/4a3642e971f404d69d4f6fa3885559d67562801b99d7592487f1ecc4e017/pip-20.3.3-py2.py3-none-any.whl Collecting wheel Using cached https://files.pythonhosted.org/packages/65/63/39d04c74222770ed1589c0eaba06c05891801219272420b40311cd60c880/wheel-0.36.2-py2.py3-none-any.whl Installing collected packages: setuptools, pkg-resources, pip, wheel Successfully installed pip-20.3.3 pkg-resources-0.0.0 setuptools-51.3.3 wheel-0.36.2 ...snip... ``` But 51.3.0 dropped support for python 3.5 which is what ships with Xenial. The fix would be to pin setuptools to `<51.3.0`. ** Bug watch added: github.com/pypa/setuptools/issues #2541 https://github.com/pypa/setuptools/issues/2541 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885571] Re: Can't set boot kernel in GRUB on focal image
** Also affects: grub (Ubuntu) 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/1885571 Title: Can't set boot kernel in GRUB on focal image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1885571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering
CPC are seeing this issue in _all_ minimal cloud images testing with LXD snap version 4.2 or greater. This blocks promotion of all minimal cloud download images and blocks build and publication of both daily and release cloud images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882955 Title: LXD 4.2 broken on linux-kvm due to missing VLAN filtering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
Verification of livecd-rootfs 2.664.2 in focal -proposed completed. The following verification was completed. * Perform livefs build with project ubuntu-base * Boot *-disk-kvm.img using kvm * Confirm it boots * Confirm there is no boot speed regression * Confirm that running `sudo apt-get autoremove` results in no packages being removed * Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. See test images @ https://people.canonical.com/~philroche/lp-1880170-Revert-of-initramfs-package-removal-in-KVM-image/focal/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
Verification of livecd-rootfs 2.620.3 in eoan -proposed completed. The following verification was completed. * Perform livefs build with project ubuntu-base * Boot *-disk-kvm.img using kvm * Confirm it boots * Confirm there is no boot speed regression * Confirm that running `sudo apt-get autoremove` results in no packages being removed * Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. See test images @ https://people.canonical.com/~philroche/lp-1880170-Revert-of-initramfs-package-removal-in-KVM-image/eoan/ ** Tags removed: verification-needed verification-needed-eoan verification-needed-focal ** Tags added: verification-done verification-done-eoan verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
debdiff for eoan SRU rev2. Building package without extraneous contents as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html #build-noextra ** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal-eoan-rev2.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375697/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan-rev2.debdiff ** Patch removed: "lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375695/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff ** Patch removed: "lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375692/+files/lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
debdiff for focal SRU rev2. Building package without extraneous contents as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html #build-noextra ** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal-focal-rev2.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375696/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-focal-rev2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
debdiff for eoan SRU ** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375695/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
debdiff for focal SRU ** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375692/+files/lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
** Description changed: - We want to the revert of initramfs package removal in KVM image. + No packages marked for auto-removal should be present in a published + cloud image. + + The current kvm binary hook in livecd-rootfs removes the packages + `initramfs-tools` and `busybox-initramfs`. This results in many packages + [1] being marked for auto-removal. These packages are still required in + the image and should not be marked for auto-removal. + + The removal of initramfs-tools and busybox-initramfs was to avoid the + generation of initramfs in images that should boot initramfsless. + + This requirement is obsolete now because the initramfsless boot handling + is now handled via setting GRUB_FORCE_PARTUUID in /etc/default/grub.d/40-force-partuuid.cfg. [Impact] - * We don't want any packages marked for auto-removal on a published kvm - cloud image. + * No packages marked for auto-removal. This is a requirement for all + public cloud images. [Test Case] - * Perform livefs build with project ubuntu-base - * Boot *-disk-kvm.img using kvm -* Confirm it boots -* Confirm there is no boot speed regression + * Perform livefs build with project ubuntu-base + * Boot *-disk-kvm.img using kvm + * Confirm it boots + * Confirm there is no boot speed regression +* Confirm that running `sudo apt-get autoremove` results in no packages being removed +* Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. [Regression Potential] - * Boot speed regression - * Unable to boot KVM image + * Boot speed regression + * Unable to boot KVM image [Other Info] - * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 - * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 - * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified + * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 + * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 + * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified + + + [1] apport apport-symptoms at bc bcache-tools bolt btrfs-progs byobu cryptsetup cryptsetup-bin cryptsetup-run dmeventd ethtool finalrd + fonts-ubuntu-console fwupd fwupd-signed git git-man htop initramfs-tools-bin klibc-utils kpartx landscape-common libaio1 libarchive13 + libcurl3-gnutls libdevmapper-event1.02.1 liberror-perl libevent-2.1-7 libfl2 libfwupd2 libfwupdplugin1 libgcab-1.0-0 libgpgme11 + libgudev-1.0-0 libgusb2 libisns0 libjson-glib-1.0-0 libjson-glib-1.0-common libklibc liblvm2cmd2.03 libmspack0 libreadline5 + libsgutils2-2 libsmbios-c2 libtss2-esys0 liburcu6 libutempter0 libxmlb1 libxmlsec1 libxmlsec1-openssl libxslt1.1 lvm2 lxd-agent-loader + lz4 mdadm open-iscsi open-vm-tools patch pollinate python3-apport python3-automat python3-click python3-colorama python3-constantly + python3-debconf python3-debian python3-hamcrest python3-hyperlink python3-incremental python3-newt python3-problem-report python3-pyasn1 + python3-pyasn1-modules python3-service-identity python3-systemd python3-twisted python3-twisted-bin python3-zope.interface run-one + screen sg3-utils sosreport thin-provisioning-tools tmux tpm-udev update-notifier-common xfsprogs zerofree -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] [NEW] SRU: Revert of initramfs package removal in KVM image
Public bug reported: We want to the revert of initramfs package removal in KVM image. [Impact] * We don't want any packages marked for auto-removal on a published kvm cloud image. [Test Case] * Perform livefs build with project ubuntu-base * Boot *-disk-kvm.img using kvm * Confirm it boots * Confirm there is no boot speed regression [Regression Potential] * Boot speed regression * Unable to boot KVM image [Other Info] * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified ** Affects: livecd-rootfs (Ubuntu) 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/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869963] Re: Unable to install chromium-browser 20.04
This does not appear to be docker specific but the chromium package has moved to a snap package. What is your host OS and kernel version? Is the snapd service running in the container? We have added the chromium package to this bug so they can investigate. ** Changed in: cloud-images Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869963 Title: Unable to install chromium-browser 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861704] Re: ubuntu-fan recommends netcat package in universe
It appears that a bug was already filed against netcat https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861704 Title: ubuntu-fan recommends netcat package in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1861704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861704] [NEW] ubuntu-fan recommends netcat package in universe
Public bug reported: Following some debug of the docker.io package in universe, we (Canonical CPC) discovered that the ubuntu-fan package from main and the netcat- traditional package from universe were being installed. This was due to the following dependency/recommends tree: * docker.io (in universe) recommends ubuntu-fan (main) * ubuntu-fan (main) recommends netcat (universe) * netcat (universe) is a transitional package and depends on netcat-traditional (universe) Our concern is that this might be a packaging violation as ubuntu-fan is recommending a package not in main. > In addition, the packages in main > > must not require a package outside of main for compilation or execution > (thus, the package must > not declare a "Depends", "Recommends", or "Build-Depends" relationship on a > non-main package), Source: https://people.canonical.com/~cjwatson/ubuntu-policy/policy.html /ch-archive.html#s-main I will file a bug against netcat too to start a discussion on netcat being built from netcat-openbsd (main) instead of netcat-traditional (universe). Our feeling is that netcat is such a frequently depended on or recommended package that it being present in main would benefit Ubuntu. ** Affects: ubuntu-fan (Ubuntu) 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/1861704 Title: ubuntu-fan recommends netcat package in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1861704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851858] Re: adds ESM to sources.list.d unconditionally, despite it being x86-only
We (CPC) are seeing this issue too when trying to build Trusty non amd64/i386 images. When we hit this yesterday Security team confirmed that ESM doesn't support other arches but we shouldn't block builds because of this change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851858 Title: adds ESM to sources.list.d unconditionally, despite it being x86-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1851858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840135] Re: Request for new Eoan build of python-simplestreams
Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840135 Title: Request for new Eoan build of python-simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1840135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840135] [NEW] Request for new Eoan build of python-simplestreams
Public bug reported: Following the merge of MP https://code.launchpad.net/~philroche/simplestreams/+git/simplestreams/+merge/369682 would it be possible to get a new build of simplestreams published to Eoan? This change might not be SRUable as it could change behavior that current users are already used to. ** Affects: simplestreams (Ubuntu) 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/1840135 Title: Request for new Eoan build of python-simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1840135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766287] Re: 18.04 minimal images on GCE intermittently fail to set up networking
On guidance from raharper I have opened new bug for this @ https://bugs.launchpad.net/cloud-init/+bug/1822353 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766287 Title: 18.04 minimal images on GCE intermittently fail to set up networking To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766287] Re: 18.04 minimal images on GCE intermittently fail to set up networking
I'd like to reopen this following Disco minimal images failing to set up networking due to similar reasons to this bug with the only difference being that no nic was found. A workaround was found to set up cloud-init service config: /etc/systemd/system/cloud-init-local.service.d/gcp.conf ``` [Unit] After=systemd-udev-trigger.service [Service] ExecStartPre=/bin/udevadm settle ``` The goal of this workaround is to: 1) ensure that cloud-init-local.service runs after systemd-udev-trigger.service starts (this is what triggers udev coldplug events, like plugging in the nic) 2) Run udevadm settle before we start cloud-init local so that any nic processing is completed before cloud-init starts looking for a nic. Currently this is only required on minimal images but there is a chance it could occur in base images too should they boot quick enough. Minimal disco does not have snap preseeding as base images do and due to this running before cloud-init it makes it extremely unlikely to happen in base images. I understand that cloud-init might not be the place to fix the issue for all images but I'd like to re-open this bug to start that discussion. I have attached cloud-init logs, netplan yaml, image manifest and sosreports from an instance that failed to set up networking. ** Attachment added: "Disco GCE Minimal Failed Networking Setup Logs" https://bugs.launchpad.net/cloud-init/+bug/1766287/+attachment/5250709/+files/20190322-Disco-GCE-Minimal-Failed-Networking-Setup-Logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766287 Title: 18.04 minimal images on GCE intermittently fail to set up networking To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813246] Re: Update gce-compute-image-packages to 20190124
Verification is complete and GCE have given +1 on 20190124 packages migrating to -updates ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813246 Title: Update gce-compute-image-packages to 20190124 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1813246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
Myself and @kamalmostafa spoke and the issue is not obvious especially as linux-azure is installed in the base image too which does not exhibit the issue. Although not obvious @kamalmostafa did suspect the issue to lie somewhere with random number generation and a related package/kernel patch. One line of investigation is to check the package diff between the minimal image with initramfs-tools installed and the image without that installed. That diff is @ https://pastebin.canonical.com/p/7hJTSQHbyD/ Another possibility is to check the package diff between base and minimal. That diff is @ https://pastebin.canonical.com/p/B9m7GbsFhs/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
@kamalmostafa @mhcerri I noticed that linux-azure 4.18.0.1003.3 was uploaded to cosmic-proposed so I built a new test image. For convenience I have imported your SSH keys to 'ssh ubuntu@51.140.217.58'. All logs and VHD etc. have been uploaded to https://private- fileshare.canonical.com/~philroche/azure-cosmic-20181011/ ** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1003.3 (from cosmic-proposed) boot log" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5199957/+files/eeDaquoh3aiqu-vm-imagedebug-boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1002.2 (from cosmic-proposed) boot log" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5195337/+files/chohv4Va7Ahx7-vm-imagedebug-boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
On request on IRC I have tried a new image with linux-azure 4.18.0.1002.2 from cosmic-proposed. This too exhibited the slow boot 5min 19.070s (kernel) + 41.724s (userspace) = 6min 794ms Full logs @ https://private-fileshare.canonical.com/~philroche/azure- cosmic-20181001/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
