[Bug 2083685] Re: Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories
I attempted a build applying the linked patch, and `germinate` did not like what was happening. it seemed to download most of the correct files but something was missing. I've personally never tried `germinate` from the snapshot archive, so I can't state if it's user error when setting up the patch and passing in timestamp, if it's an ephemeral issue, or if there's something else at play here. ** Attachment added: "build_log.amd64.qcow2.txt" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083685/+attachment/5825997/+files/build_log.amd64.qcow2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083685 Title: Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083611] Re: trying to enable livepatch and anbox-cloud
this normally indicates the the kernel does not have support for the squashfs filesystem. in most Ubuntu kernels, squashfs support is compiled in. Since this is a pro-only kernel, less easy for me to check. you can check /proc/filesystems but that "only" shows filesystems in use: cat /proc/filesystems you normally wouldn't need to modprobe squashfs as it's _generally_ builtin. we'll have to get someone from the kernel side to weigh in on the realtime kernel. some useful information 1. output of /proc/filesystems 2. install / setup procedures and environment (just a gist -- from an ISO, in house, public cloud, etc) 3. output of dmesg in full the error from dmesg above is usually what happens when an unauthorized user tries to read dmesg. trying running as sudo. you can try grepping around for `snapd` or `squashfs` but likely it'll pop up as some other thing in `dmesg`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083611 Title: trying to enable livepatch and anbox-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2083611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083685] [NEW] Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories
Public bug reported: # Background as of 20241004 (RIP w9xn), $SNAPSHOT_SERVICE_TIMESTAMP has been made available as an official environment variable in launchpad livefs builds. When a build is triggered with in launchpad with the metadata snapshot_service_timestamp, $SNAPSHOT_SERVICE_TIMESTAMP will be populated with the provided timestamp. This allows livecd-rootfs to configure the initial mirrors to use the snapshot service rather than the current overwrite cases. documentation on the snapshot service: https://snapshot.ubuntu.com/ proposed patch by mwhudson: https://paste.ubuntu.com/p/5RtpSKm2QQ/ This is only to enable the snapshot service in one variable. There are other variables throughout livecd-rootfs that reference archives which may need to be investigated LB_PARENT_MIRROR_BINARY LB_PARENT_MIRROR_BINARY_VOLATILE LB_PARENT_MIRROR_BINARY_SECURITY Section of code around $EXTRA_PPAS : livecd-rootfs/live- build/auto/config:1519 [0] Any hooks that add PPAs or change the default apt configurations may need to be investigated as well. if these are housed in private areas, and nested (looking at you CPC), then those will need to be handled by individual teams. ** Affects: livecd-rootfs (Ubuntu) Importance: Wishlist Assignee: Simon Poirier (simpoir) Status: New ** Affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu Oracular) Importance: Wishlist Assignee: Simon Poirier (simpoir) Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Oracular) Importance: Wishlist Assignee: Simon Poirier (simpoir) Status: New ** Summary changed: - Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuration Repositories + Utilize SNAPSHOT_SERVICE_TIMESTAMP When ConfiguringRepositories ** Summary changed: - Utilize SNAPSHOT_SERVICE_TIMESTAMP When ConfiguringRepositories + Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083685 Title: Utilize SNAPSHOT_SERVICE_TIMESTAMP When Configuring Repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
ran builds on launchpad as well (these take a long time). noble: https://launchpad.net/~cloudware/+livefs/ubuntu/noble/cpc- development/+build/694145 focal: https://launchpad.net/~cloudware/+livefs/ubuntu/focal/cpc- development/+build/694072 this proves that on the launchpad workers, everything working as expected there. bartender, outside the "host" VM, runs in the same path -- a buildd container of $SUITE is where the builds occur. The launchpad test shows that any differences that occur due to any host differences (like installing the snap). An issue can occur if there's a breaking change _specifically_ between host VM + host LXD + $SUITE container. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done 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/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
test and verified focal 1. didn't need to clone, thank you git-ubuntu :) 2. git checkout ubuntu/focal-proposed 3. utilized ubuntu-old-fashioned/bartender to run a build: bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd-rootfs --hook-extras-dir /home/jchittum/dev01/cloudware/cpc_packaging.extra --build-provider aws -- --series focal --project ubuntu-cpc --image-target disk-image --image-target qcow2 --image-target vmdk 4. ensured that the sbom was made for the vmdk and qcow focal/downloads$ ls build.output/ binary.log livecd.ubuntu-cpc.img livecd.ubuntu-cpc.qcow.filelist livecd.ubuntu-cpc.vmdk.manifest livecd.ubuntu-cpc.disk-image.filelist livecd.ubuntu-cpc.initrd-generic livecd.ubuntu-cpc.qcow.manifest livecd.ubuntu-cpc.vmdk.spdx livecd.ubuntu-cpc.disk-image.manifest livecd.ubuntu-cpc.kernel-generic livecd.ubuntu-cpc.qcow.spdx livecd.ubuntu-cpc.disk-image.spdx livecd.ubuntu-cpc.manifest livecd.ubuntu-cpc.vmdk livecd.ubuntu-cpc.ext4 livecd.ubuntu-cpc.ova livecd.ubuntu-cpc.vmdk.filelist 5. verified via log that cpc-sbom was installed and used to generate 6. run a cloud-partner build bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd- rootfs --hook-extras-dir /home/jchittum/dev01/cloudware/cpc_packaging.extra --build-provider aws --hook-extras-release-notes-tools-repo https://git.launchpad.net/~cloud- images/cloud-images/+git/cpc-release-notes-tools --hook-extras-release- notes-tools-branch main --hook-extras-sbom-tools-repo git+ssh://g...@github.com/canonical/cpc-sbom.git --hook-extras-sbom- tools-subdir cpc_sbom -- --series focal --project ubuntu-cpc --image- target gce --image-target ec2 7. image builds succeeded 8. saw that the GCE image continue to generate an sbom focal/cloud$ ls ./build.output/ binary.log livecd.ubuntu-cpc.gce.dbx.bin livecd.ubuntu-cpc.gce.sbom.spdx.log livecd.ubuntu-cpc.ec2-hvm-ebs.vmdk livecd.ubuntu-cpc.gce.filelist livecd.ubuntu-cpc.gce.tar.gz livecd.ubuntu-cpc.ec2-hvm-ebs.vmdk.filelist livecd.ubuntu-cpc.gce.manifest livecd.ubuntu-cpc.ec2-hvm-ebs.vmdk.manifest livecd.ubuntu-cpc.gce.sbom.spdx 9. checked log to see that cpc-sbom was used to generate an SBOM _however_ as cpc_packaging.extra series files are not patched for consuming the SBOM, they remained on the system and not downloaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
test and verified jammy 1. didn't need to clone, thank you git-ubuntu :) 2. git checkout ubuntu/noble-proposed 3. utilized ubuntu-old-fashioned/bartender to run a build: bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd-rootfs --hook-extras-dir /home/jchittum/dev01/cloudware/cpc_packaging.extra --build-provider aws -- --series jammy --project ubuntu-cpc --image-target disk-image --image-target qcow2 --image-target vmdk 4. ensured that the sbom was made for the vmdk and qcow ls ../downloads/build.output/ binary.log livecd.ubuntu-cpc.img livecd.ubuntu-cpc.qcow.filelist livecd.ubuntu-cpc.vmdk.manifest livecd.ubuntu-cpc.disk-image.filelist livecd.ubuntu-cpc.initrd-generic livecd.ubuntu-cpc.qcow.manifest livecd.ubuntu-cpc.vmdk.spdx livecd.ubuntu-cpc.disk-image.manifest livecd.ubuntu-cpc.kernel-generic livecd.ubuntu-cpc.qcow.spdx livecd.ubuntu-cpc.disk-image.spdx livecd.ubuntu-cpc.manifest livecd.ubuntu-cpc.vmdk livecd.ubuntu-cpc.ext4 livecd.ubuntu-cpc.ova livecd.ubuntu-cpc.vmdk.filelist 5. verified via log that cpc-sbom was installed and used to generate 6. run a cloud-partner build bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd- rootfs --hook-extras-dir /home/jchittum/dev01/cloudware/cpc_packaging.extra --build-provider aws --hook-extras-release-notes-tools-repo https://git.launchpad.net/~cloud- images/cloud-images/+git/cpc-release-notes-tools --hook-extras-release- notes-tools-branch main --hook-extras-sbom-tools-repo git+ssh://g...@github.com/canonical/cpc-sbom.git --hook-extras-sbom- tools-subdir cpc_sbom -- --series jammy --project ubuntu-cpc --image- target gce --image-target ec2 7. image builds succeeded 8. saw that the GCE image continue to generate an sbom 9. checked log to see that cpc-sbom was used to generate an SBOM _however_ as cpc_packaging.extra series files are not patched for consuming the SBOM, they remained on the system and not downloaded. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
tested and verified noble: 1. used `git-ubuntu` to pull the source locally 2. git checkout pkg/ubuntu/noble-proposed 3. utilized ubuntu-old-fashioned/bartender to run a build: bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd-rootfs --hook-extras-branch noble -- --series noble --project ubuntu-cpc --image-target disk-image --image-target qcow2 --image-target vmdk 4. ensured that the sbom was made for the vmdk and qcow tar -xvzf nearby-cougar-ubuntu-on-the-rocks.tar.gz build.output/ build.output/livecd.ubuntu-cpc.ova build.output/livecd.ubuntu-cpc.vmdk build.output/binary.log build.output/livecd.ubuntu-cpc.vmdk.spdx build.output/livecd.ubuntu-cpc.manifest build.output/livecd.ubuntu-cpc.disk-image.filelist build.output/livecd.ubuntu-cpc.vmdk.filelist build.output/livecd.ubuntu-cpc.qcow.manifest build.output/livecd.ubuntu-cpc.qcow.spdx build.output/livecd.ubuntu-cpc.disk-image.spdx build.output/livecd.ubuntu-cpc.vmdk.manifest build.output/livecd.ubuntu-cpc.initrd-generic build.output/livecd.ubuntu-cpc.qcow.filelist build.output/livecd.ubuntu-cpc.ext4 build.output/livecd.ubuntu-cpc.disk-image.manifest build.output/livecd.ubuntu-cpc.img build.output/livecd.ubuntu-cpc.kernel-generic 5. verified via log that cpc-sbom was installed and used to generate 6. run a cloud-partner build bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/packages/livecd-rootfs/livecd-rootfs --hook-extras-dir /home/jchittum/dev01/cloudware/cpc_packaging.extra --hook-extras-release-notes-tools-repo https://git.launchpad.net/~cloud-images/cloud-images/+git/cpc-release-notes-tools --hook-extras-release-notes-tools-branch main --hook-extras-sbom-tools-repo git+ssh://g...@github.com/canonical/cpc-sbom.git --hook-extras-sbom-tools-subdir cpc_sbom -- --series noble --project ubuntu-cpc --image-target gce --image-target ec2 7. image builds succeded 8. saw that the GCE image continue to generate an sbom 9. checked log to see that cpc-sbom was used to generate an SBOM _however_ as cpc_packaging.extra series files are not patched for consuming the SBOM, they remained on the system and not downloaded. Testing looks good for noble ** 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/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083240] Re: buildd system user lacks homedir leading to issues with snaps[and more]
** Description changed: when running a Noble buildd image as a CI runner, the following error occurs ``` Running job phase... Running test:0 cmd_run.go:1129: WARNING: cannot create user data directory: cannot create snap home dir: mkdir /nonexistent: permission denied Sorry, home directories outside of /home needs configuration. See https://forum.snapcraft.io/t/11209 for details. ``` the buildd user is created with the following code in livecd- rootfs/live-build/buildd/02-user.chroot ``` # Create the buildd user and group. addgroup --gid 2501 buildd adduser --system --disabled-password --gecos 'Build Daemon user' \ - --ingroup buildd --uid 2001 --shell /bin/bash buildd + --ingroup buildd --uid 2001 --shell /bin/bash buildd mkdir -p /build/buildd chown buildd:buildd /build/buildd ``` as of 24.04 (maybe earlier), adduser does not create a homedir for system users: > If no home directory is specified, the default home directory for a new system user is /nonexistent. This directory should never exist on any Debian system, and adduser will never create it automatically. on jammy and earlier images, the following ends up the user conf ``` buildd:x:2001:2501:Build Daemon user,,,:/home/buildd:/bin/bash ``` and on 24.04 ``` buildd:x:2001:2501:Build Daemon user,,,:/nonexistent:/bin/bash ``` this is fixed by adding an explicit `--home /home/buildd` to the user creation call + + [ Impact ] + + * Current buildd images are unable to use snaps (and likely other + issues, since it has assumed an existing $HOME) + + * fix has no impact outside buildd, as the fix is only in a buildd hook + + [ Test Plan ] + + * basic testing: + * build image locally + * check the created buildd user does have a homedir + * attempt to install and run a snap + * expanded testing: + * NOTE: this may not be possible, depending on how launchpad is able to consume images. if not possible, do not consider blocking, and instead get sign off from the Launchpad team that the basic testing is acceptable + * build image in launchpad using a PPA of livecd-rootfs + * point launchpad team to build + * consume buildd image from the launchpad build + * execute a build in the qa environment that requires a snap + + [ Where problems could occur ] + + * if the call is incorrect, no homedir will be made and the fix will fail. + * it's livecd-rootfs, so layers and layers of bash. that can always go wrong. + + [ Other Info ] + + * we'll need to expedite as this is causing issues in launchpad + production now. ** 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/2083240 Title: buildd system user lacks homedir leading to issues with snaps[and more] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083240] [NEW] buildd system user lacks homedir leading to issues with snaps[and more]
Public bug reported: when running a Noble buildd image as a CI runner, the following error occurs ``` Running job phase... Running test:0 cmd_run.go:1129: WARNING: cannot create user data directory: cannot create snap home dir: mkdir /nonexistent: permission denied Sorry, home directories outside of /home needs configuration. See https://forum.snapcraft.io/t/11209 for details. ``` the buildd user is created with the following code in livecd- rootfs/live-build/buildd/02-user.chroot ``` # Create the buildd user and group. addgroup --gid 2501 buildd adduser --system --disabled-password --gecos 'Build Daemon user' \ --ingroup buildd --uid 2001 --shell /bin/bash buildd mkdir -p /build/buildd chown buildd:buildd /build/buildd ``` as of 24.04 (maybe earlier), adduser does not create a homedir for system users: > If no home directory is specified, the default home directory for a new system user is /nonexistent. This directory should never exist on any Debian system, and adduser will never create it automatically. on jammy and earlier images, the following ends up the user conf ``` buildd:x:2001:2501:Build Daemon user,,,:/home/buildd:/bin/bash ``` and on 24.04 ``` buildd:x:2001:2501:Build Daemon user,,,:/nonexistent:/bin/bash ``` this is fixed by adding an explicit `--home /home/buildd` to the user creation call ** 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/2083240 Title: buildd system user lacks homedir leading to issues with snaps[and more] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2083240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Changed in: livecd-rootfs (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Focal) Status: In Progress => 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/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
I've been running chromium:latest/beta since 20240918. I haven't had any issues, so it looks like whatever root cause, it gets fixed in beta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
echo $XDG_SESSION_TYPE wayland i noticed that i was behind a kernel update, so i moved up, saw it happen again on -45-generic switching to beta channel now to see if it reproduces there. I've also snagged a few more warnings that pop up in journal on first launch: ## apparmor denies: Sep 18 10:52:05 j5awry-sys76 systemd[5552]: snap.chromium.chromium-00d28d4e-d513-4f77-b311-14344af1ccdf.scope: Consumed 13.054s CPU time. Sep 18 10:52:13 j5awry-sys76 systemd[5552]: Started snap.chromium.chromium-be63e3af-7a12-4975-8c7d-b277acc9ea30.scope. Sep 18 10:52:13 j5awry-sys76 kernel: kauditd_printk_skb: 5 callbacks suppressed Sep 18 10:52:13 j5awry-sys76 kernel: audit: type=1400 audit(1726671133.971:708): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.chromium" name="/proc/80336/maps" pid=80336 comm="5" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1326 audit(1726671134.098:709): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=80380 comm="chrome" exe="/snap/chromium/2943/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x70a24661bf6b code=0x5 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1326 audit(1726671134.099:710): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=80381 comm="chrome" exe="/snap/chromium/2943/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x74e60047ef6b code=0x5 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1326 audit(1726671134.101:711): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=80315 comm="chrome" exe="/snap/chromium/2943/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=444 compat=0 ip=0x7ab48729988d code=0x5 ## GTK+ module issues Sep 18 10:52:14 j5awry-sys76 chrome[80315]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. Sep 18 10:52:14 j5awry-sys76 chrome[80315]: GTK+ module /snap/chromium/2943/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Sep 18 10:52:14 j5awry-sys76 chrome[80315]: Failed to load module "canberra-gtk-module" Sep 18 10:52:14 j5awry-sys76 chrome[80315]: GTK+ module /snap/chromium/2943/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. ## specific Vulkan related things Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:712): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:713): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:714): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:715): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:716): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 kernel: audit: type=1400 audit(1726671134.228:717): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=80419 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 18 10:52:14 j5awry-sys76 chromium_chromium.desktop[80315]: Sep 18 10:52:16 j5awry-sys76 chromium_chromium.desktop[80419]: [80419:80419:0918/105216.169561:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! Sep 18 10:52:16 j5awry-sys76 chromium_chromium.desktop[80419]: [80419:80419:0918/105216.175965:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! Sep 18 10:52:16 j5awry-sys76 chromium_chromium.desktop[80419]: [80419:80419:0918/105216.193302:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! -- Yo
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
nteodesio: just had the exact same crash, launching Chromium by clicking the icon on the dock (without discreet graphics). I'm in meetings 5-6 hours a day, so I can try just about any fashion you'd like me to launch. i'm also confused about that commandline being unsupported -- that's what clicking on the dock item shows in ps, with the graphics pieces removed, and trying to make it a base launch command not one of the tools (sorry if it's a bit off, as reading browser process trees confuses me sometimes). > airspeed velocity: African or European? it's in the notes about "raising a bug" with helpful commands and all that. guess a maintainer really like Monty Python :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] [NEW] Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
Public bug reported: ## Info chromium 128.0.6613.119 2943 latest/stablecanonical✓ snapd 2.6321759 latest/stablecanonical✓ Ubuntu 24.04 kernel - 6.8.0-41-generic ## hardware system76 gazelle 14" 2019 model ### GPU NVIDIA GeForce GTX 1660 Ti Driver Version: 535.183.01 ### CPU Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz ## webcams BisonCam, NBPro Microsoft LifeCam Studion (TM) ## other connected hardware C-Media Electronics Inc. AKG Ara USB Microphone ## Background First noticed on 20240916 journalctl filling up with ERROR:gl_utils.cc(415)] [.WebGL-0x21680d278700] GL_INVALID_OPERATION: Invalid query Id. this has happened when launching with "Launch with discreet graphics", launching via a simple commandline, or launching "normally" the command from "launch with discreet graphics" /snap/chromium/2943/usr/lib/chromium-browser/chrome --type=gpu-process --crashpad-handler-pid=655636 --enable-crash-reporter=,snap --change- stack-guard-on-fork=enable --gpu- preferences=UAAgAAAEAABgAAEAAQAAABAAEAAIAAgA --shared-files --field-trial- handle=3,i,9141409946131128162,11100357177403877201,262144 --disable- features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed- version ## Info logging snippet INFO:CONSOLE(195)] "WebGL: INVALID_OPERATION: endQuery: target query is not active", source: https://www.gstatic.com/video_effects/effects/673214282/videopipe_bundle.js (195) [666284:666284:0917/082204.295519:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082204.296983:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082210.871019:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [666284:666284:0917/082210.879465:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [666371:103:0917/082217.166630:WARNING:rtcp_receiver.cc(326)] OnPeriodicRttUpdate: Timeout: No RTCP RR received. [666284:666284:0917/082218.676804:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! I don't know if the first line, middle lines, and end lines are related, other than references to Web GL (other than the rtcp_receiver, which i just left because it was there...) ## Reproducer able to reproduce with good logging to commandline with: /snap/chromium/2943/usr/lib/chromium-browser/chrome --enable-crash- reporter=,snap --change-stack-guard-on-fork=enable --shared-files --disable-features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed-version --enable-logging=stderr ## Errata Quest: to make chromium work :) airspeed velocity: African or European? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: ## Info chromium 128.0.6613.119 2943 latest/stablecanonical✓ snapd 2.6321759 latest/stablecanonical✓ Ubuntu 24.04 kernel - 6.8.0-41-generic ## hardware system76 gazelle 14" 2019 model ### GPU NVIDIA GeForce GTX 1660 Ti Driver Version: 535.183.01 ### CPU Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz ## webcams - BisonCam, NBPro + BisonCam, NBPro Microsoft LifeCam Studion (TM) ## other connected hardware C-Media Electronics Inc. AKG Ara USB Microphone ## Background First noticed on 20240916 journalctl filling up with ERROR:gl_utils.cc(415)] [.WebGL-0x21680d278700] GL_INVALID_OPERATION: Invalid query Id. this has happened when launching with "Launch with discreet graphics", launching via a simple commandline, or launching "normally" the command from "launch with discreet graphics" /snap/chromium/2943/usr/lib/chromium-browser/chrome --type=gpu-process --crashpad-handler-pid=655636 --enable-crash-reporter=,snap --change- stack-guard-on-fork=enable --gpu- preferences=UAAgAAAEAABgAAEAAQAAABAAEAAIAAgA --shared-files --field-trial- handle=3,i,9141409946131128162,11100357177403877201,262144 --disable- features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed- version ## Info logging snippet INFO:CONSOLE(195)] "WebGL: INVALID_OPERATION: endQuery: target query is not active", source: https://www.gstatic.com/video_effects/effects/673214282/videopipe_bundle.js (195) [666284:666284:0917/082204.295519:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082204.296983:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id.
[Bug 2080223] Re: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline
adding cloud-images. if multiple artifacts are generated, the CPC pipeline will need to ensure that we download and transport all the livefs-build artifacts. ** Also affects: cloud-images 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/2080223 Title: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2080223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Changed in: livecd-rootfs (Ubuntu Noble) Status: New => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress ** Changed in: cloud-images Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Changed in: livecd-rootfs (Ubuntu Noble) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: livecd-rootfs (Ubuntu Jammy) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Description changed: cloud images are not currently producing spdx formatted SBOMs equally. Some builds do produce sboms continuously. all cloud images must produce SBOMs, across all Suites and products. # REQUIREMENTS # * Current calls to create_manifest in livecd-rootfs/live-build/functions must not break * sbom generation must only be done for ubuntu-cpc project. + # IMPACT # + + * will only affect `ubuntu-cpc` project + * will add the creation of a new file + * the SBOM requirement is part of Canonical's SSDLC efforts as well as partner contracts (multiple partners are requiring SBOMs for each generated artifact) + # TEST PLAN # * test all the ubuntu-cpc livecd-rootfs only hooks and series. ensure that an spdx formatted sbom, manifest, and filelist is generated and saved * test non-ubuntu-cpc hook and make sure that nothing is generated (check for calls of create_manifest. if they aren't even calling it, then it's safe) * test private ubuntu-cpc hooks. ensure that current calls to create_manifest are not broken + * test buildd builds to ensure no manifest is generated and no error is raised. - # POSSIBLE REGRESSIONS # + # POSSIBLE REGRESSIONS / WHERE PROBLEMS COULD OCCUR # * any hook calling create_manifest is at risk if there is an issue with create_manifest + * outside CPC specific hooks, the only build calling create_manifest is `buildd`. however this is not in the `ubuntu-cpc` project so it should skip the sbom generation. * any build where access to the snapstore is restricted, as this requires a snap - * NOTE: launchpad livefs builds have access to the snapstore + * NOTE: launchpad livefs builds have access to the snapstore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Description changed: cloud images are not currently producing spdx formatted SBOMs equally. Some builds do produce sboms continuously. all cloud images must produce SBOMs, across all Suites and products. + + # REQUIREMENTS # + + * Current calls to create_manifest in livecd-rootfs/live-build/functions must not break + * sbom generation must only be done for ubuntu-cpc project. + + # TEST PLAN # + * test all the ubuntu-cpc livecd-rootfs only hooks and series. ensure that an spdx formatted sbom, manifest, and filelist is generated and saved + * test non-ubuntu-cpc hook and make sure that nothing is generated (check for calls of create_manifest. if they aren't even calling it, then it's safe) + * test private ubuntu-cpc hooks. ensure that current calls to create_manifest are not broken + + # POSSIBLE REGRESSIONS # + * any hook calling create_manifest is at risk if there is an issue with create_manifest + * any build where access to the snapstore is restricted, as this requires a snap + * NOTE: launchpad livefs builds have access to the snapstore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] [NEW] cloud-images do not produce sboms
Public bug reported: cloud images are not currently producing spdx formatted SBOMs equally. Some builds do produce sboms continuously. all cloud images must produce SBOMs, across all Suites and products. ** Affects: cloud-images Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also 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/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051918] Re: Ubuntu CVE-2024-21626 runc vulnerability
** Changed in: cloud-images Status: In Progress => 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/2051918 Title: Ubuntu CVE-2024-21626 runc vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2051918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046486] Re: units with credentials fail in LXD containers
blech, sorry, misclicks trying to get things added properly marking as affects cloud-images as producers of the lxd images. ** Also affects: systemd Importance: Undecided Status: New ** No longer affects: systemd ** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046486 Title: units with credentials fail in LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072883] Re: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu
you can check any progress in Ubuntu by checking the issue tracker https://ubuntu.com/security/CVE-2024-24790 https://ubuntu.com/security/CVE-2024-24791 it looks like 2024-24690 is fixed, so may be a false-positive. 24791 is still in needs-triage on the page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072883 Title: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
I've set this to incomplete for now. @air-awan, if you have time to give an update related to vmware environments, let me know. i double checked, and the addition of the serial port was requested by the vmware team, so if it's breaking things now due to hypervisor level issues, I'll have to sync with vmware to figure out the appropriate fix. ** Changed in: cloud-images Status: New => Incomplete ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056065] Re: cloud images slow to boot under kvm
** 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/2056065 Title: cloud images slow to boot under kvm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
** Changed in: cloud-images 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/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072929] Re: Ubuntu cloud image partition numbering
** Changed in: cloud-images Status: New => Confirmed ** Changed in: cloud-images/oracular Status: New => Confirmed ** Changed in: cloud-images Importance: Undecided => High ** Changed in: cloud-images/oracular Importance: Undecided => High ** Changed in: cloud-images Assignee: (unassigned) => Simon Poirier (simpoir) ** Changed in: cloud-images/oracular Assignee: (unassigned) => Simon Poirier (simpoir) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072929 Title: Ubuntu cloud image partition numbering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072883] Re: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu
`gosu` is a universe package in Ubuntu, and from what i can see was inherited from `side` at version 1.17.1 https://packages.debian.org/sid/gosu I see no open bugs against `gosu` : https://bugs.debian.org/cgi- bin/pkgreport.cgi?src=gosu , and it needs to be confirmed that it's built against golang 1.17 in `debian`. Not my expertise normally the correct move would be to go upstream first. Since i control things on the Ubuntu side for cloud-images, i'll move the ticket around there. I'll also make it public as it's not a new security vulnerability (private security bugs are for new disclosures, not for tracking already announced vulnerabilities). Public Ubuntu tracking of the golang vulnerability: https://ubuntu.com/security/CVE-2024-24790 Note, since this is reported against Noble, i _believe_ this is an incorrect match. I'm working on double checking, but in noble, the golangs have been patched (both 1.21 and 1.22) It's likely a bad version string match. but i've listed this against `gosu` for someone to double check my assertions. `gosu` in noble is building against `golang- go=1.22` http://archive.ubuntu.com/ubuntu/pool/universe/g/gosu/gosu_1.17-1.dsc ** Also affects: gosu (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-24790 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072883 Title: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072929] Re: Ubuntu cloud image partition numbering
** Also 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/2072929 Title: Ubuntu cloud image partition numbering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812752] Re: UX: changing GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub has no effect in cloud images
I disagree racb -- using the `.d` directory is generally the approach CPC has used for all configuration. that way users can easily see what is package maintained and what is changed in the build process. I don't think the suggestion that CPC change that general guidance because grub.d is less well known that other `.d` directories is a strong rationale. It seems fairly "normal" for Ubuntu packages to have $PACKAGE_CONF.d directories to add additional configuration. I think mkukri has the correct solution. we should add a comment to the top level file, and ensure all man pages correctly state how the grub handles the `.d` directory. And any official Ubuntu docs should be updated. we can't change the history of everyone that's posted online about every version of Ubuntu, but changing how we configure things because information online isn't strictly correct (because it predates grub.d, posters didn't know about grub.d, etc) doesn't seem like strong reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812752 Title: UX: changing GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub has no effect in cloud images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1812752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023758] Re: Updating guest additions on ubuntu/focal64 hits timeout
Virtualbox in focal and jammy (20.04 and 22.04) has migrated to 6.1.50-dfsg-1~ubuntu1.20.04.1 reminder that virtualbox is a multiverse package, meaning it relies on community support at this time. Since we ar eon 6.1.x in 22.04 and 20.04, users can expect bugfixes and security fixes from the community through the lifetime of standard support. with extended support via Ubuntu Pro, universe (and multiverse) may also be covered in security updates. Based on previous discussion, it looks like using the Ubuntu supplied GuestAdditions works. this is shipped as part of the image, and works in a matchup with Ubuntu hosts. Vagrant images have community level support, where we do our best to help debug issues. Since it looks like reverting to the Ubuntu version of guest additions works, I'll be closing this ticket. We are also working on having more public docs for the community available here: https://documentation.ubuntu.com/public- images/en/latest/public-images-how-to/ you can see examples of building and running vagrant, as well as more information about what we can best support. We welcome community contributions to the documentation ** Changed in: virtualbox-guest-additions (Ubuntu) Status: New => Invalid ** Changed in: virtualbox (Ubuntu) Status: New => Invalid ** Changed in: cloud-images 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/2023758 Title: Updating guest additions on ubuntu/focal64 hits timeout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2023758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
Thank you for checking Aditya. I'll leave this open till you get some guidance from VMware regarding any changes in Cloud Director that may be affecting serial console connections. I've also added this to our 24.04 release notes (to be published soon for the clouds). Thank you a bunch for trying out 24.04 so that we can help others if they see this as well! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
1. what versions of VMware ESXi is this applicable? 2. is this reproducible in other environments, such as Virtualbox? 3. is this error true of all ubuntu images for those versions then? This was added in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1895104 at the request of vmware 4. I have a worry that removing serial port may cause issues in other deployment areas, such as Virtualbox, and possibly other versions of ESXi. Could a full test plan be provided to ensure compatibility? This is also tightly coupled to this ticket, in which i requested a meeting and documentation, and it hasn't occurred yet: https://bugs.launchpad.net/ubuntu/+bug/1898871 NOTE: this is after Release Freeze so there is a change this does _not_ get fixed prior to the 24.04 release next week. If we cannot work out a fix, we will release note this issue and work on releasing as soon as possible ** Also 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/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895104] Re: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi
** Changed in: cloud-images Status: Confirmed => 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/1895104 Title: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
@DisatesR : if you're not seeing a 50-cloud-init.conf file, it indicates to me that cloud-init is failing to parse the cloud_init configuration properly, and thus not adding the required configuration to /etc/ssh/sshd_config.d/ could you provide your entire cloud config? you can also use cloud-init to verify your user-data https://cloudinit.readthedocs.io/en/latest/howto/debug_user_data.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046154] Re: [MIR] libcryptx-perl (libmail-dkim-perl dependency)
Alternative idea, what about instead of writing a wrapper: 1. look at https://packages.ubuntu.com/noble/libnet-ssleay-perl a. libnet-ssleay-perl is in main 2. add eddsa-25519 to the list of constants upstream a. if i'm reading correctly, there's a mapping in a helper_scripts/constants.txt that contains a list of all algorithms, that is then used to autgen C and perl bindings. if libssl or libgrypt on the system already has eddsa-25519, it should "just work" 3. switch to using libnet-ssleay-perl for the backend of these calls a. bonus, you could see if you could switch _everything_. it'd make sense to me... I don't know if this ends up being a heavier or lighter lift. and it takes updating libnet-ssleay-perl upstream, but reading the list of constants, it could benefit from someone going through and fleshing out current libssl and libcrypt support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046154 Title: [MIR] libcryptx-perl (libmail-dkim-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/2046154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
Tested working on the image from http://cloud- images.ubuntu.com/releases/jammy/release-20240319/ $ ssh -o "UserKnownHostsFile=/dev/null -o CheckHostIP=no StrictHostKeyChecking no" jchittum@0.0.0.0 -p The authenticity of host '[0.0.0.0]: ([0.0.0.0]:)' can't be established. ED25519 key fingerprint is This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '[0.0.0.0]:' (ED25519) to the list of known hosts. jchittum@0.0.0.0's password: Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro System information as of Mon Apr 1 11:55:56 UTC 2024 $ ls /etc/ssh/sshd_config.d/ 50-cloud-init.conf 60-cloudimg-settings.conf $ sudo cat /etc/ssh/sshd_config.d/50-cloud-init.conf PasswordAuthentication yes $ sudo cat /etc/ssh/sshd_config.d/60-cloudimg-settings.conf PasswordAuthentication no cloud-init and passwords is a bit confusing. here is a working example of a cloud-init: #cloud-config ssh_pwauth: true users: - name: jchittum groups: [adm, lxd, sudo] passwd: sudo: ALL=(ALL) NOPASSWD:ALL shell: /bin/bash lock_passwd: false - name: timmy groups: [adm, lxd, sudo, cdrom, dip] ssh_import_id: lp:jchittum sudo: ALL=(ALL) NOPASSWD:ALL passwd: shell: /bin/bash lock_passwd: false NOTES: passwd was set by running : mkpasswd --method=SHA-512 --rounds=50 lock_passwd: false is _required_ to make this work. otherwise providing a password won't do anything, and you'll never be able to log in. I'm wondering if it's from a different version of cloud-init instead? 20231211: cloud-init 23.3.3-0ubuntu0~22.04.1 20240319: cloud-init 23.4.4-0ubuntu0~22.04.1 i don't see anything related in the changelog[https://github.com/canonical/cloud-init/blob/main/ChangeLog] next steps: try a coud-init config like i have above. If it fails, please provide your cloud-init and outputs (especially helpful with some cloud-init logs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
@DisasteR -- could you be more specific? Which images are you seeing this in? which cloud, which download from `cloud-images.ubuntu.com`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059730] [NEW] Focal 5.15 kernel apparmor mismatch missing snap_validate_preseed functionality in livecd-rootfs
Public bug reported: kernel bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384 introduced an apparmor change to the 5.15. This rolled down to the Focal HWE 5.15 kernel, causing failures to properly snap seed The original functionality was added into ubuntu/master and ubuntu/jammy with this bug: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2015596 which happened during the HWE roll to the 5.19 kernel. There was an assumption that a breaking change like this would not affect Focal, as rolls were done. However, 2045384 shows that this is not necessarily true. To fix 2045384, a backport to focal of the functionality in snap_validate_seed allowing matching on kernel version, and the creation of kernel specific directories is required [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] * for focal build any cloud image with preseeded snaps with HWE 5.15 kernel * boot * run `snap debug seeding` * 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 ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Description changed: kernel bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384 introduced an apparmor change to the 5.15. This rolled down to the Focal HWE 5.15 kernel, causing failures to properly snap seed The original functionality was added into ubuntu/master and ubuntu/jammy with this bug: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2015596 which happened during the HWE roll to the 5.19 kernel. There was an assumption that a breaking change like this would not affect Focal, as rolls were done. However, 2045384 shows that this is not necessarily true. To fix 2045384, a backport to focal of the functionality in snap_validate_seed allowing matching on kernel version, and the creation of kernel specific directories is required + + [ Impact ] + + Boot will be slowed by ~200ms until this is resolved in livecd-rootfs + + [ Test Plan ] + + * for focal build any cloud image with preseeded snaps with HWE 5.15 kernel + * boot + * run `snap debug seeding` + * 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/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
The statement in the bug was correct -- we had not anticipated or
thought an apparmor change would get backported to an LTS branch that
would necessitate the backport of the functionality in
`snap_validate_seed`. but now we have a break, where the HWE of focal
(5.15) and LTS of jammy (5.15) got changed to include things.
What is really required is the functionality added to match on
${kern_major_min}, so it's a few commits / bugs deep.
goes back to the origin commit in ubuntu/jammy :
bd1690bd16c70f9631ee2798514b51ed2dc973d5
which was never backported because there weren't going to be new kernel
versions of 20.04 (5.15 was already out) and we didn't believe there'd
be an addition to apparmor that'd break it:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2015596
and follow up:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2024639
So, i'd say, no, it's not about fixing LP #2038957 specifically, it's
about how a kernel change caused us to require the functionality to
special case on kernel version. Actually, the original bug doesn't say
anything about focal:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384
so this may be a _side effect_. Let me ping that ticket quickly to see
if it was intentional to release this to 20.04 5.15 (it's abnormal to
put something in LTS Kernel and then _not_ in HWE of $PREVIOUS_SUITE,
but it's not listed on the bug)
--
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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Question -- this has landed in various jammy-5.15 kernels. This rolled downstream to the focal HWE kernels (specifically the cloud kernels) 1. was this intentional? 2. if so, could we add an affects for focal as well? it'll help us with tracking downstream dependency changes, specifically in livecd-rootfs: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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
** Tags added: verification-needed -- 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
** Tags added: verification-done-jammy -- 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
Verified Jammy:
Steps:
1. using bartender, built an image using the livecd-rootfs 2.765.41 code
pulled from https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.41
bartender \
--hook-extras-branch jammy \
--livecd-rootfs-dir
/home/jchittum/dev01/troubleshooting/various-rootfs/2.765.41/livecd-rootfs \
--build-provider aws \
--aws-keypair-name ${AWS_BUILD_KEY} \
--aws-profile image_builder \
-- \
--series jammy \
--project ubuntu-cpc \
--image-target qcow2
### NOTE ###
You don't have to provide hook-extras-branch build a qcow2. I just default to
always using it...
2. untarred the contents
3. launched with QEMU
qemu-system-x86_64 \
-cpu host -machine type=q35,accel=kvm -m 2048 \
-nographic \
-snapshot \
-netdev id=net00,type=user,hostfwd=tcp::-:22 \
-device virtio-net-pci,netdev=net00 \
-drive if=virtio,format=qcow2,file=livecd.ubuntu-cpc.img \
-cdrom cloud_init.iso \
-bios /usr/share/OVMF/OVMF_CODE.fd
### NOTE ###
cloud-init.iso just adds my ssh key into the image.
4. logged in and ran `sudo snap debug seeding`
sudo snap debug seeding
seeded:true
preseeded: true
image-preseeding: 8.498s
seed-completion: 1.823s
5. and just to double check, yes there are snaps
snap list
NameVersionRevTracking Publisher Notes
core20 20240111 2182 latest/stable canonical✓ base
lxd 5.0.3-babaaf8 27948 5.0/stable/… canonical✓ -
snapd 2.61.2 21184 latest/stable canonical✓ snapd
** Tags removed: verification-needed verification-needed-jammy
** 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 ]
* 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
+ * for jammy build any cloud image with preseeded snaps with up to date 5.15
kernel
* boot
- * run `snap debug preseed`
+ * run `snap debug seeding`
* 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 2057776] Re: ubuntu-cpc project remove armhf vm images until grub2 armhf fixes in place
** Description changed: grub-efi-arm and grub-efi-arm-bin are not currently installable for armhf images. This leads to build failures for in the disk-image- uefi.binary in the ubuntu-cpc image. the future of UEFI booting armhf cloud images is currently in question, with possibilities including: 1. removing VM images entirely for armhf (due to lack of hardware support) 2. keeping a Bios booting VM available for armhf (need to check booting on appropriate devices, such as an older Raspberry Pi) 3. fixing grub-efi-arm and grub-efi-arm-bin and re-enabling UEFI booting armhf cloud images. - - In the short term, removing armhf from the list of supported architectures results in skipping the hook. + In the short term, removing armhf from the list of supported + architectures results in skipping the hook. ### Testing The required change must be tested with a Launchpad built livecd-rootfs. + + ### NOTE ### + + This is not for SRU, only noble forward at this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057776 Title: ubuntu-cpc project remove armhf vm images until grub2 armhf fixes in place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2057776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057776] [NEW] ubuntu-cpc project remove armhf vm images until grub2 armhf fixes in place
Public bug reported: grub-efi-arm and grub-efi-arm-bin are not currently installable for armhf images. This leads to build failures for in the disk-image- uefi.binary in the ubuntu-cpc image. the future of UEFI booting armhf cloud images is currently in question, with possibilities including: 1. removing VM images entirely for armhf (due to lack of hardware support) 2. keeping a Bios booting VM available for armhf (need to check booting on appropriate devices, such as an older Raspberry Pi) 3. fixing grub-efi-arm and grub-efi-arm-bin and re-enabling UEFI booting armhf cloud images. In the short term, removing armhf from the list of supported architectures results in skipping the hook. ### Testing The required change must be tested with a Launchpad built livecd-rootfs. ** 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/2057776 Title: ubuntu-cpc project remove armhf vm images until grub2 armhf fixes in place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2057776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
upstream commit in `crun` : https://github.com/containers/crun/pull/1309/commits/57262a2710c83fa08767f0ce3ba7a80993515bb2 I think a trivial reproducer, outside GH runners, is * start a system with a 6.5 kernel (for a VM downloaded from cloud-images, need to install the HWE kernel. or start on your favourite $BIG_CLOUD as they should have all rolled. Azure is an environment) * install podman from Ubuntu 22.04 archive * try to run a container That _should_ be it, if I'm reading everything correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04
** Description changed: The problem is very well described in https://github.com/actions/runner- images/issues/9425. + + ## COPY FROM LINK + + I think there might be a regression in this release of the ubuntu-22.04 + image which breaks podman.[1] + + The image updated the kernel from 6.2.y to 6.5.y, but podman/crun don't + seem to be updated. + + Our build fails with this error link to run:[2] + + STEP 1/1: FROM ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac + Trying to pull ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac... + Getting image source signatures + Copying blob sha256:041b542221cfde2f9fa4ac13f8b5804e25b23ab48ba47db2822c382a134256e1 + Copying blob sha256:041b542221cfde2f9fa4ac13f8b5804e25b23ab48ba47db2822c382a134256e1 + Copying config sha256:1eba10d0345cc6df78b7c3a6ced45da9db675d05eb20d5d286996e4f7ffb24d5 + Writing manifest to image destination + Storing signatures + COMMIT localhost/builder + --> 1eba10d0345 + Successfully tagged localhost/builder:latest + Successfully tagged ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac + 1eba10d0345cc6df78b7c3a6ced45da9db675d05eb20d5d286996e4f7ffb24d5 + Error: OCI runtime error: chmod `run/shm`: Operation not supported + Error: Process completed with exit code 126. + + This is with this image version: + + Current runner version: '2.313.0' + Operating System + Ubuntu + 22.04.4 + LTS + Runner Image + Image: ubuntu-22.04 + Version: 20240225.1.0 + Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240225.1/images/ubuntu/Ubuntu2204-Readme.md + Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240225.1 + + Trying to reproduce, it seems like I am only able to get this image + version 20240218.1.0 where the issue does not appear. + + Tried to reproduce in this repo[3], but I'm not able to get this with + image version 20240225.1.0. + + Is this a known issue and version 20240225.1.0 is not in use anymore? + + This blog post seems to suggest that the crun version is too old.[4] + + [1]https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240225.1 + [2]https://github.com/gardenlinux/gardenlinux/actions/runs/8061893233/job/22020522535 + [3]https://github.com/fwilhe/turbo-lamp/blob/main/.github/workflows/podman.yml + [4]https://noobient.com/2023/11/15/fixing-ubuntu-containers-failing-to-start-with-systemd/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04
** Also affects: libpod (Ubuntu) Importance: Undecided Status: New ** Also affects: crun (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/2056442 Title: Podman (crun) regression in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout
Kinetic Vagrant image is available at : https://app.vagrantup.com/ubuntu/boxes/kinetic64 for a fresh install quickly vagrant init ubuntu/kinetic64 vagrant up This image should work on all versions of Vagrant available in Ubuntu archives. I'll spin some VMs and do more testing, but community help is appreciated. Once a few versions of Vagrant and hosts are verified, we'll be able to do an SRU to Jammy Testing ** Host: Ubuntu 22.04 Vagrant: 2.2.19 Virtualbox: 6.1 VBox Guest Additions: 6.0.0 r127566 successful boot and ssh. no errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969664 Title: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974100] Re: qemu ide/sata disks do not work well with discard/trim
I haven't come across this before. Our builds for the cloud images from
cloud-images.ubuntu.com have the following cleanup code run that should
be preventing this sort of thing:
https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n231
hard to read exact ramifications, but the gist is we create a
filesystem, mount it, create the image, then at the end during clean up
we run
# rootfs_dev_mapper is set in https://git.launchpad.net/livecd-
rootfs/tree/live-build/functions#n62 when mounting an image
e2fsck -y -E discard ${rootfs_dev_mapper}
zerofree ${rootfs_dev_mapper}
before running kpartx to remove the mount
this _should_ be discarding the empty blocks. That matches the
expectation b1 and b2.
But I haven't seen
> The cloudimage extended and used as root grows more lost blocks (seems
like 5 MB above)
so that bears investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974100
Title:
qemu ide/sata disks do not work well with discard/trim
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1974100/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971788] Re: Failure to enable SSL out of the box when in fips mode
Data points provided: using an 18.04 Bionic FIPS cloud image, doing ``` apt-get update && apt-get install mysql-server mysql-client ``` successfully installs the server and client, and enables TLS properly for the FIPS environment. There may be a difference in packaging scripts between mysql-5.7 and mysql-8.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971788 Title: Failure to enable SSL out of the box when in fips mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1971788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971532] [NEW] [snap] Firefox Save File Unable To Paste Into Filename
Public bug reported: related to a few other bug reports: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168 Save File prompt disallows paste to filename. Attached is a screenshot of what pops up. Tested in various directories. Info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy uname -a Linux j5awry-sys76 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux snap version snap2.55.3+22.04ubuntu1 snapd 2.55.3+22.04ubuntu1 series 16 ubuntu 22.04 kernel 5.15.0-27-generic snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: 21 days ago, at 14:48 CDT ... installed: 99.0.1-1 (1232) 163MB - (tracking latest/stable) Reproduction: Download a file to get file prompt Cut the name attempt to paste the name back in Reproducible when targeting ~/Downloads, ~/Documents, and /tmp ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "firefox_paste_disallow.png" https://bugs.launchpad.net/bugs/1971532/+attachment/5586514/+files/firefox_paste_disallow.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971532 Title: [snap] Firefox Save File Unable To Paste Into Filename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout
** Also 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/1969664 Title: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553119] Re: vagrant box for vivid64 missing on https://vagrantcloud.com/ubuntu/boxes/vivid64
** Changed in: vagrant 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/1553119 Title: vagrant box for vivid64 missing on https://vagrantcloud.com/ubuntu/boxes/vivid64 To manage notifications about this bug go to: https://bugs.launchpad.net/vagrant/+bug/1553119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965180 Title: apt-add-repository requires --login for private repos, breaking automated workflows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965180] [NEW] apt-add-repository requires --login for private repos, breaking automated workflows
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 Packages
[3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main Translation-en
[1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu jammy main"
Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, in
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
429, in _request
raise error
lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
Response headers:
---
-content-encoding: gzip
content-length: 91
content-type: text/plain;charset=utf-8
date: Wed, 16 Mar 2022 19:54:16 GMT
server: gunicorn/19.8.1
status: 404
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
---
Response body:
---
b"Object: ,
name: '$REPO'"
---
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, in
description
return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, in
lpppa
raise ShortcutException(msg)
softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa
'$REPO/proposed' not found (use --login if private)
Impish similarly breaks. Digging through changelogs, I see various
entries in Impish forward, starting with version 0.99.0 where a refactor
was done.
using `--login` is not possible in an automated setup (such as a
builder) as it starts an OAuth dance, which requires human interaction.
this will break existing automation utilizing apt-add-repository for
users when migrating to Jammy
** Affects: software-properties (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/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960537] Re: umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
package from https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.57, the Bionic upload has been verified against a currently
failing CPC build
1. downloaded package
2. untarred locally
3. checked out CPC's extras code for Bionic(cpc_packaging.extra)
4. using `ubuntu-old-fashioned` , executed a build for CPC's azure hook:
bartender --hook-extras-dir ~/dev01/cloudware/cpc_packaging.extra
--livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-
rootfs/2.525.57/livecd-rootfs --build-provider aws --aws-keypair-name
jchittum-cpc-jenkins -- --series impish --project ubuntu-cpc --image-
target azure
5. Observed the sleep 30 was run in the build log
6. observed that the Azure hook completed successfully
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-impish
** Tags added: verification-done-bionic verification-done-focal
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/1960537
Title:
umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960537] Re: umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
package from https://launchpad.net/ubuntu/+source/livecd-rootfs/2.664.38
, the Focal upload has been verified against a currently failing CPC
build
1. downloaded package
2. untarred locally
3. checked out CPC's extras code for Focal (cpc_packaging.extra)
4. using `ubuntu-old-fashioned` , executed a build for CPC's azure hook:
bartender --hook-extras-dir ~/dev01/cloudware/cpc_packaging.extra
--livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-
rootfs/2.664.38/livecd-rootfs --build-provider aws --aws-keypair-name
jchittum-cpc-jenkins -- --series impish --project ubuntu-cpc --image-
target azure
5. Observed the sleep 30 was run in the build log
6. observed that the Azure hook completed successfully
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960537
Title:
umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960537] Re: umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
package from https://launchpad.net/ubuntu/+source/livecd-rootfs/2.742.3
, the Impish upload has been verified against a currently failing CPC
build
1. downloaded package
2. untarred locally
3. checked out CPC's extras code for Impish (cpc_packaging.extra)
4. using `ubuntu-old-fashioned` , executed a build for CPC's azure hook:
bartender --hook-extras-dir ~/dev01/cloudware/cpc_packaging.extra
--livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-
rootfs/2.742.3/livecd-rootfs --build-provider aws --aws-keypair-name
jchittum-cpc-jenkins -- --series impish --project ubuntu-cpc --image-
target azure
5. Observed the sleep 30 was run in the build log
6. observed that the Azure hook completed successfully
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960537
Title:
umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960537] [NEW] umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
Public bug reported:
When running builds locally or within launchpad, cloud-images are
starting to fail in many places with the following error:
```
+ udevadm settle
+ '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']'
+ '[' -e /etc/mtab ']'
+ e2fsck -y -E discard /dev/mapper/loop0p1
e2fsck 1.45.5 (07-Jan-2020)
/dev/mapper/loop0p1 is in use.
e2fsck: Cannot continue, aborting.
```
This call happens on calls to `umount_disk_image` which then calls
`umount_partition`.
`dmsetup info` reports (as an example)
```
Name: loop3p1
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:1
Event number: 0
Major, minor: 253, 0
Number of targets: 1
UUID: part1-devnode_7:3_Wh5pYvM
```
This shows that there's an open file handle on loop3p1.
This was first noticed in Jammy builds. After a fair amount of debugging
by jchittum, no root cause was found. However, a workaround was added to
the failing CPC hook:
sleep 30
Trial and error found that shorter sleeps still failed.
Due to the ephemeral nature, I [jchittum] have been unable to find a
root cause. The file handle cleans itself up quickly enough that even
when I'm on a node watching the build, I haven't been able to track down
an exact cause due to the handle releasing in a short time.
** 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/1960537
Title:
umount_partition e2fsck call fails with ${rootfs_dev_mapper} in use
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1960537/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898871] Re: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5)
Thank you for providing more information. Is it possible to find out what sections of the OVF to change without having to boot an image in vsphere? It'd be wonderful to have documentation of generally available configurations and descriptions. I check the primary source document, but it's difficult to use to answer questions such as "how do I make a serial console not available automatically" https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf Does VMWare provide guidance on editing OVF files outside of booting an image, making a change, and exporting? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898871 Title: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1898871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898871] Re: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5)
vmware-gos-Yuhua : what is the corresponding ovf template entry for Connected At Power On? We generate all builds in a chroot, with a templated OVF, so we need to identify the exact stanza. What we have now is: https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- cpc/hooks.d/base/ovf/ubuntu-ova-v1-vmdk.tmpl#n87 true serial0 4 vmware.serialport.device 21 Generally speaking, is there a place to look up all the possible values? I keep going to https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf but that doesn't include a full list of the things that'd full under type options, nor what values may be possible (such as vmware.serialport.device). Could you help by pointing to a resource? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898871 Title: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1898871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
with the release of bug 1949116 this morning, I was able to verify the hirsute change 1. downloaded source package of https://launchpad.net/ubuntu/+source/livecd-rootfs/2.719.2 2. untarred locally 3. executed a local build using ubuntu-old-fashioned I see livecd.ubuntu-desktop-hyperv.vhdx.zip.manifest. thank you brian-murray and sil2100 for unblocking things! ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
I've attempted to build hyperv-desktop from currently livecd-rootfs for Hirsute, and i run into the same issue: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable libxatracker2 : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable mesa-vulkan-drivers : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable The issue is not created via a change in livecd-rootfs (which I had presumed, but wanted to double check). I'm also generally confused as installing mesa-vulcan-drivers, libxatracker2, or libgl1-mesa-dri into a hirsute lxd container or VM does not result in this error. I can dig further into packaging, but it seems to be isolated to installing in this environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
I have verified bionic by doing the following: 1. downloaded source package of https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.56 2. untarred locally 3. executed a local build using ubuntu-old-fashioned I see that there is a livecd.ubuntu-desktop-hyperv.vhdx.zip.manifest produced at the end of the build, and that it has correct packages ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic 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/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940136] Re: HyperV images do not include package manifests
I am unable to confirm Hirsute due to an unrelated issue. During the base install of the chroot on Hirsute, there is a failure for mesa drivers command: lb_chroot_install-packages install --- shared-mime-inf ignore old unsatisfied important dependency on libnss-nis:amd64 ignore old unsatisfied important dependency on libnss-nisplus:amd64 ignore old unsatisfied important dependency on e2fsprogs-l10n:amd64 ignore old unsatisfied important dependency on libgpg-error-l10n:amd64 ignore old unsatisfied important dependency on update-motd:amd64 Installing gir1.2-clutter-1.0:amd64 as Depends of gnome-shell-extension-desktop-icons-ng:amd64 Installing gir1.2-cogl-1.0:amd64 as Depends of gir1.2-clutter-1.0:amd64 Installing gir1.2-coglpango-1.0:amd64 as Depends of gir1.2-clutter-1.0:amd64 Installing gir1.2-clutter-gst-3.0:amd64 as Depends of gnome-shell-extension-desktop-icons-ng:amd64 Installing gir1.2-gtkclutter-1.0:amd64 as Depends of gnome-shell-extension-desktop-icons-ng:amd64 libgl1-mesa-dri:amd64 Depends on libllvm12:amd64 < none @un H > (>= 1:9~svn298832-1~) can't be satisfied! mesa-vulkan-drivers:amd64 Depends on libllvm12:amd64 < none @un H > (>= 1:9~svn298832-1~) can't be satisfied! libxatracker2:amd64 Depends on libllvm12:amd64 < none @un H > (>= 1:9~svn298832-1~) can't be satisfied! Installing linux-image-generic:amd64 as Depends of linux-generic:amd64 Installing linux-image-5.11.0-38-generic:amd64 as Depends of linux-image-generic:amd64 Installing linux-modules-5.11.0-38-generic:amd64 as Depends of linux-image-5.11.0-38-generic:amd64 Installing grub-pc:amd64 as Recommends of linux-image-5.11.0-38-generic:amd64 Installing grub-common:amd64 as Depends of grub-pc:amd64 Installing os-prober:amd64 as Recommends of grub-common:amd64 Installing grub2-common:amd64 as Depends of grub-pc:amd64 Installing grub-pc-bin:amd64 as Depends of grub-pc:amd64 Installing grub-gfxpayload-lists:amd64 as Depends of grub-pc:amd64 Installing linux-modules-extra-5.11.0-38-generic:amd64 as Depends of linux-image-generic:amd64 Installing crda:amd64 as Depends of linux-modules-extra-5.11.0-38-generic:amd64 Installing iw:amd64 as Depends of crda:amd64 Installing linux-firmware:amd64 as Depends of linux-image-generic:amd64 Installing intel-microcode:amd64 as Depends of linux-image-generic:amd64 Installing iucode-tool:amd64 as Depends of intel-microcode:amd64 Installing amd64-microcode:amd64 as Depends of linux-image-generic:amd64 Installing thermald:amd64 as Recommends of linux-image-generic:amd64 Installing linux-headers-generic:amd64 as Depends of linux-generic:amd64 Installing linux-headers-5.11.0-38-generic:amd64 as Depends of linux-headers-generic:amd64 Installing linux-headers-5.11.0-38:amd64 as Depends of linux-headers-5.11.0-38-generic:amd64 --- leads to: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable libxatracker2 : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable mesa-vulkan-drivers : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable However, this is not an issue with code change under test. I'll look into if there are open bugs related to this on Hirsute somewhere already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940136 Title: HyperV images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
The latest lxd rootfs have been tested and daily images have been released. ** Changed in: cloud-images Status: In Progress => 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/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
I've tested the proposed upload on a pple64 and s390x systems. I used the following procedure 1. lxc launch ubuntu-daily:impish test-i-update 2. lxc shell test-i-update 3. enabled proposed in /etc/apt/sources.list 4. apt update 5. apt install snapd Get:1 http://ports.ubuntu.com/ubuntu-ports impish-proposed/main s390x snapd s390x 2.53+21.10ubuntu1 Get:1 http://ports.ubuntu.com/ubuntu-ports impish-proposed/main ppc64el snapd ppc64el 2.53+21.10ubuntu1 6. exit && lxc restart test-i-update 7. lxc shell test-i-update 8. snap changes observed Done state for Initialize system state instead of Error 9. snap debug seeding observed seeding completed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
ls -lah /lib64/ld64.so.2 on ppcle64 impish, hirsute On Impish ls -lah /lib64/ld64.so.2 lrwxrwxrwx 1 root root 36 Sep 2 21:26 /lib64/ld64.so.2 -> /lib/powerpc64le-linux-gnu/ld64.so.2 Hirsute: ls -lah /lib64/ld64.so.2 lrwxrwxrwx 1 root root 37 Mar 31 2021 /lib64/ld64.so.2 -> /lib/powerpc64le-linux-gnu/ld-2.33.so -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
ppcle64 hirsute lxd journalctl ** Attachment added: "ppc_hirsute_lxd_journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944004/+attachment/5531325/+files/ppc_hirsute_lxd_journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
ppcle64 outputs:
lxc ubuntu-daily:impish
ls -lah /usr/lib/ld64.so.1
ls: cannot access '/usr/lib/ld64.so.1': No such file or directory
ldd /usr/lib/snapd/snap-confine
linux-vdso64.so.1 (0x7fd86005)
libudev.so.1 => /lib/powerpc64le-linux-gnu/libudev.so.1 (0x7fd85ff7)
libc.so.6 => /lib/powerpc64le-linux-gnu/libc.so.6 (0x7fd85fcf)
/lib64/ld64.so.2 (0x7fd86006)
snap debug seeding
seeded: false
seed-error: |
cannot perform the following tasks:
- Run install hook of "lxd" snap if present (run hook "install": signal:
segmentation fault)
preseeded: true
image-preseeding: 4.51s
seed-completion: –
preseed-system-key: {
"apparmor-features": [
"caps",
"dbus",
"domain",
"file",
"mount",
"namespaces",
"network",
"network_v8",
"policy",
"ptrace",
"query",
"rlimit",
"signal"
],
"apparmor-parser-features": [
"qipcrtr-socket",
"unsafe"
],
"apparmor-parser-mtime": 1628490219,
"build-id": "e09cf7be4df8b799f8e788659c66fe1bb79404cc",
"cgroup-version": "2",
"nfs-home": false,
"overlay-root": "",
"seccomp-compiler-version": "bb391d0fd29f0bc97f0a62a4dcdd58abcdd57620 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-actlog",
"seccomp-features": [
"allow",
"errno",
"kill_process",
"kill_thread",
"log",
"trace",
"trap",
"user_notif"
],
"version": 10
}
seed-restart-system-key: {
"apparmor-features": [
"caps",
"dbus",
"domain",
"file",
"mount",
"namespaces",
"network",
"network_v8",
"policy",
"ptrace",
"query",
"rlimit",
"signal"
],
"apparmor-parser-features": [
"qipcrtr-socket",
"unsafe"
],
"apparmor-parser-mtime": 1628490219,
"build-id": "e09cf7be4df8b799f8e788659c66fe1bb79404cc",
"cgroup-version": "1",
"nfs-home": false,
"overlay-root": "",
"seccomp-compiler-version": "bb391d0fd29f0bc97f0a62a4dcdd58abcdd57620 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-actlog",
"seccomp-features": [
"allow",
"errno",
"kill_process",
"kill_thread",
"log",
"trace",
"trap",
"user_notif"
],
"version": 10
}
snap changes
ID Status Spawn Ready Summary
1Error yesterday at 18:32 UTC today at 15:16 UTC Initialize system state
2Donetoday at 15:16 UTC today at 15:16 UTC Initialize device
3Error today at 15:21 UTC today at 15:21 UTC Initialize system state
4Error today at 15:26 UTC today at 15:27 UTC Initialize system state
5Error today at 15:32 UTC today at 15:32 UTC Initialize system state
6Error today at 15:37 UTC today at 15:37 UTC Initialize system state
7Error today at 15:42 UTC today at 15:43 UTC Initialize system state
8Error today at 15:47 UTC today at 15:48 UTC Initialize system state
9Error today at 15:53 UTC today at 15:53 UTC Initialize system state
On Hirsute:
ls -lah /usr/lib/ld64.so.1
ls: cannot access '/usr/lib/ld64.so.1': No such file or director
ldd /usr/lib/snapd/snap-confine
linux-vdso64.so.1 (0x79e167af)
libudev.so.1 => /lib/powerpc64le-linux-gnu/libudev.so.1
(0x79e167a1)
libpthread.so.0 => /lib/powerpc64le-linux-gnu/libpthread.so.0
(0x79e1679c)
libc.so.6 => /lib/powerpc64le-linux-gnu/libc.so.6 (0x79e16778)
/lib64/ld64.so.2 (0x79e167b0)
snap changes
ID Status Spawn Ready Summary
1Done9 days ago, at 07:52 UTC today at 15:22 UTC Initialize system
state
2Donetoday at 15:22 UTCtoday at 15:22 UTC Initialize device
snap debug seeding
seeded:true
preseeded: true
image-preseeding: 4.137s
seed-completion: 7.487s
attached are journctl --no-pager files, labeled for hirsute and impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
ppcle64 impish lxd journalctl ** Attachment added: "ppc_impish_lxd_journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944004/+attachment/5531324/+files/ppc_impish_lxd_journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
lxc container snap changes root@test-i:~# snap changes ID Status Spawn Ready Summary 1Error yesterday at 19:26 UTC today at 13:12 UTC Initialize system state 2Donetoday at 13:12 UTC today at 13:12 UTC Initialize device 3Error today at 13:17 UTC today at 13:17 UTC Initialize system state 4Error today at 13:22 UTC today at 13:22 UTC Initialize system state 5Error today at 13:27 UTC today at 13:27 UTC Initialize system state Attached is host machine journalctl --no-pager ** Attachment added: "journalctl_no_pager.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944004/+attachment/5531318/+files/journalctl_no_pager.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
debugging info from a s390x VM test: 1. lxd init (all defaults) 2. lxc launch ubuntu-daily:impish test-i 3. lxc shell test-i 4. cat /etc/cloud/build.info build_name: server serial: 20211006 confirms latest 5. snap debug changes (See attachment) I'm seeing a ton of "permission denied" all over for s390x. it looks like the change that worked for arm64 failed for s390x. working on getting a ppcel64 machine to check as well ** Attachment added: "snap_debug_seeding.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1944004/+attachment/5531317/+files/snap_debug_seeding.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
images from 20211006 have been posted. These can be pulled with lxc launch ubuntu-daily:impish The build date can be verified at /etc/cloud/build.info On our nightly test of lxd with ubuntu-daily:impish I'm still seeing powerpcel64 and s390x fail. I'll attempt to get VMs up for these for debugging today. With release one week away, I'm growing concerned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
a new lxd rootfs and lxd metadata tar have been published to cloud- images.ubuntu.com/impish/20211004/ I confirmed with a local check of lxc launch ubuntu-daily:impish that lxd is picking up the daily produced on 20211004 from streams. Anyone affected, if you could test the latest impish daily to ensure the following: 1. cloud-init finished 2. snap changes shows Done 3. snap debug seeding outputs test repro steps (for non-x84/amd64 based arches only) 1. lxc launch ubuntu-daily:impish test 2. lxc shell test 3. cloud-init status 4. snap changes 5. snap debug seeding I'll have more test results from multiple arches soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
TY anonymouse67, that was my assumption as well, and acceptable from my POV for the image. I do think it's worth putting in our release notes, so I shall :) I'm still working on getting something out. We're getting held up by riscv64 builders just not wanting to play nicely. and those builds take 3+ hours, and like to fail around hour 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
latest daily was built yesterday. Testing, however, is inconclusive.
Even though I tested livecd-rootfs in the Launchpad environment, it
seems like something still isn't jiving, as the system restart key is
still present. Test case below:
1. downloaded arm64 daily lxc rootfs from Launchpad
2. downloaded generated arm64 lxc metadata generated by build system
3. started an arm64 Focal server on AWS (c6g.large)
4. rsynced downloaded files
5. ssh'd to instance
6. lxd init (took all defaults)
7. reboot
8. lxc image import METADATA.tar.xz ROOTFS.tar.xz --alias impish-20211001
9. lxc launch impish-20211001 test-snapd
10. lxc shell test-snapd
11. snap changes:
root@test-snapd:~# snap changes
ID Status Spawn Ready Summary
1Doneyesterday at 17:46 UTC today at 17:57 UTC Initialize system state
2Donetoday at 17:57 UTC today at 17:57 UTC Initialize device
12: snap debug seeding:
snap debug seeding
seeded:true
preseeded: true
image-preseeding: 7.621s
seed-completion: 2.732s
preseed-system-key: {
"apparmor-features": [
"caps",
"dbus",
"domain",
"file",
"mount",
"namespaces",
"network",
"network_v8",
"policy",
"ptrace",
"query",
"rlimit",
"signal"
],
"apparmor-parser-features": [
"qipcrtr-socket",
"unsafe"
],
"apparmor-parser-mtime": 1628490219,
"build-id": "b1511de00d634afe3e6972d273aa6c27f23bdd84",
"cgroup-version": "2",
"nfs-home": false,
"overlay-root": "",
"seccomp-compiler-version": "eeeb2b6ddab2f13c1e5a54e79439562523c7e583 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-actlog",
"seccomp-features": [
"allow",
"errno",
"kill_process",
"kill_thread",
"log",
"trace",
"trap",
"user_notif"
],
"version": 10
}
seed-restart-system-key: {
"apparmor-features": [
"caps",
"dbus",
"domain",
"file",
"mount",
"namespaces",
"network",
"network_v8",
"policy",
"ptrace",
"query",
"rlimit",
"signal"
],
"apparmor-parser-features": [
"qipcrtr-socket",
"unsafe"
],
"apparmor-parser-mtime": 1628490219,
"build-id": "b1511de00d634afe3e6972d273aa6c27f23bdd84",
"cgroup-version": "1",
"nfs-home": false,
"overlay-root": "",
"seccomp-compiler-version": "eeeb2b6ddab2f13c1e5a54e79439562523c7e583 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-actlog",
"seccomp-features": [
"allow",
"errno",
"kill_process",
"kill_thread",
"log",
"trace",
"trap",
"user_notif"
],
"version": 10
}
Still have the system restart key. _however_, snapd is done seeding and
cloud-init finished. At this point, I think it's safe to do a daily
release of the lxc rootfs, to hopefully minimally unblock the docker
transition.
however, I don't believe the changes have closed out the bug entirely.
Once a new daily gets published, I can get more public debugging help on
the system restart key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: cloud-images Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: livecd-rootfs (Ubuntu) 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/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
I've added `livecd-rootfs` as affected after discussing the issue with the snapd team. I'll be introducing a change to `livecd-rootfs` to address how snapd expects cgroup2 with a mount at /sys/fs/cgroup ** Also 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/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
Full output from `snap debug seeding`
{'image-preseeding': '7.949s',
'preseed-system-key': {'apparmor-features': ['caps', 'dbus', 'domain', 'file',
'mount', 'namespaces', 'network',
'network_v8', 'policy', 'ptrace',
'query', 'rlimit', 'signal'],
'apparmor-parser-features': ['qipcrtr-socket',
'unsafe'],
'apparmor-parser-mtime': 1628490219,
'build-id': '62fa24aa378519ac08950d814427f03cc6ef1ee5',
'cgroup-version': '1',
'nfs-home': False,
'overlay-root': '',
'seccomp-compiler-version':
'59f5ac9a4838ef078f5b3f464f7669f76fddeab0 '
'2.5.1 '
'80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c '
'bpf-actlog',
'seccomp-features': ['allow', 'errno', 'kill_process',
'kill_thread', 'log', 'trace',
'trap', 'user_notif'],
'version': 10},
'preseeded': True,
'seed-completion': '4.464s',
'seed-restart-system-key': {'apparmor-features': ['caps', 'dbus', 'domain',
'file', 'mount',
'namespaces', 'network',
'network_v8', 'policy',
'ptrace', 'query', 'rlimit',
'signal'],
'apparmor-parser-features': ['qipcrtr-socket',
'unsafe'],
'apparmor-parser-mtime': 1628490219,
'build-id':
'62fa24aa378519ac08950d814427f03cc6ef1ee5',
'cgroup-version': '2',
'nfs-home': False,
'overlay-root': '',
'seccomp-compiler-version':
'59f5ac9a4838ef078f5b3f464f7669f76fddeab0 '
'2.5.1 '
'80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c '
'bpf-actlog',
'seccomp-features': ['allow', 'errno',
'kill_process',
'kill_thread',
'log', 'trace', 'trap',
'user_notif'],
'version': 10},
'seeded': True}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
after the upload of `snapd (2.53~pre1.git19b68f708)`, I see that snap
pre-seed optimizations aren't completing properly. the `seed-restart-
system-key` is now a call seen in `snap debug seeding`
'seed-restart-system-key': {'apparmor-features': ['caps', 'dbus',
'domain', 'file', 'mount', 'namespaces', 'network', 'network_v8',
'policy', 'ptrace', 'query', 'rlimit', 'signal'], 'apparmor-parser-
features': ['qipcrtr-socket', 'unsafe'], 'apparmor-parser-mtime':
1628490219, 'build-id': '62fa24aa378519ac08950d814427f03cc6ef1ee5',
'cgroup-version': '2', 'nfs-home': False, 'overlay-root': '', 'seccomp-
compiler-version': '59f5ac9a4838ef078f5b3f464f7669f76fddeab0 2.5.1
80ce90419d281437e5b8b03baec604016043649f7c00b7a578f5fc8afef1d29c bpf-
actlog', 'seccomp-features': ['allow', 'errno', 'kill_process',
'kill_thread', 'log', 'trace', 'trap', 'user_notif'], 'version': 10}
the helpful message in our tests state:
```
snap debug seeding' output (on stdout) contained
'seed-restart-system-key'. This 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.
Check the debug logs for /sys/kernel/apparmor/features/* and
/proc/sys/kernel/seccomp/actions_avail to update livecd-rootfs.
This failure can be ignored when publishing images with critical fixes.
```
I know the upload changed some seccomp profiles, so it may be that
something has changed in a way that's incompatible with 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/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
i've tested manually using the following: 1. created an arm64 server instance on AWS 2. uploaded the most recent rootfs from CPC's internal build system 3. created lxd metadata tool using CPC's metadata script (sorry, this and above aren't public) 4. uploaded lxd metadata tar.xz 5. lxd init on the arm instance 6. lxc image import impish-server-cloudimg-arm64-lxd.tar.xz impish-server-cloudimg-arm64-root.tar.xz --alias impish-20210928 7. lxc launch impish-20210928 test-i-20210928 8. lxc shell test-i-20210928 9. test: root@test-i-20210928:~# cloud-init status status: done root@test-i-20210928:~# snap changes ID Status Spawn Ready Summary 1Donetoday at 06:47 UTC today at 13:35 UTC Initialize system state 2Donetoday at 13:35 UTC today at 13:35 UTC Initialize device Based on the above, the snapd change looks good. I'll coordinate with the rest of the CPC team for next steps on the Impish daily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
@sergiodj : Build happened early this AM. I see in the image manifest snapd 2.53~pre1.git19b68f708 I'll do manual verification this morning, and push an image if it passes manual testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
We have reproducers on arm64 and s390x now. I'm seeing the same things as the snapd.log in https://bugs.launchpad.net/cloud-images/+bug/1944004/comments/1 any attempts to restart the service do the same thing. So something has set up snapd with incorrect permissions. At this point, I'm going to have to defer to someone on the snapd team for further debugging help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
available at: http://cloud- images.ubuntu.com/daily/server/impish/20210904/impish-server-cloudimg- arm64-root.manifest ** Attachment added: "20210904-impish-server-cloudimg-arm64-root.manifest" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527408/+files/20210904-impish-server-cloudimg-arm64-root.manifest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
Apologies, i had some file confusion locally in creating the diff of packages, which led to confusion. Attached is the proper diff. I'll also attached the manifest used to generate this diff From the list of package changes here, I'm not seeing a smoking gun. `cloud-init` upreved, as well as a bunch of gcc ** Attachment removed: "20210903-to-20210904-rootfs-diff-unified.txt" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527403/+files/20210903-to-20210904-rootfs-diff-unified.txt ** Attachment added: "20210903-to-20210904-rootfs-diff-unified.txt" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527405/+files/20210903-to-20210904-rootfs-diff-unified.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
available at: http://cloud- images.ubuntu.com/daily/server/impish/20210903/impish-server-cloudimg- arm64-root.manifest ** Attachment added: "20210903-impish-server-cloudimg-arm64-root.manifest" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527407/+files/20210903-impish-server-cloudimg-arm64-root.manifest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Attachment removed: "diff-2021093-to-20210904.txt" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527398/+files/diff-2021093-to-20210904.txt ** Attachment added: "20210903-to-20210904-rootfs-diff-unified.txt" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527403/+files/20210903-to-20210904-rootfs-diff-unified.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
livecd-rootfs, used for building this, had a release on 20210830 and on 20210914. This feels like it may be a dead end, as I should have been able to reproduce the error on the 20210903 image built with the 20210830 release of livecd-rootfs if there was an issue in the base build scripts. for cpc extras, there were changes, but not to any paths touched by a rootfs build (they were to hyperv and oracle builds). At this point, I'm leaning towards a package change rather than a build change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
Manifest Diff from 20210903 to 20210904 is now attached 20210903 rootfs is working fine. I did the following: 1. started an ARM image on Oracle 2. downloaded http://cloud-images.ubuntu.com/impish/20210903/impish-server-cloudimg-arm64-root.tar.xz and http://cloud-images.ubuntu.com/impish/20210903/impish-server-cloudimg-arm64-lxd.tar.xz 3. lxc image import impish-server-cloudimg-arm64-lxd.tar.xz impish-server-cloudimg-arm64-root.tar.xz --alias impish-20210903 4. lxc launch impish-20210903 5. lxc shell 6. snap changes 7. cloud-init status repeat for 20210904 and see see the reproduction of the error (snap initialize system state ERROR) The diff shows what packages changed between the working and failing versions. There is no snapd difference between working and failing versions. Next steps for me are to dig into what changes may have occurred in livecd-rootfs that could change build behaviour, and to dig into the package diffs themselves and see if there is a specific package causing the issue in state. ** Attachment added: "diff-2021093-to-20210904.txt" https://bugs.launchpad.net/cloud-images/+bug/1944004/+attachment/5527398/+files/diff-2021093-to-20210904.txt ** Changed in: cloud-images Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
ACK. I've started looking into it. initial things I can see: 1. there have been no code changes to how the image is being made. code is https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- cpc/hooks.d/base/create-root-dir.binary and https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- cpc/hooks.d/base/root-xz.binary 2. from a date when our tests were 100% green (20210904) to our first failing tests (20210907) there was not an update to snapd 3. The failing case with `lxc launch ubuntu-daily:impish test-container && lxc shell test-container` should be pulling our last successfully tested rootfs, 202010904. We need to check to see what rootfs / container is being pulled on that command, and correlate to any possible changes. there's more triage to be done on this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939603] [NEW] Oracle DataSource Fails When Used With a Bionic Image
Public bug reported: When attempting to launch a Bionic instance on Oracle Cloud Infrastructure, with an explicitly set datasource: [ Oracle ], the instance fails to run the OracleDataSource. This leads to the instance not having SSH keys imported from the metadata service. The failure is related to the command: Running command ['ip', '-4', 'route', 'add', '0.0.0.0/0', 'via', '10.0.0.1', 'dev', 'ens3'] with allowed return codes [0] (shell=False, capture=True) Which showed up in the logs : 2021-08-11 13:56:13,289 - util.py[DEBUG]: Reading from /var/tmp/cloud-init/cloud-init-dhcp-p8n35ztd/dhcp.leases (quiet=False) 2021-08-11 13:56:13,289 - util.py[DEBUG]: Read 519 bytes from /var/tmp/cloud-init/cloud-init-dhcp-p8n35ztd/dhcp.leases 2021-08-11 13:56:13,289 - dhcp.py[DEBUG]: Received dhcp lease on ens3 for 10.0.0.66/255.255.255.0 2021-08-11 13:56:13,289 - __init__.py[DEBUG]: Attempting setup of ephemeral network on ens3 with 10.0.0.66/24 brd 10.0.0.255 2021-08-11 13:56:13,289 - subp.py[DEBUG]: Running command ['ip', '-family', 'inet', 'addr', 'add', '10.0.0.66/24', 'broadcast', '10.0.0.255', 'dev', 'ens3'] with allowed return codes [0] (shell=False, capture=True) 2021-08-11 13:56:13,291 - __init__.py[DEBUG]: Skip ephemeral network setup, ens3 already has address 10.0.0.66 2021-08-11 13:56:13,291 - subp.py[DEBUG]: Running command ['ip', '-4', 'route', 'add', '0.0.0.0/0', 'via', '10.0.0.1', 'dev', 'ens3'] with allowed return codes [0] (shell=False, capture=True) 2021-08-11 13:56:13,293 - handlers.py[DEBUG]: finish: init-local/search-Oracle: FAIL: no local data found from DataSourceOracle 2021-08-11 13:56:13,293 - util.py[WARNING]: Getting data from failed 2021-08-11 13:56:13,293 - util.py[DEBUG]: Getting data from failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 792, in find_source if s.update_metadata([EventType.BOOT_NEW_INSTANCE]): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 681, in update_metadata result = self.get_data() File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 292, in get_data return_value = self._get_data() File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceOracle.py", line 138, in _get_data with network_context: File "/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py", line 57, in __enter__ return self.obtain_lease() File "/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py", line 110, in obtain_lease ephipv4.__enter__() File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 1088, in __enter__ self._bringup_static_routes() File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 1142, in _bringup_static_routes ['dev', self.interface], capture=True) File "/usr/lib/python3/dist-packages/cloudinit/subp.py", line 295, in subp cmd=args) cloudinit.subp.ProcessExecutionError: Unexpected error while running command. Command: ['ip', '-4', 'route', 'add', '0.0.0.0/0', 'via', '10.0.0.1', 'dev', 'ens3'] Exit code: 2 Reason: - Stdout: Stderr: RTNETLINK answers: File exists This eventually leads to cloud-init falling back to NoDataSource. To create this image, I: * Updated CPC's livecd-rootfs code for Oracle to include: # etc/cloud/cloud.cfg.d/99-oracle-compute-infra-datasource.cfg" # Configuration for Oracle Cloud Infrastructure datasource_list: [ Oracle ] * created an image using CPC's livecd-rootfs using ubuntu-bartender * registered a custom image in OCI * attempted to create an instance using the custom image I was unable to connect via ssh, getting "Permission denied (publickey)" I attempted to create a serial connection, however, I was never able to successfully SSH in. It just hung forever. In a second attempt, I tried to pass in a username:password to cloud- init. However, due to the failure of the datasource, and fallback to NoDataSource, my custom data was not loaded either I was able to collect logs by terminating the instance, but keeping the boot volume. I then created a Bionic instance using the platform image, and verified that it worked with the OpenStack datasource currently in use. I then attached the boot volume from the now terminated instance as a block volume, ran the required iscsi commands (found via the web console after attaching the block volume), and mounted the drive to /mnt/nods. I was then able to collect the logs in /mnt/nods/var/log/cloud-init*. Because of how I had to collect logs, i was unable to run `cloud-init collect-logs`. I actually could run cloud- init in a chroot setup, like `sudo chroot /mnt/nods cloud-init collect- logs`. This failed with being unable to find the command `cloud-init`. Honestly not sure if that's the correct approach in the circumstance. To reproduce, an image would need made with the datasource explicitly set to Oracle. ** Affects: cloud-init (Ubuntu) Importance: Undecided Statu
[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
For all new commenters -- what you're experiencing is a new bug with similar symptoms, though slightly different root cause. Note the original bug was "no device found" and this is "Invalid argument." This appears to be a new bug. I don't see an identical bug to this new issues, so i've opened https://bugs.launchpad.net/cloud- images/+bug/1939580 and copied over comments. Please use issue 1939580 to track this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925780] Re: armhf & arm64 image do not have cloud-init grub customizations
rcj and I had just been discussing this in relation to a new arm64 image. We are currently re-enabling the file for EC2 arm64 in our EC2 specific code. I took the workaround from our EC2 and implemented in our test image. We agreed that we'll need to get 999-cpc-fixes worked out more. The code that writes the mentioned file is: https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- cpc/hooks.d/chroot/999-cpc-fixes.chroot#n189 what everything from 125 to 189 is where I needed to get some more guidance to ensure everything would work on arm properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925780 Title: armhf & arm64 image do not have cloud-init grub customizations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1925780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
