[Bug 1938299] Re: Unable to SSH Into Instance when deploying Impish 12.10
** Description changed: - Google Instances deployed with the Ubuntu 12.10 Daily images are + Google Instances deployed with the Ubuntu 21.10 Daily images are inaccessible via SSH. gcloud compute instances create sf-impish-v20200720 --zone us-west1-a --network "default" --no-restart-on-failure --image-project ubuntu-os- cloud-devel --image daily-ubuntu-2110-impish-v20210720 --machine-type n1-standard-2 Will result in a successful deploy yet, inaccessible via ssh from the end users configured laptop. This appears to affect all daily images after 20210719. daily-ubuntu-2110-impish-v20210719ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210720ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210721ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210723ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210724ubuntu-os-cloud-devel ubuntu-2110 READY daily-ubuntu-2110-impish-v20210725ubuntu-os-cloud-devel ubuntu-2110 READY - daily-ubuntu-2110-impish-v20210728ubuntu-os-cloud-devel ubuntu-2110 + daily-ubuntu-2110-impish-v20210728ubuntu-os-cloud-devel ubuntu-2110 - - This problem also appears to be reproducible via the gcloud UI, create a new virtual machine using the daily-ubuntu-2110-impish-v20210720 or greater and instruct the virtual machine to import a ssh_pub_key in the security tab. The Instance will start, yet still be inaccessible via the users private sshkey + This problem also appears to be reproducible via the gcloud UI, create a + new virtual machine using the daily-ubuntu-2110-impish-v20210720 or + greater and instruct the virtual machine to import a ssh_pub_key in the + security tab. The Instance will start, yet still be inaccessible via + the users private sshkey The google-guest-agent.service appears to be responsible for adding the google project ssh keys to the instance once its deployed. Please see below when queried on the 20210719 image: - google-guest-agent.service - Google Compute Engine Guest Agent - Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) - Active: active (running) since Tue 2021-07-27 19:47:48 UTC; 18h ago -Main PID: 711 (google_guest_ag) - Tasks: 9 (limit: 8924) - Memory: 19.7M - CGroup: /system.slice/google-guest-agent.service - └─711 /usr/bin/google_guest_agent + google-guest-agent.service - Google Compute Engine Guest Agent + Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) + Active: active (running) since Tue 2021-07-27 19:47:48 UTC; 18h ago + Main PID: 711 (google_guest_ag) + Tasks: 9 (limit: 8924) + Memory: 19.7M + CGroup: /system.slice/google-guest-agent.service + └─711 /usr/bin/google_guest_agent Jul 27 19:47:55 sean-imp gpasswd[1469]: user google added by root to group floppy Jul 27 19:47:55 sean-imp gpasswd[1475]: user google added by root to group audio Jul 27 19:47:55 sean-imp gpasswd[1481]: user google added by root to group dip Jul 27 19:47:55 sean-imp gpasswd[1487]: user google added by root to group video Jul 27 19:47:55 sean-imp gpasswd[1493]: user google added by root to group plugdev Jul 27 19:47:55 sean-imp gpasswd[1499]: user google added by root to group netdev Jul 27 19:47:55 sean-imp gpasswd[1505]: user google added by root to group lxd Jul 27 19:47:55 sean-imp gpasswd[1511]: user google added by root to group google-sudoers Jul 27 19:47:55 sean-imp GCEGuestAgent[711]: 2021-07-27T19:47:55.1699Z GCEGuestAgent Info: Updating keys for user google. Jul 27 19:47:55 sean-imp google_guest_agent[711]: 2021/07/27 19:47:55 logging client: rpc error: code = PermissionDenied desc = Clo> lines 1-19/19 (END) ** Summary changed: - Unable to SSH Into Instance when deploying Impish 12.10 + Unable to SSH Into Instance when deploying Impish 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938299 Title: Unable to SSH Into Instance when deploying Impish 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1938299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] Re: Google Confidential Compute fails to boot with shim version 1.47
Verification steps: 1. Enabled Confidential Compute 2. Change image to daily-ubuntu-2104-hirsute-v20210510 (last working image) 3. Launched image 4. Enabled proposed 5. Updated system https://paste.ubuntu.com/p/mNrZNkVYtB/ 6. Rebooted sucessfully! https://paste.ubuntu.com/p/G9CmvhW9tx/ Marking verification-done ** 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/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
# GCE Verification ## Test Steps Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/ Ensure system successfully reboots ## Xenial Results uEFI only: https://paste.ubuntu.com/p/nwcjCSVTRD/ uEFI+Secure Boot: https://paste.ubuntu.com/p/KZ8tS9zkKr/ Both systems reboot successfully! Marking verification done. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935559] Re: Cron script uses up all space in /run
# Steps to reproduce 1. $ multipass launch bionic --name b1 2. $ multipass exec b1 bash 3. $ sudo apt update 4. $ sudo apt install aide 5. At the MTA configuration select "No configuration" 6. $ sudo run-parts /etc/cron.daily 7. $ sudo run-parts /etc/cron.daily 8. $ sudo ls /run/aide At this point, the /run/aide directory will have a cron.daily and cron.daily.old* folder It appears that the aide crontab will fail if an MTA is not configured or is not even running. Instead of selecting "No configuration" stopping the postfix process will cause the same failure. # Possible workarounds/fixes 1. Remove `set -e` from /etc/cron.daily/aide or add `set +e` around the postfix section to ensure the cronjob completes even if the MTA is down 2. If this is due to a unconfigured MTA, then ensure that it is configured For example, set the MTA to a local configuration: $ sudo debconf-set-selections <<< "postfix postfix/main_mailer_type select 'Local only'" $ sudo dpkg-reconfigure -f noninteractive postfix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935559 Title: Cron script uses up all space in /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1935559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
# GCE Verification ## Test Steps Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/ Ensure system successfully reboots ## Xenial Results uEFI only: https://paste.ubuntu.com/p/kqjn5YbYCb/ uEFI+Secure Boot: https://paste.ubuntu.com/p/xZ5t24P7nr/ Both systems reboot successfully! Marking verification done. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
# Xenial AWS Verification ## Test Steps Booted AWS arm64 baremetal and VM systems Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/ Ensure system successfully reboots ## Results t4g.medium: https://paste.ubuntu.com/p/ys4hgfTfRm/ c6g.metal: https://paste.ubuntu.com/p/2RFYbCmFxh/ Both systems successfully updated grub from proposed and rebooted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
Marking verification done ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations
# Bionic Verification ## Test Steps Booted AWS arm64 baremetal and VM systems Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/ Ensure system successfully reboots ## Results t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/ c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/ Both systems successfully updated grub from proposed and rebooted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
After verifying that the "error" messages in #15 is ignorable, marking this verification done. ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
Testing complete, if someone can explain the error messages in comment #15 we can mark this verification-done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
# GCE Verification ## Test Steps Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot Ran the following script: https://paste.ubuntu.com/p/BDwhF4KHZ2/ Ensure system successfully reboots ## Xenial Results uEFI only: https://paste.ubuntu.com/p/vhxkYy5F43/ uEFI+Secure Boot: https://paste.ubuntu.com/p/hwr9Z4qdZB/ Both systems successfully rebooted. ## Bionic Results The bionic systems did not have these files so removing and touching them was not done: /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/grubx64.efi uEFI only: https://paste.ubuntu.com/p/tMrs2jJrDc/ uEFI+Secure Boot: https://paste.ubuntu.com/p/xgwG6FVwCt/ Both systems successfully rebooted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
# Bionic AWS Verification ## Test Steps Booted AWS arm64 baremetal and VM systems Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/ Ensure system successfully reboots ## Results t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/ c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/ Both systems successfully updated grub from proposed and rebooted. However, on the c6g.metal instance, while apt did not report an error, there were error messages printed out: Inserting key update /usr/share/secureboot/updates/dbx/dbxupdate_arm64.bin into dbx Error writing key update: Invalid argument Error syncing keystore file /usr/share/secureboot/updates/dbx/dbxupdate_arm64.bin Setting up grub-efi-arm64-signed (1.167~18.04.5+2.04-1ubuntu44.1.2) ... Can this error please either be fixed or explained in this bug before marking verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
# Xenial AWS Verification ## Test Steps Booted AWS arm64 baremetal and VM systems Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/ Ensure system successfully reboots ## Results Both systems successfully updated grub from proposed and rebooted t4g.medium: https://paste.ubuntu.com/p/ys4hgfTfRm/ c6g.metal: https://paste.ubuntu.com/p/2RFYbCmFxh/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] [NEW] Google Confidnetial Compute fails to boot with 1.47
Public bug reported: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone =us-west1-b --machine-type=n2d-standard-2 --image=daily-ubuntu-2104 -hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ ** Affects: shim-signed (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/1931254 Title: Google Confidnetial Compute fails to boot with 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930742] Re: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable
Launched c6g.metal, a1.metal, and t4g.medium instance with Xenial (20210429) on upgrade of all three I got the following error: grub-install: error: relocation 0x113 is not implemented yet. Failed: grub-install --target=arm64-efi WARNING: Bootloader is not properly installed, system may not be bootable Log: https://paste.ubuntu.com/p/khgMBYH86N/ Script: https://paste.ubuntu.com/p/cnTHCd8hGQ/ Marking verification verification-failed-xenial ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930742 Title: cloud images in xenial do not get their boot path updated because we don't call grub-install --force-extra-removable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1930742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928856] Re: Please update to upstream release 20210429.00
Google has confirmed that the SRU has successfully passed their tests and previously failing tests are now consistently passing. Marking fixed verified. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy 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/1928856 Title: Please update to upstream release 20210429.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1928856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928856] Re: Please update to upstream release 20210429.00
Test images were delivered to Google with images with the following versions: * bionic-livecd.ubuntu-cpc.gce.devel.manifest google-compute-engine-oslogin20210429.00-0ubuntu1~18.04.0 * focal-livecd.ubuntu-cpc.gce.devel.manifest google-compute-engine-oslogin20210429.00-0ubuntu1~20.04.0 * groovy-livecd.ubuntu-cpc.gce.devel.manifest google-compute-engine-oslogin 20210429.00-0ubuntu1~20.10.0 * hirsute-livecd.ubuntu-cpc.gce.devel.manifest google-compute-engine-oslogin 20210429.00-0ubuntu1~21.04.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928856 Title: Please update to upstream release 20210429.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1928856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924589] Re: Please update to 20210414.00 upstream release
Marking verification-done for all releases. Images were successfully generated with the following versions of google-guest-agent from proposed: bionic: 20210414.00-0ubuntu1~18.04.0 focal: 20210414.00-0ubuntu1~20.04.0 groovy: 20210414.00-0ubuntu1~20.10.0 hirsute: 20210414.00-0ubuntu1 These images were uploaded and provided to Google's engineering team to complete testing of their own. Their own verification suite is used for previous SRUs as well. Their testing was successful as well. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy 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/1924589 Title: Please update to 20210414.00 upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1924589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927231] Re: u-boot-update complains about a syntax error
Per the diff there are two merge issues https://launchpadlibrarian.net/536068009/u-boot- menu_4.0.2ubuntu5_4.0.3ubuntu1.diff.gz fwiw this is blocking impish builds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927231 Title: u-boot-update complains about a syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923865] Re: Bootable buildd xenial images go to initramfs on boot
Marking confirmed # Steps to reproduce 1. wget http://cloud-images.ubuntu.com/daily/server/buildd/daily/xenial/current/xenial-server-cloudimg-amd64-disk.img 2. Modify /etc/boot/grub.cfg to add "console=ttyS0" to kernel command line 3. Boot using the following qemu CLI: qemu-system-x86_64 \ -cpu host -machine type=q35,accel=kvm -m 2048 \ -snapshot \ -nographic \ -netdev id=net00,type=user,hostfwd=tcp::2-:22 \ -device virtio-net-pci,netdev=net00 \ -drive if=virtio,format=qcow2,file=xenial-server-cloudimg-amd64-disk.img # Expected behavior Boot to login # Actual behavior Boot drops to an initramfs busy box console ** Changed in: cloud-images Status: Incomplete => Confirmed ** 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/1923865 Title: Bootable buildd xenial images go to initramfs on boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# Upgrading Xenial to Bionic on GCE Running again with the correct, newer release-upgrader version from today 1. Launched GCE instance 2. Installed google-cloud-sdk snap 3. Updated system 4. Verified the tracking channel was updated $ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04 --classic 2021-04-21T20:25:30Z INFO Waiting for automatic snapd restart... google-cloud-sdk 337.0.0 from Cloud SDK (google-cloud-sdk✓) installed $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-16.04 refresh-date: today at 20:25 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ do-release-upgrade -p Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,247 kB] Fetched 1,247 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz' [screen is terminating] $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-18.04 refresh-date: today at 20:25 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2021-04-21 20:32:40,783 INFO release-upgrader version '18.04.44' started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# Upgrading Xenial to Bionic on GCE (again with more logs this time) 1. Launched GCE instance 2. Installed google-cloud-sdk snap 3. Updated system 4. Verified the tracking channel was updated $ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04 --classic 2021-04-21T16:41:37Z INFO Waiting for automatic snapd restart... google-cloud-sdk 337.0.0 from Cloud SDK (google-cloud-sdk✓) installed $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-16.04 refresh-date: today at 16:41 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ do-release-upgrade -p Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,247 kB] Fetched 1,248 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz' [screen is terminating] $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-18.04 refresh-date: today at 16:41 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2021-04-21 16:42:07,419 INFO release-upgrader version '18.04.40' started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# update /etc/update-manager/release-upgrades to Prompt=normal $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Google Cloud SDK publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-20.04 refresh-date: 4 days ago, at 04:14 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 336.0.0(177) 236MB classic $ do-release-upgrade -p $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-20.10 refresh-date: today at 17:57 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2021-04-20 17:47:06,645 INFO release-upgrader version '20.10.15' started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# Upgrading Xenial to Bionic on GCE 1. Launched GCE instance 2. Installed google-cloud-sdk snap 3. Updated system 4. Verified the tracking channel was updated name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-16.04 refresh-date: today at 17:20 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# Upgrading Xenial to Bionic on GCE (again with more logs this time) 1. Launched GCE instance 2. Installed google-cloud-sdk snap 3. Updated system 4. Verified the tracking channel was updated $ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04 --classic 2021-04-20T16:24:02Z INFO Waiting for automatic snapd restart... google-cloud-sdk 337.0.0 from Cloud SDK (google-cloud-sdk✓) installed $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-16.04 refresh-date: today at 17:20 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ do-release-upgrade -p $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-18.04 refresh-date: today at 16:24 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2021-04-20 16:24:46,328 INFO release-upgrader version '18.04.40' started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
# Upgrading Bionic to Focal on GCE 1. Launched GCE instance 2. Installed google-cloud-sdk snap 3. Updated system 4. Verified the tracking channel was updated $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Google Cloud SDK publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-18.04 refresh-date: today at 15:58 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 336.0.0(177) 236MB classic $ do-release-upgrade -p $ sudo snap info google-cloud-sdk name: google-cloud-sdk summary: Command-line interface for Google Cloud Platform products and services publisher: Cloud SDK (google-cloud-sdk✓) store-url: https://snapcraft.io/google-cloud-sdk contact: https://cloud.google.com/sdk/docs/ license: unset description: | Command-line interface for Google Cloud Platform products and services commands: - google-cloud-sdk.anthoscli - google-cloud-sdk.bq - google-cloud-sdk.docker-credential-gcloud - google-cloud-sdk.gcloud - google-cloud-sdk.gsutil - google-cloud-sdk.kubectl snap-id: MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd tracking: latest/stable/ubuntu-20.04 refresh-date: today at 17:08 UTC channels: latest/stable:337.0.0 2021-04-20 (178) 237MB classic latest/candidate: ↑ latest/beta: 337.0.0 2021-04-20 (178) 237MB classic latest/edge: 337.0.0 2021-04-20 (178) 237MB classic installed: 337.0.0(178) 237MB classic $ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2021-04-20 16:44:43,490 INFO release-upgrader version '20.04.32' started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925008] Re: no memory hot-plugging in cloud-images
Marking affects linux, so the kernel folks can weigh in on this. ** Also affects: linux (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/1925008 Title: no memory hot-plugging in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923868] Re: Bootable buildd images silent on both graphical and serial console
Investigating your other bug caused me to find: https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd- rootfs/+merge/398027 Which will set up a custom grub config without quiet. Looking at a hirsute image, this appears to be the case already. What is remaining is the SRU back to other releases via the following MPs: xenial https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/398900 bionic https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/398899 focal https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/398898 groovy https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/398897 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923868 Title: Bootable buildd images silent on both graphical and serial console To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923868] Re: Bootable buildd images silent on both graphical and serial console
Adding livecd-rootfs as this is where I believe this would be changed. In livecd-rootfs, CPC images get a 50-cloudimg-settings.cfg where GRUB_CMDLINE_LINUX_DEFAULT is set without quiet. Similarly, ubuntu-core does something similar in their hooks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923868 Title: Bootable buildd images silent on both graphical and serial console To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923868] Re: Bootable buildd images silent on both graphical and serial console
** 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/1923868 Title: Bootable buildd images silent on both graphical and serial console To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
The reason I am looking into this is that we are stating we support cloud image upgrades from LTS to LTS now. As such, I would hope that the upgrade process would upgrade the snap channels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel
I don't see why ubuntu-desktop is required in either of those bugs. Is there a defined policy that says we only do snap upgrades on systems with that package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922581] [NEW] 5s boot delay added when System BootOrder not found
Public bug reported: # Overview Recent changes in boot logic moved grub from "removable disk" path to "/efi/ubuntu" in order to fix grub package updates. This had the side-effect of adding a 5-second boot delay in images. This was discovered in GCE images booting Bionic or newer. # Expected result The system to correctly boot from the first boot entry with no delay. # Actual result The system cannot find "System BootOrder", initializes defaults, and creates a 5-second delay in boot. # Steps to reproduce 1. Launch any GCE bionic or newer image after 20210224 2. View the serial console for the image and look for: "System BootOrder not found. Initializing defaults." Afterward, there were are messages counting down, starting with "Booting in 5 seconds" # Logs GCE Image 20210211: https://pastebin.ubuntu.com/p/JdgfRbZrCY/ GCE Image 20210224: https://pastebin.ubuntu.com/p/M7d4SZ4BJ3/ ** Affects: shim (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/1922581 Title: 5s boot delay added when System BootOrder not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1922581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] [NEW] 20.10 to 21.04: snap does not upgrade channel
Public bug reported: # Overview Per LP: #1827951 and LP: #1748581, it would appear that if a snap is tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a do-release-upgrade the snap channel should update to the new release. Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud- sdk does not get updated. # Expected result After a do-release-upgrade, the snap channel for google-cloud-sdk should be updated from "latest/stable/ubuntu-20.10" to "latest/stable/ubuntu-21.04". # Actual result After install, the snap continues to track "latest/stable/ubuntu-20.10". # Steps to reproduce 1. Boot 20.10 GCE image 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" 3. do-release-upgrade -d 4. accept defaults and reboot 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" # Logs main.log https://paste.ubuntu.com/p/kbSvM5JMzP/ screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/ apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/ ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Description changed: # Overview Per LP: #1827951 and LP: #1748581, it would appear that if a snap is tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a do-release-upgrade the snap channel should update to the new release. Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud- sdk does not get updated. # Expected result After a do-release-upgrade, the snap channel for google-cloud-sdk should be updated from "latest/stable/ubuntu-20.10" to "latest/stable/ubuntu-21.04". # Actual result After install, the snap continues to track "latest/stable/ubuntu-20.10". # Steps to reproduce 1. Boot 20.10 GCE image 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" 3. do-release-upgrade -d 4. accept defaults and reboot - 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-21.04" + 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" # Logs main.log https://paste.ubuntu.com/p/kbSvM5JMzP/ screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/ apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908548] Re: Add manpages to packaging branches
# Summary All man pages appear to show up as expected, marking all releases as verification-done. # Test Steps All SRUs were tested using an LXD instance from ubuntu-daily. Proposed was added and cloud-init updated. The apt-cache policy is shown below and then a directory listing of the man pages to show the existence of the three new cloud-init specific man pages (e.g. cloud-id, cloud-init- per, and cloud-init). Additionally, per the test case above, viewed each man page. # Verification for Xenial root@x:~# apt-cache policy cloud-init cloud-init: Installed: 21.1-19-gbad84ad4-0ubuntu1~16.04.1 Candidate: 21.1-19-gbad84ad4-0ubuntu1~16.04.1 Version table: *** 21.1-19-gbad84ad4-0ubuntu1~16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20.4.1-0ubuntu1~16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 0.7.7~bzr1212-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@x:~# ls -l /usr/share/man/man1/cloud-* -rw-r--r-- 1 root root 407 Mar 23 23:07 /usr/share/man/man1/cloud-id.1.gz -rw-r--r-- 1 root root 587 Mar 23 23:07 /usr/share/man/man1/cloud-init-per.1.gz -rw-r--r-- 1 root root 983 Mar 23 23:07 /usr/share/man/man1/cloud-init.1.gz root@x:~# man cloud-id; echo $? 0 root@x:~# man cloud-init-per; echo $? 0 root@x:~# man cloud-init; echo $? 0 # Verification for Bionic root@b:~# apt-cache policy cloud-init cloud-init: Installed: 21.1-19-gbad84ad4-0ubuntu1~18.04.1 Candidate: 21.1-19-gbad84ad4-0ubuntu1~18.04.1 Version table: *** 21.1-19-gbad84ad4-0ubuntu1~18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20.4.1-0ubuntu1~18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 18.2-14-g6d48d265-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@b:~# ls -l /usr/share/man/man1/cloud-* -rw-r--r-- 1 root root 407 Mar 22 15:46 /usr/share/man/man1/cloud-id.1.gz -rw-r--r-- 1 root root 587 Mar 22 15:46 /usr/share/man/man1/cloud-init-per.1.gz -rw-r--r-- 1 root root 983 Mar 22 15:46 /usr/share/man/man1/cloud-init.1.gz root@b:~# man cloud-id; echo $? 0 root@b:~# man cloud-init-per; echo $? 0 root@b:~# man cloud-init; echo $? 0 # Verification for Focal root@f:~# apt-cache policy cloud-init cloud-init: Installed: 21.1-19-gbad84ad4-0ubuntu1~20.04.1 Candidate: 21.1-19-gbad84ad4-0ubuntu1~20.04.1 Version table: *** 21.1-19-gbad84ad4-0ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20.4.1-0ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 20.1-10-g71af48df-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@f:~# ls -l /usr/share/man/man1/cloud-* -rw-r--r-- 1 root root 407 Mar 22 15:01 /usr/share/man/man1/cloud-id.1.gz -rw-r--r-- 1 root root 587 Mar 22 15:01 /usr/share/man/man1/cloud-init-per.1.gz -rw-r--r-- 1 root root 983 Mar 22 15:01 /usr/share/man/man1/cloud-init.1.gz root@f:~# man cloud-id; echo $? 0 root@f:~# man cloud-init-per; echo $? 0 root@f:~# man cloud-init; echo $? 0 # Verification for Groovy root@g:~# apt-cache policy cloud-init cloud-init: Installed: 21.1-19-gbad84ad4-0ubuntu1~20.10.1 Candidate: 21.1-19-gbad84ad4-0ubuntu1~20.10.1 Version table: *** 21.1-19-gbad84ad4-0ubuntu1~20.10.1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 20.4.1-0ubuntu1~20.10.1 500 500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 20.3-15-g6d332e5c-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages root@g:~# ls -l /usr/share/man/man1/cloud-* -rw-r--r-- 1 root root 407 Mar 22 14:32 /usr/share/man/man1/cloud-id.1.gz -rw-r--r-- 1 root root 587 Mar 22 14:32 /usr/share/man/man1/cloud-init-per.1.gz -rw-r--r-- 1 root root 983 Mar 22 14:32 /usr/share/man/man1/cloud-init.1.gz root@g:~# man cloud-id; echo $? 0 root@g:~# man cloud-init-per; echo $? 0 root@g:~# man cloud-init; echo $? 0 ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908548 Title: Add manpages to packaging branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1908548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/
[Bug 1911689] Re: Please update to upstream release 20210219.00
There was one build failure on xenial: "powerpc: Failed to build". However, this arch is not a target of this package in images and can be ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911689 Title: Please update to upstream release 20210219.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1911689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911689] Re: Please update to upstream release 20210219.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. >From my own testing, I used the latest GCE images, enabled proposed and installed google-osconfig-agent. I verified: 1) the versions of packages 2) that the services were running/completed successfully My notes and logs are below. # Xenial powersj@xenial:~$ apt-cache policy google-osconfig-agent google-osconfig-agent: Installed: 20210219.00-0ubuntu1~16.04.0 Candidate: 20210219.00-0ubuntu1~16.04.0 Version table: *** 20210219.00-0ubuntu1~16.04.0 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 Packages 100 /var/lib/dpkg/status powersj@xenial:~$ systemctl status google-osconfig-agent.service ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-16 20:43:14 UTC; 30s ago Main PID: 1297 (google_osconfig) Tasks: 10 Memory: 24.3M CPU: 279ms CGroup: /system.slice/google-osconfig-agent.service └─1297 /usr/bin/google_osconfig_agent Mar 16 20:43:14 xenial systemd[1]: Started Google OSConfig Agent. Mar 16 20:43:14 xenial OSConfigAgent[1297]: 2021-03-16T20:43:14.4248Z OSConfigAgent Info: OSConfig Agent (version 20210219.00-0ubuntu1~16.0 # Bionic powersj@bionic:~$ apt-cache policy google-osconfig-agent google-osconfig-agent: Installed: 20210219.00-0ubuntu1~18.04.0 Candidate: 20210219.00-0ubuntu1~18.04.0 Version table: *** 20210219.00-0ubuntu1~18.04.0 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status powersj@bionic:~$ systemctl status google-osconfig-agent.service ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-16 20:48:45 UTC; 25s ago Main PID: 1049 (google_osconfig) Tasks: 10 (limit: 4669) CGroup: /system.slice/google-osconfig-agent.service └─1049 /usr/bin/google_osconfig_agent Mar 16 20:48:45 bionic systemd[1]: Started Google OSConfig Agent. Mar 16 20:48:45 bionic OSConfigAgent[1049]: 2021-03-16T20:48:45.2502Z OSConfigAgent Info: OSConfig Agent (version 20210219.00-0ubuntu1~18.0 # Focal powersj@focal:~$ apt-cache policy google-osconfig-agent google-osconfig-agent: Installed: 20210219.00-0ubuntu1~20.04.0 Candidate: 20210219.00-0ubuntu1~20.04.0 Version table: *** 20210219.00-0ubuntu1~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status powersj@focal:~$ systemctl status google-osconfig-agent.service ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-16 20:50:57 UTC; 23s ago Main PID: 498 (google_osconfig) Tasks: 10 (limit: 4713) Memory: 23.4M CGroup: /system.slice/google-osconfig-agent.service └─498 /usr/bin/google_osconfig_agent Mar 16 20:50:57 focal systemd[1]: Started Google OSConfig Agent. Mar 16 20:50:58 focal OSConfigAgent[498]: 2021-03-16T20:50:58.2064Z OSConfigAgent Info: OSConfig Agent (version 20210219.00-0ubuntu1~20.04> # Groovy powersj@groovy:~$ apt-cache policy google-osconfig-agent google-osconfig-agent: Installed: 20210219.00-0ubuntu1~20.10.0 Candidate: 20210219.00-0ubuntu1~20.10.0 Version table: *** 20210219.00-0ubuntu1~20.10.0 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 20200625.00-0ubuntu3 500 500 http://us-west1.gce.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages powersj@groovy:~$ systemctl status google-osconfig-agent.service ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-16 20:52:43 UTC; 49s ago Main PID: 480 (google_osconfig) Tasks: 8 (limit: 4708) Memory: 24.4M CGroup: /system.slice/google-osconfig-agent.service └─480 /usr/bin/google_osconfig_agent Mar 16 20:52:43 groovy systemd[1]: Started Google OSConfig Agent. Mar 16 20:52:43 groovy OSConfigAgent[480]: 2021-03-16T20:52:43.6233Z OSConfigAgent Info: OSConfig Agent (version 20210219.00-0ubuntu1~20.1 ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verificati
[Bug 1902103] Re: Ensure default fstab options are sane and consistent across all images
fwiw LP: #1912835 is tracking this and is already checked in: https://git.launchpad.net/livecd-rootfs/commit/?id=33b7272a2331279b4c7aa8de73ed8a9069d0bd39 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902103 Title: Ensure default fstab options are sane and consistent across all images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking
Fixed in 20210222 daily images. Marking fix released. ** Changed in: systemd (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/1911059 Title: gce: 247.1-4ubuntu1 causes loss of networking To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1911059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915445] Re: [MIR] python-aws-requests-auth package
** Description changed: [Availability] python-aws-requests-auth was introduced in Bionic as a sync from Debian and carries no patches. It only depends on packages provided in main (python and python-requests). The package builds an architecture-independent package (all). [Rationale] This package is to be included in AWS cloud images the public cloud team builds going back to Bionic. As cloud images are to ship only packages from main this request is to see that happen. [Security] As there is network communication to authenticate this warrants a security review. The good news is the entire package is a couple of hundred lines of python. [Quality assurance] There are currently 0 open bug reports (excluding this one) about the package in Ubuntu or Debian. [Dependencies] python and python-requests, both in main already [Standards compliance] $ lintian python-aws-requests-auth_0.4.3-1.dsc W: python-aws-requests-auth source: newer-standards-version 4.5.1 (current is 4.5.0) [Maintenance] - TBD + Foundations team [Background information] This package allows you to authenticate to AWS with Amazon's signature version 4 signing process with the python requests library. - Upstream: + Upstream: https://github.com/davidmuller/aws-requests-auth - Launchpad page: + Launchpad page: https://launchpad.net/ubuntu/+source/python-aws-requests-auth - Ubuntu bugs: + Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth - Debian Package Tracker: + Debian Package Tracker: https://tracker.debian.org/pkg/python-aws-requests-auth - Debian bugs: + Debian bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=python-aws-requests-auth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915445 Title: [MIR] python-aws-requests-auth package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth/+bug/1915445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915445] [NEW] [MIR] python-aws-requests-auth package
Public bug reported: [Availability] python-aws-requests-auth was introduced in Bionic as a sync from Debian and carries no patches. It only depends on packages provided in main (python and python-requests). The package builds an architecture-independent package (all). [Rationale] This package is to be included in AWS cloud images the public cloud team builds going back to Bionic. As cloud images are to ship only packages from main this request is to see that happen. [Security] As there is network communication to authenticate this warrants a security review. The good news is the entire package is a couple of hundred lines of python. [Quality assurance] There are currently 0 open bug reports (excluding this one) about the package in Ubuntu or Debian. [Dependencies] python and python-requests, both in main already [Standards compliance] $ lintian python-aws-requests-auth_0.4.3-1.dsc W: python-aws-requests-auth source: newer-standards-version 4.5.1 (current is 4.5.0) [Maintenance] TBD [Background information] This package allows you to authenticate to AWS with Amazon's signature version 4 signing process with the python requests library. Upstream: https://github.com/davidmuller/aws-requests-auth Launchpad page: https://launchpad.net/ubuntu/+source/python-aws-requests-auth Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth Debian Package Tracker: https://tracker.debian.org/pkg/python-aws-requests-auth Debian bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=python-aws-requests-auth ** Affects: python-aws-requests-auth (Ubuntu) Importance: Undecided Status: New ** Description changed: [Availability] python-aws-requests-auth was introduced in Bionic as a sync from Debian and carries no patches. It only depends on packages provided in main (python and python-requests). The package builds an architecture-independent package (all). [Rationale] This package is to be included in AWS cloud images the public cloud team builds going back to Bionic. As cloud images are to ship only packages from main this request is to see that happen. [Security] As there is network communication to authenticate this warrants a security review. The good news is the entire package is a couple of hundred lines of python. [Quality assurance] There are currently 0 open bug reports (excluding this one) about the package in Ubuntu or Debian. [Dependencies] python and python-requests, both in main already [Standards compliance] $ lintian python-aws-requests-auth_0.4.3-1.dsc W: python-aws-requests-auth source: newer-standards-version 4.5.1 (current is 4.5.0) [Maintenance] TBD [Background information] - This package allows you to authenticate to AWS with Amazon's signature version 4 signing process with the python requests library. + This package allows you to authenticate to AWS with Amazon's signature version 4 signing process with the python requests library. - Upstream: https://github.com/davidmuller/aws-requests-auth - Launchpad page: https://launchpad.net/ubuntu/+source/python-aws-requests-auth - Ubuntu bugs: https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth - Debian Package Tracker: https://tracker.debian.org/pkg/python-aws-requests-auth - Debian bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=python-aws-requests-auth + Upstream: + https://github.com/davidmuller/aws-requests-auth + Launchpad page: + https://launchpad.net/ubuntu/+source/python-aws-requests-auth + Ubuntu bugs: + https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth + Debian Package Tracker: + https://tracker.debian.org/pkg/python-aws-requests-auth + Debian bugs: + https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=python-aws-requests-auth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915445 Title: [MIR] python-aws-requests-auth package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-aws-requests-auth/+bug/1915445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911448] Re: Please update to upstream release 20201217.02
There are build failures in Xenial on powerpc and Focal on riscv64. These packages are not used on these architectures at all as the Google cloud does not support these architectures. Additionally, these are new packages that have not existed before, so this is not a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911448 Title: Please update to upstream release 20201217.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1911448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905986] Re: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead
@balint Here are my logs following the test case: https://pastebin.ubuntu.com/p/wrjK5nx8cW/ google-compute-engine gets held back, but not gce-compute-image-packages as the test case says. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905986 Title: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1905986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900897] Re: Please build the package as upstream does
Build logs from Groovy package in proposed: https://launchpadlibrarian.net/517240236/buildlog_ubuntu-groovy-amd64.google-osconfig-agent_20210112.00-0ubuntu1~20.10.0_BUILDING.txt.gz Verify the build flags: dh_auto_build -O--buildsystem=golang -- -ldflags="-s -w -X main.version=20210112.00-0ubuntu1~20.10.0" Which matches the test case above. Marking verification-done. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900897 Title: Please build the package as upstream does To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1900897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911454] Re: Update gce-compute-image-packages to 20201222.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. >From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. Groovy testing was done by updating an existing image. I verified: 1) the versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. My notes and logs are below. ## Xenial Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~16.04.0 google-compute-engine20201222.00-0ubuntu2~16.04.0 google-compute-engine-oslogin20210122.00-0ubuntu1~16.04.0 google-guest-agent 20201217.02-0ubuntu1~16.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:42:01 UTC; 10min ago Main PID: 1692 (google_guest_ag) Tasks: 12 Memory: 20.3M CPU: 557ms CGroup: /system.slice/google-guest-agent.service └─1692 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:01 UTC; 10min ago Process: 1350 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 1350 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:10 UTC; 11min ago Process: 2275 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2275 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:42:02 UTC; 11min ago Process: 1804 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 1804 (code=exited, status=0/SUCCESS) ## Bionic Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~18.04.0 google-compute-engine 20201222.00-0ubuntu2~18.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~18.04.0 google-guest-agent 20201217.02-0ubuntu1~18.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:41:32 UTC; 4min 2s ago Main PID: 1790 (google_guest_ag) Tasks: 12 (limit: 4671) CGroup: /system.slice/google-guest-agent.service └─1790 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:29 UTC; 4min 31s ago Main PID: 1473 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:49 UTC; 8min ago Process: 2858 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2858 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:41:34 UTC; 8min ago Main PID: 1873 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4671) CGroup: /system.slice/google-shutdown-scripts.service ## Focal Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~20.04.0 google-compute-engine 20201222.00-0ubuntu2~20.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~20.04.0 google-guest-agent 20201217.02-0ubuntu1~20.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Lo
[Bug 1911448] Re: Please update to upstream release 20201217.02
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. >From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. Groovy testing was done by updating an existing image. I verified: 1) the versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. My notes and logs are below. ## Xenial Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~16.04.0 google-compute-engine20201222.00-0ubuntu2~16.04.0 google-compute-engine-oslogin20210122.00-0ubuntu1~16.04.0 google-guest-agent 20201217.02-0ubuntu1~16.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:42:01 UTC; 10min ago Main PID: 1692 (google_guest_ag) Tasks: 12 Memory: 20.3M CPU: 557ms CGroup: /system.slice/google-guest-agent.service └─1692 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:01 UTC; 10min ago Process: 1350 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 1350 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:10 UTC; 11min ago Process: 2275 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2275 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:42:02 UTC; 11min ago Process: 1804 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 1804 (code=exited, status=0/SUCCESS) ## Bionic Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~18.04.0 google-compute-engine 20201222.00-0ubuntu2~18.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~18.04.0 google-guest-agent 20201217.02-0ubuntu1~18.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:41:32 UTC; 4min 2s ago Main PID: 1790 (google_guest_ag) Tasks: 12 (limit: 4671) CGroup: /system.slice/google-guest-agent.service └─1790 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:29 UTC; 4min 31s ago Main PID: 1473 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:49 UTC; 8min ago Process: 2858 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2858 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:41:34 UTC; 8min ago Main PID: 1873 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4671) CGroup: /system.slice/google-shutdown-scripts.service ## Focal Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~20.04.0 google-compute-engine 20201222.00-0ubuntu2~20.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~20.04.0 google-guest-agent 20201217.02-0ubuntu1~20.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Lo
[Bug 1911633] Re: Please update to upstream release 20210108.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. >From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. Groovy testing was done by updating an existing image. I verified: 1) the versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. My notes and logs are below. ## Xenial Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~16.04.0 google-compute-engine20201222.00-0ubuntu2~16.04.0 google-compute-engine-oslogin20210122.00-0ubuntu1~16.04.0 google-guest-agent 20201217.02-0ubuntu1~16.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:42:01 UTC; 10min ago Main PID: 1692 (google_guest_ag) Tasks: 12 Memory: 20.3M CPU: 557ms CGroup: /system.slice/google-guest-agent.service └─1692 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:01 UTC; 10min ago Process: 1350 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 1350 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:42:10 UTC; 11min ago Process: 2275 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2275 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:42:02 UTC; 11min ago Process: 1804 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 1804 (code=exited, status=0/SUCCESS) ## Bionic Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~18.04.0 google-compute-engine 20201222.00-0ubuntu2~18.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~18.04.0 google-guest-agent 20201217.02-0ubuntu1~18.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-02-05 20:41:32 UTC; 4min 2s ago Main PID: 1790 (google_guest_ag) Tasks: 12 (limit: 4671) CGroup: /system.slice/google-guest-agent.service └─1790 /usr/bin/google_guest_agent $ systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:29 UTC; 4min 31s ago Main PID: 1473 (code=exited, status=0/SUCCESS) $ systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2021-02-05 20:41:49 UTC; 8min ago Process: 2858 ExecStart=/usr/bin/google_metadata_script_runner startup (code=exited, status=0/SUCCESS) Main PID: 2858 (code=exited, status=0/SUCCESS) $ systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2021-02-05 20:41:34 UTC; 8min ago Main PID: 1873 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4671) CGroup: /system.slice/google-shutdown-scripts.service ## Focal Package versions: gce-compute-image-packages 20201222.00-0ubuntu2~20.04.0 google-compute-engine 20201222.00-0ubuntu2~20.04.0 google-compute-engine-oslogin 20210122.00-0ubuntu1~20.04.0 google-guest-agent 20201217.02-0ubuntu1~20.04.0 $ systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Lo
[Bug 1911689] Re: Please update to upstream release 20210112.00
Based on comments from Google, the initial MIR issues are resolved with the code found in the following tag: https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20210202.00 The next steps would be to package that version up, upload the new version into proposed, and get a re-review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911689 Title: Please update to upstream release 20210112.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1911689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896443] Re: The latest Ubuntu base image for armhf return random values for date/time
I am adding docker.io package to the affects, as the versions in bionic (19.03.6) and focal (19.03.8) are just behind the 19.03.9 version required with a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896443 Title: The latest Ubuntu base image for armhf return random values for date/time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896443] Re: The latest Ubuntu base image for armhf return random values for date/time
Hi, Thanks for the link about libseccomp. After reading that link and a couple of bugs on Github about this it seems the root cause is due to containers of newer releases (e.g. 20.04), which make syscalls that hosts with older software might not know about. To resolve then, users need to: 1) Use Docker version 19.03.9 or newer 2) Ensure the host has libseccomp version of 2.4.2 or higher. libseccomp is already 2.4.3 in all supported versions of Ubuntu and appears to have the newer syscalls listed. I am marking this as invalid for the "cloud-images" project as it is clear this is not an Ubuntu docker image issue. ** Changed in: cloud-images Status: Incomplete => Invalid ** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896443 Title: The latest Ubuntu base image for armhf return random values for date/time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901042] Re: Unable to inspect configuration of running google-guest-agent
agreed - I can't mark it as won't fix so I will mark it invalid. ** Changed in: google-guest-agent (Ubuntu) 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/1901042 Title: Unable to inspect configuration of running google-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/google-guest-agent/+bug/1901042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911478] Re: Please backport golang 1.13 to Bionic and Xenial
Marking verification done for versions 1.13.8-1ubuntu1~16.04.2 and 1.13.8-1ubuntu1~18.04.2 Steps were the same as previously: 1. Added proposed universe 2. Installed golang-1.13 3. Verified version output from test case 4. Git cloned google guest-agent (https://github.com/GoogleCloudPlatform/guest-agent) 5. Built package successfully Logs --- Xenial: https://pastebin.ubuntu.com/p/bCnP9Bk2k2/ Bionic: https://pastebin.ubuntu.com/p/642Sx35PHS/ ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911478 Title: Please backport golang 1.13 to Bionic and Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.13/+bug/1911478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911478] Re: Please backport golang 1.13 to Bionic and Xenial
Marking verification done for xenial, logs: https://pastebin.ubuntu.com/p/YkDsDygz9k/ Same steps as above for bionic. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911478 Title: Please backport golang 1.13 to Bionic and Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.13/+bug/1911478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911478] Re: Please backport golang 1.13 to Bionic and Xenial
Marking verification done for bionic, logs: https://pastebin.ubuntu.com/p/zKqJMq22BC/ 1. Added proposed universe 2. Installed golang-1.13 3. Verified version output from test case 4. Git cloned google guest-agent (https://github.com/GoogleCloudPlatform/guest-agent) 5. Built package successfully Not sure if the package actually does all that it should or even works, but it did build. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911478 Title: Please backport golang 1.13 to Bionic and Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.13/+bug/1911478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901906] Re: amd64 images should have correct set of bootloaders installed
The regression that was previously seen with the SRU is now fixed [1] and therefore I am marking this as verification-done-xenial. [1] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/l/livecd- rootfs/20210112_234252_88c0d@/log.gz ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901906 Title: amd64 images should have correct set of bootloaders installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1901906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking
Greater output of journalctl: https://pastebin.canonical.com/p/XJzPMHrSbx/ ** Description changed: Summary === On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud instance to loose network access. Expected Result === Working network access Actual Result === After upgrade, network access is lost and serial console is filled with messages about IPv4 martian source and ll header, see below. Steps to Reproduce === 1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image 2. sudo apt update - 3. sudo apt install systems + 3. sudo apt install systemd 4. ssh is lost The images, built with this version do not appear to be able to start networking. Logs === Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915720] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915724] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978762] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978803] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042242] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042302] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105412] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105448] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168141] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168178] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 $ journalctl --no-pager -u systemd-net -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 21:52:03 UTC. -- Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service... Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change detected, ens4 has been renamed to eth0. Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service. Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change detected, eth0 has been renamed to ens4. Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes received from DHCP server: ignoring router option Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 lease lost Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd.service: Succeeded. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration completed Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911059 Title: gce: 247.1-4ubuntu1 causes loss of networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911059] Re: gce: 247.1-4ubuntu1 causes loss of networking
$ sudo journalctl --no-pager -u systemd-networkd-wait-online.service -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 22:01:17 UTC. -- Jan 11 21:30:35 ubuntu systemd[1]: Starting Wait for Network to be Configured... Jan 11 21:30:37 ubuntu systemd-networkd-wait-online[416]: managing: ens4 Jan 11 21:30:37 ubuntu systemd[1]: Finished Wait for Network to be Configured. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd-wait-online.service: Succeeded. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Wait for Network to be Configured. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Wait for Network to be Configured... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Wait for Network to be Configured... Jan 11 21:39:27 powersj-hirsuite-20210107 systemd-networkd-wait-online[2451]: Event loop failed: Connection timed out Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jan 11 21:39:27 powersj-hirsuite-20210107 systemd[1]: Failed to start Wait for Network to be Configured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911059 Title: gce: 247.1-4ubuntu1 causes loss of networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911059] [NEW] gce: 247.1-4ubuntu1 causes loss of networking
Public bug reported: Summary === On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud instance to loose network access. Expected Result === Working network access Actual Result === After upgrade, network access is lost and serial console is filled with messages about IPv4 martian source and ll header, see below. Steps to Reproduce === 1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image 2. sudo apt update 3. sudo apt install systems 4. ssh is lost The images, built with this version do not appear to be able to start networking. Logs === Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915720] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915724] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978762] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.978803] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042242] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.042302] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105412] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.105448] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168141] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 484.168178] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 $ journalctl --no-pager -u systemd-net -- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11 21:52:03 UTC. -- Jan 11 21:30:35 ubuntu systemd[1]: Starting Network Service... Jan 11 21:30:35 ubuntu systemd-networkd[413]: Enumeration completed Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Interface name change detected, ens4 has been renamed to eth0. Jan 11 21:30:35 ubuntu systemd[1]: Started Network Service. Jan 11 21:30:35 ubuntu systemd-networkd[413]: eth0: Interface name change detected, eth0 has been renamed to ens4. Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: IPv6 successfully enabled Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Link UP Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Gained carrier Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 Jan 11 21:30:35 ubuntu systemd-networkd[413]: ens4: Classless static routes received from DHCP server: ignoring router option Jan 11 21:30:37 ubuntu systemd-networkd[413]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[413]: ens4: DHCPv6 lease lost Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopping Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: systemd-networkd.service: Succeeded. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Stopped Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Starting Network Service... Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: Gained IPv6LL Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: Enumeration completed Jan 11 21:37:27 powersj-hirsuite-20210107 systemd[1]: Started Network Service. Jan 11 21:37:27 powersj-hirsuite-20210107 systemd-networkd[2446]: ens4: DHCPv4 address 10.138.0.56/32 via 10.138.0.1 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gce: 247.1-4ubuntu1 causes loose of networking + gce: 247.1-4ubuntu1 causes loss of networking ** Description changed: Summary === - On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud instance to lose network access. + On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud instance to loose network access. Expected Result === Working network access Actual Result === After upgrade, network access is lost and serial console is filled with messages about IPv4 martian source and ll header, see below. Steps to Reproduce === 1. Launch `daily-ubuntu-2104-hirsute-v20210107` the last known good image 2. sudo apt update 3. sudo apt install systems 4. ssh is lost The images, built with this version do not appear to be able to start networking. Logs === Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915720] IPv4: martian source 10.138.0.56 from 169.254.169.254, on dev ens4 Jan 11 21:38:32 powersj-hirsuite-20210107 kernel: [ 483.915724] ll header: : 42 01 0a 8a 00 38 42 01 0a 8a 00 01 08 00 Jan 11 21:38:32 p
[Bug 1911050] Re: AttributeError: 'array.array' object has no attribute 'tostring'
This is not limited to GCE cloud images, but also the KVM images from: https://cloud-images.ubuntu.com/hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911050 Title: AttributeError: 'array.array' object has no attribute 'tostring' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1911050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911050] [NEW] AttributeError: 'array.array' object has no attribute 'tostring'
Public bug reported: Summary === Landscape client MOTD is throwing an exception Hirsuite, which shows up in the MOTD on launch. Expected Result === No Exceptions Actual result === In the MOTD, the following is printed: => There were exceptions while processing one or more plugins. See /var/log/landscape/sysinfo.log for more information. The result of that file is: 2021-01-11 19:40:34,309 ERRORNetwork plugin raised an exception. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/landscape/sysinfo/sysinfo.py", line 99, in run result = plugin.run() File "/usr/lib/python3/dist-packages/landscape/sysinfo/network.py", line 36, in run device_info = self._get_device_info() File "/usr/lib/python3/dist-packages/landscape/lib/network.py", line 163, in get_active_device_info speed, duplex = get_network_interface_speed( File "/usr/lib/python3/dist-packages/landscape/lib/network.py", line 249, in get_network_interface_speed res = status_cmd.tostring() AttributeError: 'array.array' object has no attribute 'tostring' Steps to reproduce === 1. Launch a GCE cloud image for Hirsute (20210106) 2. SSH into the system 3. Note the MOTD message landscape-common: Installed: 19.12-0ubuntu7 Candidate: 19.12-0ubuntu7 Version table: *** 19.12-0ubuntu7 500 500 http://us-west1.gce.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: landscape-client (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/1911050 Title: AttributeError: 'array.array' object has no attribute 'tostring' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1911050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666570] Re: Post install script has error in RegEx
** Changed in: tomcat7 (Ubuntu Trusty)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu Zesty)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu Xenial)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat7 (Ubuntu Xenial)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu Yakkety)
Assignee: Joshua Powers (powersj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666570
Title:
Post install script has error in RegEx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1666570/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Hi! The packages were released into the archive on December 15, 2020. Our last build of 2020 was on December 10. The first daily builds of 2021 should have this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909727] [NEW] snap always says refreshing: google-cloud-sdk
Public bug reported: When I run `sudo snap refresh`, even when there are no snaps out of date, the google-cloud-sdk snap will say that it is refreshed: ❯ date && sudo snap refresh --list Wed Dec 30 08:52:43 PM PST 2020 All snaps up to date. ~ took 2s ❯ date && sudo snap refresh Wed Dec 30 08:52:47 PM PST 2020 google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) refreshed ~ ❯ date && sudo snap refresh Wed Dec 30 08:52:49 PM PST 2020 google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) refreshed ~ ❯ date && sudo snap refresh Wed Dec 30 08:52:51 PM PST 2020 google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) refreshed The logs show that no updates are available either: Dec 30 20:52:48 ryzen snapd[1219]: storehelpers.go:551: cannot refresh: snap has no updates available: "bitwarden", "chromium", "code", "core", "core18", "core20", "discord", "docker", "gnome-3-28-1804", "google-cloud-sdk", "goreleaser", "gtk-common-themes", "hugo", "kubectl", "kubernetes-test-eks", "lpshipit", "lxd", "multipass", "node", "snapcraft", "spotify", "ubuntu-bug-triage", "ubuntu-cloud-image", "ubuntu-iso-download", "vault", "youtube-dl" Dec 30 20:52:50 ryzen snapd[1219]: storehelpers.go:551: cannot refresh: snap has no updates available: "bitwarden", "chromium", "code", "core", "core18", "core20", "discord", "docker", "gnome-3-28-1804", "google-cloud-sdk", "goreleaser", "gtk-common-themes", "hugo", "kubectl", "kubernetes-test-eks", "lpshipit", "lxd", "multipass", "node", "snapcraft", "spotify", "ubuntu-bug-triage", "ubuntu-cloud-image", "ubuntu-iso-download", "vault", "youtube-dl" Dec 30 20:52:52 ryzen snapd[1219]: storehelpers.go:551: cannot refresh: snap has no updates available: "bitwarden", "chromium", "code", "core", "core18", "core20", "discord", "docker", "gnome-3-28-1804", "google-cloud-sdk", "goreleaser", "gtk-common-themes", "hugo", "kubectl", "kubernetes-test-eks", "lpshipit", "lxd", "multipass", "node", "snapcraft", "spotify", "ubuntu-bug-triage", "ubuntu-cloud-image", "ubuntu-iso-download", "vault", "youtube-dl" ``` If I uninstall and install the google-cloud-sdk it continues to happen: ❯ sudo snap remove google-cloud-sdk google-cloud-sdk removed ~ ❯ sudo snap refresh All snaps up to date. ~ ❯ sudo snap install google-cloud-sdk --classic google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) installed ~ took 15s ❯ sudo snap refresh google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) refreshed ~ ❯ sudo snap refresh google-cloud-sdk 321.0.0 from Cloud SDK (google-cloud-sdk✓) refreshed System Info --- Ubuntu 20.10 snapd 2.48+20.10 core 16-2.48 10577 latest/stable canonical✓ core core18 202012101944 latest/stable canonical✓ base core20 20201210904latest/stable canonical✓ base google-cloud-sdk 321.0.0 162latest/stable google-cloud-sdk✓ classic ** Affects: snapd (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/1909727 Title: snap always says refreshing: google-cloud-sdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1909727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908548] [NEW] Add manpages to packaging branches
Public bug reported: Master has manpages [1] and even the debian directory file for including the manpages [2], however, it looks like the packaging branches do not have the required debian/manpages file. Please include this file so future SRUs can have man pages included. [1] https://github.com/canonical/cloud-init/tree/master/doc/man [2] https://github.com/canonical/cloud-init/commit/796f58081766c51cdb36e770541d32f84f595371 ** Affects: cloud-init (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/1908548 Title: Add manpages to packaging branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1908548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901906] Re: amd64 images should have correct set of bootloaders installed
The xenial verification has failed as once again the package names are not correct. I have an MP up [1] which reverts back to the original behavior. Xenial's behavior around shim is not the same as later releases. This work is not something scheduled till next year. Bionic [2] and Focal [3] are sru verification passed as images are building, no longer including extra packages, and are launching successfully. The build logs linked you can search for "chroot mountpoint apt-get install -qqy grub-pc shim-signed" to verify the new version is getting shipped. [1] https://code.launchpad.net/~powersj/livecd-rootfs/+git/livecd-rootfs-1/+merge/394910 [2] https://i510533839.restricted.launchpadlibrarian.net/510533839/buildlog_ubuntu_bionic_amd64_amd64-disk-image_qcow2_squashfs_tarball_vagrant_vmdk_azure_azure-pro_azure-pro-fips_dimension-data_hyperv-gcs_wsl_maas_softlayer_cpc_BUILDING.txt.gz?token=HPgBwmkbztJpx1ZSZbwW0Ln2XvmF0Clh [3] https://i510437212.restricted.launchpadlibrarian.net/510437212/buildlog_ubuntu_focal_amd64_amd64-disk-image_kvm_qcow2_squashfs_tarball_vagrant_vmdk_azure_azure-pro_hyperv-gcs_wsl_maas_softlayer_cpc_BUILDING.txt.gz?token=pxHwRfRH0CVNcL6Rj6fhcltmq1SQDtDH ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial ** Tags added: verification-done-bionic verification-done-focal verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901906 Title: amd64 images should have correct set of bootloaders installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1901906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904756] Re: [feature request] ua status to provide unattended-upgrades status
Hi Eric, I like the idea and have a few questions about how the client's behavior would interact with unattended-upgrades: For example, how should the client determine what status to report? If the user has at least the default config enabled is that enough for the client to report yes? What if the security pocket gets disabled? If a user wanted to disable unattended-upgrades, would the client remove the package? If a user wanted to enable unattended-upgrades, would the client enable the default config? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904756 Title: [feature request] ua status to provide unattended-upgrades status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1904756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630274] Re: mount-image-callback may not mount overlay when it could
Updating the tags so this turns green on the SRU board. Was `verificiaton-complete` but it should be `verification-done` :) ** Tags removed: verification-complete verification-complete-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630274 Title: mount-image-callback may not mount overlay when it could To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1630274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699913] Re: /var/lib/apt/lists has content in partner-images/Docker tarballs, which becomes stale quickly
** Changed in: cloud-images 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/1699913 Title: /var/lib/apt/lists has content in partner-images/Docker tarballs, which becomes stale quickly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1699913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756420] Re: replace grub-legacy-ec2 with pv-grub-menu
I am going to mark this as won't fix for cloud-images. grub-legacy-ec2 is only shipped in Xenial and Bionic. In Cosmic it was removed from the seed, so releases after that do not even have it. Xenial is coming to end of standard support and needs it for HVM support. I don't see any major changes happening to it now. Bionic images generally pull grub-legacy-ec2 out of the image. Therefore, I don't believe there is much further work for the cloud- images task. Feel free to respond if you think otherwise. Thanks! ** Changed in: cloud-images Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756420 Title: replace grub-legacy-ec2 with pv-grub-menu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1756420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756420] Re: replace grub-legacy-ec2 with pv-grub-menu
And by HVM support, I actually mean PV support, doh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756420 Title: replace grub-legacy-ec2 with pv-grub-menu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1756420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754055] Re: artful image doesn't launch cloud-init on vsphere
Hi, Thanks for taking the time to file a bug. I am going to add the cloud- init project to this bug and mark it incomplete. Given artful was a while ago and no longer supported, if you are still having your issue, could you provide some logs? Thanks! ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete ** 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/1754055 Title: artful image doesn't launch cloud-init on vsphere To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1754055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767131] Re: Pre-seeded snaps are not necessarily available for use in cloud-init user-data
** Changed in: cloud-images 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/1767131 Title: Pre-seeded snaps are not necessarily available for use in cloud-init user-data To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1767131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882374] Re: Support inclusion of snap from specific track/channel/branch
** Changed in: cloud-images Status: Triaged => 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/1882374 Title: Support inclusion of snap from specific track/channel/branch To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1882374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
** Changed in: cloud-images 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/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896604] Re: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances
** Changed in: cloud-images Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896604 Title: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896443] Re: The latest Ubuntu base image for armhf return random values for date/time
** 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/1896443 Title: The latest Ubuntu base image for armhf return random values for date/time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1896443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
# journalctl -u systemd-networkd https://paste.ubuntu.com/p/9M3xwgwgMj/ # systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 20:59:46 UTC; 19min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 1107 (code=exited, status=1/FAILURE) Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Aug 14 20:59:46 g systemd[1]: Stopped Network Service. Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Start request repeated too quickly. Aug 14 20:59:46 g systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 20:59:46 g systemd[1]: Failed to start Network Service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
Here are my notes from using a Groovy LXD container: Expected Results --- $ resolvectl status | grep "DNS Server" Current DNS Server: 192.168.100.1 DNS Servers: 192.168.100.1 Actual Results --- $ resolvectl status Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 24 (eth0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Steps to reproduce --- $ lxc launch ubuntu-daily:g g $ lxc exec g bash # cat /etc/cloud/build.info build_name: server serial: 20200813 # sudo apt update -qq # apt-cache policy systemd systemd: Installed: 245.7-1ubuntu1 Candidate: 246-2ubuntu1 Version table: 246-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages *** 245.7-1ubuntu1 100 100 /var/lib/dpkg/status # resolvectl status | grep "DNS Server" Current DNS Server: 192.168.100.1 DNS Servers: 192.168.100.1 # sudo apt install --yes systemd ... Job for systemd-networkd.service failed because the control process exited with error code. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Removing obsolete conffile /etc/dhcp/dhclient-enter-hooks.d/resolved ... ... # resolvectl status Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 24 (eth0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
** Attachment added: "journal short-precise" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401580/+files/journal.short -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
** Attachment added: "journal from lxd" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401579/+files/journal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
Thanks for the analysis! systemd appears to set this value in: ./sysctl.d/50-pid-max.conf:kernel.pid_max = 4194304 One possible solution is we could override this in our minimal images only by setting the value to the lower value in /etc/sysctl.d/90-override.conf ** 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/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Based on the update above, #17, I am adding the open-iscsi package task. ** Also affects: open-iscsi (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/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
Similar to bug 1888000, it appears this failure has also always been present. I verified this against the focal 20200423 (oldest release with 5.4.0-1009-kvm) and 20200703 (newest release with 5.4.0-1018-kvm) serials. While this is no longer blocking image publication, is this something that could be fixed in order to prevent us from shipping with failed systemd units? Both images produce a failure similar to: Jul 20 12:15:30 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:15:30 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:15:30 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:15:30 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument ** Description changed: Overview --- - This is *blocking* new minimal image promotion. Starting on or around 20200714, the Focal minimal cloud images reported they failed to apply kernel variables during boot. - + It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units - Actual results --- $ sudo systemctl list-units --failed --no-legend - systemd-modules-load.service loaded failed failed Load Kernel Modules + systemd-sysctl.service loaded failed failed Apply Kernel Variables + From the journal: - Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE - Jul 17 10:30:12 ubuntu systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. - Jul 17 10:30:12 ubuntu systemd[1]: Failed to start Apply Kernel Variables. - Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory - Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). - Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). - Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory - Jul 17 10:30:12 ubuntu systemd-sysctl[134]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument + Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit + ed, code=exited, status=1/FAILURE + Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile + d with result 'exit-code'. + Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. + + Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker + nel/pid_max': Invalid argument Steps to reproduce --- - 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-focal/ - 2. multipass launch file:/// - 3. multipass exec -- sudo systemctl list-units --failed --no-legend - --- + $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img + $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal + $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend + + + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: - linux-restricted-modules-5.4.0-1018-kvm N/A - linux-backports-modules-5.4.0-1018-kvm N/A - linux-firmware
[Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Thanks for the review, it turns out that this failure has always been present. Going back to the Bionic 20180705 and Xenial 20180705, which were the first releases of minimal, also showed that the system "Failed to find module 'ib_iser'". Is this something that could be fixed in order to prevent us from shipping with failed systemd units? ** Description changed: Overview --- - This is *blocking* new minimal image promotion. Starting on or around 20200714, the Bionic and Xenial minimal cloud images reported they failed to load kernel modules. - + It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units - Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory - Steps to reproduce --- - 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-bionic/ - 2. multipass launch file:/// - 3. multipass exec -- sudo systemctl list-units --failed --no-legend - --- + $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img + $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal + $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend + + + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-1069-kvm N/A - linux-backports-modules-4.15.0-1069-kvm N/A - linux-firmware N/A + linux-restricted-modules-4.15.0-1069-kvm N/A + linux-backports-modules-4.15.0-1069-kvm N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
Apport info was collected and attached... moving to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Apport info was collected and attached... moving to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393621/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393619/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393613/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393617/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393615/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393611/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888000/+attachment/5393612/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393620/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888000] [NEW] Bionic/Xenial minimal cloud image: failed to apply load kernel module
Public bug reported: Overview --- This is *blocking* new minimal image promotion. Starting on or around 20200714, the Bionic and Xenial minimal cloud images reported they failed to load kernel modules. Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... >From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-bionic/ 2. multipass launch file:/// 3. multipass exec -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic uec-images ** Tags added: apport-collected bionic uec-images ** Description changed: Overview --- This is *blocking* new minimal image promotion. Starting on or around 20200714, the Bionic and Xenial minimal cloud images reported they failed to load kernel modules. Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-bionic/ 2. multipass launch file:/// 3. multipass exec -- sudo systemctl list-units --failed --no-legend + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevices
[Bug 1888001] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393616/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393622/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393614/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393618/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888001] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888001/+attachment/5393610/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888001 Title: Focal minimal cloud image: failed to apply kernel variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
