[Bug 1923616] Re: Please remove rax-nova-agent and xe-guest-utils from Hirsute
xe-guest-utils == brought in as part of a partner image. These partners are an LTS cloud, and have not taken a Focal image at this time. The company has also produced a new generation of their cloud. Those images do not include xe-guest-utils. >From CPCs perspective, it is safe to demote xe-guest-utils from Hirsute forward. If we need the package for J / 22.04, we can revisit having this package in main. rax-nova-agent == Discussion on 2021-04-13 internally certified that CPC does not have a commercial relationship with the cloud provider at this time. The CPC team has no requirement to continue to offer official support in main. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923616 Title: Please remove rax-nova-agent and xe-guest-utils from Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rax-nova-agent/+bug/1923616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925780] Re: armhf & arm64 image do not have cloud-init grub customizations
rcj and I had just been discussing this in relation to a new arm64 image. We are currently re-enabling the file for EC2 arm64 in our EC2 specific code. I took the workaround from our EC2 and implemented in our test image. We agreed that we'll need to get 999-cpc-fixes worked out more. The code that writes the mentioned file is: https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- cpc/hooks.d/chroot/999-cpc-fixes.chroot#n189 what everything from 125 to 189 is where I needed to get some more guidance to ensure everything would work on arm properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925780 Title: armhf & arm64 image do not have cloud-init grub customizations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1925780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902260] Re: systemd-detect-virt is missing on Groovy arm64 EC2 AMI
Confirmed not just for arm64, but also latest amd64 groovy builds amd64 ami: ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily- amd64-server-20201104 ~$ uname -a Linux ip-172-31-92-148 5.8.0-1011-aws #11-Ubuntu SMP Thu Oct 22 10:15:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ~$ ls /usr/bin/systemd-detect-virt ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory arm64 ami: ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20201104 ~$ uname -a Linux ip-172-31-52-203 5.8.0-1011-aws #11-Ubuntu SMP Thu Oct 22 10:16:43 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ~$ ls /usr/bin/systemd-detect-virt ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory compared to latest focal release: arm64 ami: 099720109477/ubuntu/images/hvm-ssd/ubuntu- focal-20.04-arm64-server-20200720 ~$ uname -a Linux ip-172-31-48-176 5.4.0-1020-aws #20-Ubuntu SMP Fri Jul 10 05:53:22 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ~$ ls /usr/bin/systemd-detect-virt /usr/bin/systemd-detect-virt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902260 Title: systemd-detect-virt is missing on Groovy arm64 EC2 AMI To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
** Summary changed: - systemd-detect-virt is missing on Groovy arm64 EC2 AMI + systemd-detect-virt is missing on Groovy EC2 AMI ** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+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
I've confirmed the Groovy change using the following test: 1. downloaded source for proposed package 2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build 3. used Virtualbox to load the ova and vmdk 4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded 5. created a custom recipe with the proposed code from git(emulating our exact build process) 6. ran a livebuild from the uploaded recipe 7. downloaded the ova and vmdk 8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded. ** Tags removed: verification-needed-groovy ** Tags added: 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/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 1889688] Re: [MIR] nvme-cli
There is no specific need for this to be included in a seed. It's required for the GKE images, and we maintain cloud specific install lists, separate from the general seeds. Server or cloud-images would be too inclusive (we'd need to script uninstalling it in the other images). Is this where the "Supported" seed is used? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889688 Title: [MIR] nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1889688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889688] Re: [MIR] nvme-cli
Thanks! I also just learned about: platform.$SUITE/supported-cloud Based on the format, I'd say this package should be in that seed, in the = Per-cloud-image packages = section with a comment: # For GKE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889688 Title: [MIR] nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1889688/+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
I've confirmed the Bionic change using the following test: 1. downloaded source for proposed package 2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build 3. used Virtualbox to load the ova and vmdk 4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded 5. created a custom recipe with the proposed code from git(emulating our exact build process) 6. ran a livebuild from the uploaded recipe 7. downloaded the ova and vmdk 8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded. 9 checked build logs for bartender and lp to ensure that a diff was generated for the 2 headers and that ddb.toolsVersion = "2147483647" was present in the diff presented in the log (example in #12) ** 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/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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
I've confirmed the Focal change using the following test: 1. downloaded source for proposed package 2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build 3. used Virtualbox to load the ova and vmdk 4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded 5. created a custom recipe with the proposed code from git(emulating our exact build process) 6. ran a livebuild from the uploaded recipe 7. downloaded the ova and vmdk 8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded. 9 checked build logs for bartender and lp to ensure that a diff was generated for the 2 headers and that ddb.toolsVersion = "2147483647" was present in the diff presented in the log (example in #12) LP builds have been a bit slow today for images and recipes. For Xenial, I believe I have to wait for a fix in livecd-rootfs related to a different change. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
image builds are only built after the SRU process is complete and livecd-rootfs is in the updates pocket. This wiki page will help explain the SRU process in more detail: https://wiki.ubuntu.com/StableReleaseUpdates My verification is being done by building images against the livecd- rootfs project in proposed. After verification by all the bugs affecting a version of a package, a minimum 7 day wait period for community testing against proposed, the package will move to updates Once the package has been accepted into updates, the CPC pipeline will pick up the accepted version of livecd-rootfs, and create daily images. I'll update this ticket once we have confirmed daily builds for the suites that are still affected. -- 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 1896443] Re: The latest Ubuntu base image for armhf return random values for date/time
I've confirmed that running on kernel 4.19.97-v7l, available on the Raspbian image published on 2020-02-14 there are issues running `date`. it returns the Linux epoch date. the following containers are affected: ubuntu/focal ubuntu/groovy debian/bullseye there was not an issue with debian/buster, nor any of the other distros I tried. Passing: * alpine:latest * opensuse:leap * centos:7 * debian:buster I then ran a dist-upgrade, which upgrade the kernel from 4.19 to 5.4.51. I then ran `date` in the same containers. * ubuntu:focal returned random date/times in the epoch year * ubuntu:groovy returned epoch * debian:bullseye return epoch the previously passing containers all continued to work as expected. -- 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 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
latest Groovy vagrant image has removed virtualbox-guest-utils and now mounts properly. Any version equal to or newer than v20201006.0.0 will mount the guest folder. I'm still going to do some testing with the vagrant guest-utils plugin as well, just to see if it successfully pulls in a newer version. But otherwise the core issue has been fixed for the cloud image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
I did a test utilizing the vagrant plugin for installing guest-additions on the newly created Vagrant images (using the pre-installed guest-utils kernel module) `vagrant plugin install vagrant-vbguest` This failed in the same fashion, however, I was able to get an install log. It is attached as is the output from spinning up a test VM with `vagrant-vbguest` installed. ** Attachment added: "vagrant output from groovy image with vagrant-vbguest plugin installed" https://bugs.launchpad.net/cloud-images/+bug/1895862/+attachment/5418926/+files/failed_with_plug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
** Attachment added: "log from groovy VM attempting to install vbguest" https://bugs.launchpad.net/cloud-images/+bug/1895862/+attachment/5418927/+files/vbox-install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
I've marked cloud-images as Fixed-Released based upon the updated livecd-rootfs, and confirming that the latest Vagrant Box posted to https://app.vagrantup.com/ubuntu/boxes/groovy64. We can leave this open for the Virtualbox package and how we can deliver updates to virtualbox- guest-utils. But the original bug of being unable to mount shared folders is mitigated for the moment. ** Changed in: cloud-images/groovy Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
I've confirmed that the latest Vagrant box published has the fix. I've also confirmed that users can overwrite the default passing of the serial console to a File::NULL and write to a different file. For everyone affected, run a `vagrant box update` on Focal boxes. This will grab the latest box. If you cannot update your base, using the workaround of attaching a NULL handler will work. This is documented in the code attached to this MP, as well as below Vagrant cloud link to latest: https://app.vagrantup.com/ubuntu/boxes/focal64/versions/20201012.0.0 configuring a NULL file handler ``` config.vm.provider "virtualbox" do |vb| vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ] # Create a NULL serial port to skip console logging by default vb.customize [ "modifyvm", :id, "--uartmode1", "file", File::NULL ] end ``` ** Changed in: cloud-images/focal Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+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
** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => In Progress ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: cloud-images Status: Confirmed => In Progress ** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: cloud-images Importance: Undecided => High -- 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 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
@haggan-era, could you open a new bug on this issue? Please provide the following information: 1. version of Windows, vagrant, virtualbox, and Ruby in use on the Windows computer 2. the Vagrantfile used to create the new .box 3. any steps to reproduce the issue. On first smell it seems like a Ruby on Windows issue handling File::NULL. that was added Ruby 1.9.3 I think. I'd surmise that if you took the Vagrantfile, and ran the operation there, it'd work fine. Give that a try. If it is translating the object to a specific path reference, then that means File::NULL is platform dependent on creation of the box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+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
focal and bionic builds with this fix were not completed prior to the December holidays. Builds with the changes for focal and bionic should happen soon in 2021. Xenial is still awaiting a fix to be committed. -- 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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Focal Daily serial 20210112 has the expected change and is available for download: http://cloud-images.ubuntu.com/daily/server/focal/20210112/ Bionic Daily serial 20120112 has the expected change, and is available for download: http://cloud-images.ubuntu.com/daily/server/bionic/20210112/ Xenial: I am qualifying livecd-rootfs now. Once livecd-rootfs is qualified and moved to -updates, the cpc build process will take the change. -- 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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
I've verified a build on xenial using 2.408.65 1. downloaded source for proposed package 2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build 3. used Virtualbox to load the ova and vmdk 4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded ** Tags removed: verification-needed-xenial ** Tags added: 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/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 1898871] Re: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5)
We've confirmed this request for upgrading hardware version for our ova's. We have prioritized this on our backlog, and have it linked to 1895104 ** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898871 Title: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1898871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895104] Re: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi
Confirming this bug, as we've prioritized this work on our backlog. When we work on lp: 1898871, we'll ensure that the ova sets a serial port. ** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895104 Title: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Description changed: + SRU + + [IMPACT] + + * Users are unable to boot a vagrant image, as the boot time without a serial console connection exceeds the vagrant timeout + * bug is focal as well as latest devel devel release. + * Upload fixes the bug by creating a serial console connection to a null file + + [TEST CASE] + + * run livecd-rootfs from focal branch with vagrant target + * download and add the create vagrant box (vagrant box add --name focal-test-image + * vagrant init + * update Vagrant file to use focal-test-image as the image + * observe that image successfully boots (should boot in < 60s) + * vagrant halt + * update vagrant file to have a new serial connection and send to a log (this shows that the default NULL connection can be overridden by a local user. an example is in box Vagrantfile, findable in ~/.vagrant.d/boxes/focal-test-image/0/virtualbox/Vagrantfile) + * vagrant up and observe that a serial connection has been established, and a log is written + + [Regression Potential] + + * possibility of incorrect configuration, leading to either the serial + console not engaging properly, or a file being written instead of sent + to a NULL file. + + Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=t
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Description changed:
SRU
[IMPACT]
* Users are unable to boot a vagrant image, as the boot time without a serial
console connection exceeds the vagrant timeout
* bug is focal as well as latest devel devel release.
* Upload fixes the bug by creating a serial console connection to a null file
[TEST CASE]
- * run livecd-rootfs from focal branch with vagrant target
- * download and add the create vagrant box (vagrant box add
--name focal-test-image
- * vagrant init
- * update Vagrant file to use focal-test-image as the image
+ * tests require vagrant and virtualbox to be installed on the testing machine.
+ * livecd-rootfs build with ubuntu-cpc project
+ * download vagrant .box file and add (`vagrant box add --name
focal-test-image`)
+ * create testing directory and cd
+ * create Vagrantfile to use focal-test-image as the image
+ ```
+ # -*- mode: ruby -*-
+ # vi: set ft=ruby :
+ Vagrant.configure("2") do |config|
+ config.vm.box = "focal-test-image"
+ end
+ ```
+ * run `vagrant up`
* observe that image successfully boots (should boot in < 60s)
* vagrant halt
- * update vagrant file to have a new serial connection and send to a log (this
shows that the default NULL connection can be overridden by a local user. an
example is in box Vagrantfile, findable in
~/.vagrant.d/boxes/focal-test-image/0/virtualbox/Vagrantfile)
- * vagrant up and observe that a serial connection has been established, and a
log is written
+ * update vagrant file to have a new serial connection and send to a log (this
shows that the default NULL connection can be overridden by a local user).
+ ```
+ Vagrant.configure("2") do |config|
+ NOW = Time.now.strftime("%d.%m.%Y.%H:%M:%S")
+ FILENAME = "serial-debug-%s.log" % NOW
+ config.vm.box = "focal-test-image"
+ config.vm.provider "virtualbox" do |vb|
+vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
+vb.customize [ "modifyvm", :id, "--uartmode1", "file",
File.join(Dir.pwd, FILENAME) ]
+ end
+ end
+ ```
+ * run vagrant up and observe that a serial connection has been established,
and a log is written. Log should be named `serial-debug-$NOW.log` where $NOW is
the current date and time (of the vagrant up)
[Regression Potential]
- * possibility of incorrect configuration, leading to either the serial
- console not engaging properly, or a file being written instead of sent
- to a NULL file.
+ * possibility of incorrect configuration, leading to either the serial
console not engaging properly, or a file being written instead of sent to a
NULL file.
+ * configuration stanza could be incorrect depending upon version(such as
File::NULL not being available)
+
+ [ORIGINAL DESCRIPTION]
Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
extremely slow and the box always reboots once before completing a
successful boot. With default settings, this causes a timeout in
Vagrant waiting for SSH to be available. Setting a long enough timeout
it does eventually boot successfully. For comparison, `ubuntu/bionic64`
boots successfully in roughly 10 seconds on my machine.
This appears to be the big hang-up:
Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1]
enabled
Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0]
enabled
I have a hard time telling where exactly it reboots because my
/var/log/syslog only ends up with the second boot. I can watch it in
Virtualbox though and it suddenly reboots, then the second boot process
runs to completion. The long delay shown above happens both times
making the total time to a successful boot very long. Here is the head
of my /var/log/syslog:
Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel
File Systems.
Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall.
Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System...
Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File
System...
Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild
Hardware Database being skipped.
Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent
Storage...
Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform
Persistent Storage Archival being skipped.
Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed...
Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables...
Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users...
Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices.
[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
I did a test build using a branch of livecd-rootfs where I removed the code installing virtualbox-guest-utils. The vagrant box produced booted fine and mounted guest folders. This works on groovy on the 5.8.0 kernel. Looking at groovy, vboxsf, vboxguest, and vboxvideo are included as part of the linux-modules package. This was an update done in Focal on 5.4.0-48 and migrated forward. Moving forward for our creation of Vagrant boxes, we can remove the explicit install of vbox-guest-utils. https://packages.ubuntu.com/groovy/amd64/linux- modules-5.8.0-19-generic/filelist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895862] Re: vboxsf unable to mount old binary data in Groovy Vagrant box
** Also affects: cloud-images/groovy Importance: Undecided Status: Confirmed ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images/groovy Assignee: (unassigned) => John Chittum (jchittum) ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895862 Title: vboxsf unable to mount old binary data in Groovy Vagrant box To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
SRU for Focal testing.
Created 2 Vagrant boxes to cover the 2 main build cases of CPC (produced
of the Vagrant image and user of the hook changed)
box A: Created via ubuntu-bartender(https://github.com/chrisglass
/ubuntu-old-fashioned/tree/master/scripts/ubuntu-bartender) utilizing
the source download of the proposed package (found here in the web UI).
ran bartender using multipass as a provider with the following command
./ubuntu-bartender --livecd-rootfs-dir
/home/jchittum/dev01/troubleshooting/vagrant-testing/1874453/livecd-
rootfs --build-provider multipass -- --series focal --project ubuntu-cpc
--image-target vagrant
box B: Created via a Launchpad build utilizing a recipe pointed to
~livecd-rootfs ubuntu/focal. This created a livecd-rootfs package in a
personal PPA which was then used to run the build.
boxes were then added to the vagrant inventory
vagrant box add --name focal-sru-test-from-(bartender
|| lp)
2 directories were then created from-bartender & from-lp
Ran the following 2 test cases:
[Test Case 1]
-- vagrant up with minimal configuration --
1. made minimal Vagrantfiles in each directory
```
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "focal-sru-test-from-bartender" # Or from-lp
end
```
2. ran `time vagrant up`
3. observed that boxes successfully booted
4. observed that boxes booted in a reasonable amount of time (on my machine
~30s)
5. ensured the ability to SSH into the box
6. checked the guest system has mounted the default guest directory (./ on host
mounted to /vagrant on guest)
7. exited host and destroyed boxes (vagrant halt && vagrant destroy)
Both boxes worked.
[Test Case 2]
1. Update Vagrantfiles to override default serial connection and write file
```
Vagrant.configure("2") do |config|
NOW = Time.now.strftime("%d.%m.%Y.%H:%M:%S")
FILENAME = "serial-debug-%s.log" % NOW
config.vm.box = "focal-sru-test-from-bartender" # Or from-lp
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
vb.customize [ "modifyvm", :id, "--uartmode1", "file",
File.join(Dir.pwd, FILENAME) ]
end
end
```
2. ran `time vagrant up`
3. Observed that boxes successfully booted
4. observed the log file was created
5. observed that boxes booted in a reasonable amount of time (on my machine
~30s)
6. ensured the ability to SSH into the box
7. checked the guest system has mounted the default guest directory (./ on host
mounted to /vagrant on guest)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+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 was unable to reproduce with Ubuntu Focal 64 bit as the host. Could you provide the Host OS version. Focal is on a 5.4 kernel, and Bionic should have rolled to a 5.x kernel as well. my guess at this time is your host is a 32bit (from the armv7l listing in the kernel). if you let me know the Host OS version (not just kernel) I can work on reproducing. I'm flashing a Bionic 18.0.4.5 32bit image now for testing -- 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
I tested with Ubuntu Bionic 32bit and was unable to reproduce. Also unable to reproduce with a Focal 32bit. Both of these are running the 5.4 kernel though, so it may just be affecting 4.X series kernels. I'll flash a Raspbian Buster 32 bit and test on my Raspberry Pi 4 -- 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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
With the release of livecd-rootfs 2.408.65 in Xenial, cloud_images will take the package and produce builds. I will update the ticket when our next Xenial daily build goes out built with this version -- 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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
reinstall attempted today. CD image downloaded on 20210124 and USB created via Rufus on Windows. Attempted install, indicated Install Third-Party Drivers. Crashed at the very end, after updating packages. hardware is a System 76 Gazelle (2019). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+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
vmware-gos-Yuhua (yhzou) and cloud users: The latest Xenial daily build has the required changes, serial 20210127 http://cloud-images.ubuntu.com/xenial/20210127/ The vmdk and ova were both validated in the following way: 1) downloaded vmdka and ova from http://cloud-images.ubuntu.com/xenial/20210127/ 2) launch virtualbox 3) select Add and choose the vmdk 4) give unique name (xenial-jchittum-test) and ensure linux ubuntu is chosen for OS info. 5) Go to settings, and set a serial port (file) and added a working cloud_init (sets ubuntu password and imports my launchpad id) 6) boot image 7) check `cloud-init status`, `systemctl is-system-running`, `uname -a` to ensure the services are up, running, complete, and correct kernel is up 8) quit and terminate VM 9) Import .ova 10) repeat steps 4-8 Images were found to generally be working and the required change was found in our build logs ** Changed in: cloud-images Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
** Tags removed: verification-needed ** Tags added: 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/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 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
also affects other cloud-images beyond ec2. confirmed in GCE as well, and may affect other clouds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889688] [NEW] [MIR] nvme-cli
Public bug reported: [Availability] Package is available in Universe. Builds are green for all arches specified [Rationale] This is a request from Google as they utilize nvme-cli to manage nvme drives in their cloud. The package offers tools for managing nvme drives, including nvme over fabric (NVMEoF). NVMEoF is of particular interest as cloud providers build out with nvme drives. [Security] No current security advisories. Has been a part of Universe since Xenial, and shows supportability (the source in Github is updated with regularity [within 1 hour of me opening the page, with regular commits including 11 merged PRs in the past 30 days]) [Quality assurance] Upstream bugs are tracked on the github repo: https://github.com/linux- nvme/nvme-cli nvme-cli has been a part of Debian since stretch: https://packages.debian.org/stretch/nvme-cli. [UI standards] Autogenerated man pages for nvme commands and all subcommands (nvme-*) Man pages are fleshed out with all options described. [Dependencies] libc6 (>= 2.14) [amd64] GNU C Library: Shared libraries also a virtual package provided by libc6-udeb libc6 (>= 2.17) [arm64, ppc64el] libc6 (>= 2.8) [armhf, s390x] [Standards compliance] nvmeexpress.org, the group maintaining the package, is a compliance organization. They include many major technology groups as members. [Maintenance] Foundations will subscribe to the package ** Affects: nvme-cli (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/1889688 Title: [MIR] nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1889688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
I've actually done some checks on latest versions, and it looks like we can. I'll make a public bug to match the internal ticket I made to remove the connection. We've got a release tomorrow (20201022), so the change will go into the next devel release first, then get SRU'd back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
I've opened https://bugs.launchpad.net/cloud-images/+bug/1900852 related to removing uart1 connections in the base Vagrantfile. We can move discussion there related to the issue found for derivative images via Packer, and generally removing it. I, too, had been under the impression that due to the console=ttyS0 line in the kernel setup that we wouldn't be able to just not have the connection. but I now understand that it was our initiating of the connection and then not sending it anywhere that was causing the hangups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900852] [NEW] Remove uart1 connection from Vagrant boxes
Public bug reported: In discussions on lp: 1874453, a user (haggai-eran) ran into an issue with File::NULL being turned into an absolute path on a derivative image rather than staying the Ruby handling of File::NULL. In comment 54 during verification (https://bugs.launchpad.net/cloud- images/+bug/1874453/comments/54), nginer tried disabling uart1 connection entirely. He noted that previously this did not work on releases, however, in his current setup it did work. This led to me (jchittum) investigating removing configuring uart1 in CPC's base Vagrantfile (https://git.launchpad.net/livecd-rootfs/tree /live-build/ubuntu-cpc/hooks.d/base/vagrant.binary#n149). An initial test using the ubuntu/master branch of livecd-rootfs successfully booted. I also tested a user's ability to enable and add a serial debugging file and it worked. I propose the removal of the entire `config.vm.provider "virtualbox" do |vb|` stanza from the base Vagrantfile in Groovy and newer images, with further testing needed for possible SRU. ** Affects: cloud-images Importance: Undecided Assignee: John Chittum (jchittum) Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: John Chittum (jchittum) Status: New ** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900852 Title: Remove uart1 connection from Vagrant boxes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1900852/+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
Also confirmed that this affects Xenial images. MP is up, will make revisions shortly based on feedback. Due to the release Thursday, this won't be included in the Groovy Gorilla day 1. We'll have this in shortly after release, and work work the SRU process from the H release to Groovy, Focal, Bionic, and Xenial. -- 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 1900852] Re: Remove uart1 connection from Vagrant boxes
disabling `uart1` leads to `cloud-init` failures when writing keys:
```
2020-10-26 18:37:30,888 - util.py[WARNING]: Running module keys-to-console
() failed
2020-10-26 18:37:30,889 - util.py[DEBUG]: Running module keys-to-console
() failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 402, in
multi_log
wfh.flush()
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 848, in
_run_modules
ran, _r = cc.run(run_name, mod.handle, func_args,
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 185, in run
results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_keys_to_console.py",
line 69, in handle
util.multi_log("%s\n" % (stdout.strip()),
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 402, in
multi_log
wfh.flush()
OSError: [Errno 5] Input/output error
```
We've had discussions regarding default console connections
(specifically console=ttyS0) at various points. It appears cloud-init
will have this specific issue when no console is connection is available
at boot, at least for NoCloud
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900852
Title:
Remove uart1 connection from Vagrant boxes
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1900852/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
I can reproduce locally doing the following (fails on focal and groovy). I did this using the cloud-images.ubuntu.com VMDK, Virtualbox, and a simple cloud-init with ssh key and username/pw w/ ssh pw auth on. I got the following error: ``` 2020-10-28 13:32:33,680 - util.py[WARNING]: Running module ssh-authkey-fingerprints () failed 2020-10-28 13:32:33,680 - util.py[DEBUG]: Running module ssh-authkey-fingerprints () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 402, in multi_log wfh.flush() OSError: [Errno 5] Input/output error ``` TESTING: Requirements: Virtualbox cloud-localds command (to make your local ISO of cloud-init data) 1. download the latest VMDK (groovy): http://cloud-images.ubuntu.com/groovy/current/ 2. make a simple cloud-init w/ ssh pub key and pw login (to ensure you can get in) #cloud-config chpasswd: list: | ubuntu:ubuntu expire: False ssh_pwauth: True ssh_authorized_keys: 3. create the iso using cloud-localds ` cloud-localds my-seed.iso my-cloud-config.yaml ` 4. Open Virtualbox 5. Create New 6. Under Hard Disk, choose "Use Existing" and choose the VMDK and create 7. select image on Left, right click and choose Settings, or hit ctrl+s 8. go to Storage 9. Click on the +CD(Add Optical Drive) beside Controller: IDE 10. select your cloud-init iso (my-seed.iso) 11. click on drive, and set Attributes: Optical Drive to IDE Primary Master and hit OK 12. Boot machine Vbox will show you the console as it goes along. once booted 1. login with provided pw 2. `cloud-init status` will show failed 3. check cloud-init log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
This can also be configured to pass by having virtualbox provide a serial console connect: 1. select image on Left, right click and choose Settings, or hit ctrl+s 2. Choose Serial Ports 3. Enable Port 1 as follows: a. Enable b. COM1 c. IRQ: 4 d. I/O Port: 0x3F8 e. Port Mode: Raw File f. Path/Address: After connecting this, I observed that cloud-init finished all parts successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900852] Re: Remove uart1 connection from Vagrant boxes
This appears related to : https://bugs.launchpad.net/ubuntu/+source /cloud-init/+bug/1473527 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900852 Title: Remove uart1 connection from Vagrant boxes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1900852/+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
initial fix has been merged into Hirsute, and is currently in proposed. I did the following test using the deb src of release 2.697 from proposed (now superseded by 2.698) 1. downloaded dev source 2. unpacked 3. used ubuntu-oldfashioned/scripts/ubuntu-bartender to run a hirsute build ``` ./ubuntu-bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-rootfs/2.697/livecd-rootfs/ --build-provider multipass -- --series hirsute --project ubuntu-cpc --image-target vmdk ``` 4. Verified via the log the new descriptor was written. The build log now prints the descriptor files. copied below 5. Verified ova and vmdk booted using Virtualbox. Once the package moves from proposed to updates, we'll be able to produce a test hirsute image to verify the change, then work on SRUing the changes to all suites. build log below: + echo 'Cat'\''ing original descriptor to console for debugging.' Cat'ing original descriptor to console for debugging. + cat /tmp/tmp.LMSTXgWc8d # Disk Descriptor File # Created by VMDKstream version=1 # Believe this is random CID=7e5b80a7 # Indicates no parent parentCID= createType="streamOptimized" # Extent description RDONLY 20971520 SPARSE "call-me-stream.vmdk" # The Disk Data Base #DDB ddb.adapterType = "lsilogic" # 20971520 / 63 / 255 rounded up ddb.geometry.cylinders = "1306" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" # Believe this is random ddb.longContentID = "8f15b3d0009d9a3f456ff7b28d324d2a" ddb.virtualHWVersion = "7" + echo '' + echo -n 'ddb.toolsVersion = "2147483647"' + echo 'Printing diff of original and new descriptors.' Printing diff of original and new descriptors. + cat + diff --text /tmp/tmp.LMSTXgWc8d /tmp/tmp.K3j1jxkbgk 23c23,24 < ddb.virtualHWVersion = "7"^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ \ No newline at end of file --- > ddb.virtualHWVersion = "7" > ddb.toolsVersion = "2147483647" \ No newline at end of file -- 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 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
The latest hirsute cloud image ova and vmdk include this change. These can be downloaded from: http://cloud-images.ubuntu.com/hirsute/20201103/ My initial checks show correct headers and images boot fine using Virtualbox. I'll await confirmation from vmware-gos-Yuhua before marking complete and beginning the SRU process. -- 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 1895104] Re: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi
** 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/1895104 Title: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898871] Re: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5)
** 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/1898871 Title: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1898871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895104] Re: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi
Thank you for opening this ticket. I've added it to the cloud-images project for prioritization. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895104 Title: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898871] Re: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5)
Thank you for opening this ticket. I've added it to the cloud-images project for prioritization. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898871 Title: change the future OVA(s) to have default VM hardware version 13(ESXi 6.5) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1898871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872485] [NEW] virtualbox-guest-utils fails to install on 20.04
Public bug reported: Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install virtualbox-guest-utils` below. Steps to reproduce: 1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 test-container) 2. lxc exec test-container bash 3. apt update 4. apt full-upgrade 5. apt-get install virtualbox-guest-utils Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed init : PreDepends: systemd-sysv but it is not going to be installed Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 59 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59 Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 59 as a solution to systemd:amd64 59 Or group remove for systemd:amd64 Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23 Removing libpam-systemd:amd64 rather than change systemd:amd64 Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14 Removing libnss-systemd:amd64 rather than change systemd:amd64 Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib > Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 232-8~) Considering systemd:amd64 59 as a solution to plymouth:amd64 12 Removing plymouth:amd64 rather than change systemd:amd64 Investigating (3) plymouth-theme-ubuntu-text:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib > Broken plymouth-theme-ubuntu-text:amd64 Depends on plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mR > (= 0.9.4git20200323-0ubuntu6) Considering plymouth:amd64 59 as a solution to plymouth-theme-ubuntu-text:amd64 11 Removing plymouth-theme-ubuntu-text:amd64 rather than change plymouth:amd64 Investigating (3) netplan.io:amd64 < 0.98-0ubuntu4 @ii mK Ib > Brok
[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
Focal and Eoan boxes with the above kernels have been pushed to Vagrant and verified. Please run a `vagrant box update` to get the latest versions. ** Changed in: cloud-images Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Vagrant boxes with updated kernels have been pushed. My current tests are showing boot times in the 30s range. Could folks commenting on slow boot speeds in Focal and Eoan please run a `vagrant box update` on their current setups? https://app.vagrantup.com/ubuntu/boxes/eoan64/versions/20200522.0.0 and https://app.vagrantup.com/ubuntu/boxes/focal64/versions/20200518.0.0 Have the latest kernels. Any produced after those dates should also load faster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
May 22nd was made available when I commented. Not sure why your update didn't find it. Maybe there's lag with specific mirrors. Official listings show them available: https://app.vagrantup.com/ubuntu/boxes/focal64 https://app.vagrantup.com/ubuntu/boxes/eoan64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
apologies -- the 0518 Focal image has the fix as well. That may not have been clear since the comments came on the 19th, and I updated on the 22nd. The eoan 22nd made it up on the 22nd, but there was lag with the Focal 0522 serial syncing on our end. It's up there now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
is this post updating the boxes? could you please post which boxes are still kernel panicking, as that should have been fixed with https://bugs.launchpad.net/cloud-images/+bug/1873506 I'm having a bear of a time trying to reproduce the slow boots. I'm wondering if it's host specific to MacOS and Virtualbox on MacOS. I haven't been able to reproduce with Ubuntu as my host machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
I've set the kernel component to confirmed to move this ticket forward. ** 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
was passed a related issue: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Was able to recreate the slow boot. Put together a clean environment, made a simple focal Vagrantfile only pulling the box, saw the same things. Confirmed on a Focal host. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872813] Re: cloud-init fails to detect iSCSI root on focal Oracle instances
Confirmed fix. The main symptom was inability to SSH into a running instance due to cloud-init not completing. Main test was to instantiate an instance and SSH in. Test procedures: 1. checked daily CPC Oracle build to ensure build passed 2. Checked image manifest to ensure open-iscsi 2.0.874-7.1ubuntu6 was installed 3. Uploaded image to Oracle US-East Bucket 4. Imported image as both a PV and Native boot images (Native boot images use iscsi) 5. Created instances of both PV and Native images 6. checked PV and Native images booted (Success) 7. checked ability to SSH into both images (Success) 8. Ran basic smoke checks to system errors, internet connectivity, etc (systemctl, apt, and snap commands)(Success) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872813 Title: cloud-init fails to detect iSCSI root on focal Oracle instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1872813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Attached are some prints and logs. lshw shows that it's using a scsi storage control with the mptspi driver. serial console logs show that initramfsless boots using a a generic scsi driver which appears to fail to load the root device. initramfs pulls in the mptspi driver properly, and things boot. system details host OS: Focal vagrant: 2.2.7 virtualbox: 6.1.6_Ubuntu r137129 ** Attachment added: "print-outs.txt" https://bugs.launchpad.net/cloud-images/+bug/1874453/+attachment/5366964/+files/print-outs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777827] Re: remove log from Vagrantfile
*** This bug is a duplicate of bug 1874453 *** https://bugs.launchpad.net/bugs/1874453 ** This bug is no longer a duplicate of bug 1829625 Vagrant box startup timeout due to no serial port ** This bug has been marked a duplicate of bug 1874453 ubuntu/focal64 very slow to boot and reboots once -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777827 Title: remove log from Vagrantfile To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1777827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829625] Re: Vagrant box startup timeout due to no serial port
*** This bug is a duplicate of bug 1874453 *** https://bugs.launchpad.net/bugs/1874453 ** This bug has been marked a duplicate of bug 1874453 ubuntu/focal64 very slow to boot and reboots once -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829625 Title: Vagrant box startup timeout due to no serial port To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1829625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546108] Re: Latest Vagrant box for Ubuntu Xenial is failing to boot
*** This bug is a duplicate of bug 1874453 *** https://bugs.launchpad.net/bugs/1874453 ** This bug is no longer a duplicate of bug 1829625 Vagrant box startup timeout due to no serial port ** This bug has been marked a duplicate of bug 1874453 ubuntu/focal64 very slow to boot and reboots once -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546108 Title: Latest Vagrant box for Ubuntu Xenial is failing to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1546108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Package changed: linux (Ubuntu) => livecd-rootfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
MP, taking giner's work and integrating all the needs for livecd-rootfs SRU process is going: https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd- rootfs/+merge/389918 Should be moving in Groovy soon, and then SRU'd back to Focal. ** Also affects: cloud-images/focal Importance: Undecided Status: New ** Also affects: cloud-images/groovy Importance: Undecided Assignee: John Chittum (jchittum) Status: Confirmed ** Changed in: cloud-images/focal Status: New => Confirmed ** Changed in: cloud-images/focal Assignee: (unassigned) => John Chittum (jchittum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
fix in livecd-rootfs/master has been merged, built, and tested. Groovy boxes with any serial with a date 20200917 or newer should have the fix (we're working on getting this published now). I am also beginning the SRU procedure to backport the change into Focal. Thank you giner for the providing the code to pass a serial to a null file handler in our base Vagrantfile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Also, for anyone that has run a Focal or Groovy box, and had it hang completely with it not showing up in Virtualbox GUI for stopping, the following can get the image unlocked for future work (without a reboot) vboxmanage startvm --type emergencystop vboxmanage unregistervm If you're unsure of a UUID or name, try running a Vagrant command (such as vagrant halt). If it fails, Vagrant will print the command used which includes the UUID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Updated Groovy Vagrant box has been pushed to Atlas, and tested. Steps
below, Vagrantfile at bottom:
1. create a minimal Vagrantfile for testing
2. `vagrant box update`
3. check box is at a serial 20200917 or newer (if done now, 20200917 should
download)
4. `vagrant up`
5. observe it now boots faster (on my system, < 40s)
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/groovy64"
end
Will begin SRU cycle for Focal with successful test of the public
Vagrant box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** Changed in: cloud-images/groovy Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] [NEW] Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
Public bug reported: ## Info chromium 128.0.6613.119 2943 latest/stablecanonical✓ snapd 2.6321759 latest/stablecanonical✓ Ubuntu 24.04 kernel - 6.8.0-41-generic ## hardware system76 gazelle 14" 2019 model ### GPU NVIDIA GeForce GTX 1660 Ti Driver Version: 535.183.01 ### CPU Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz ## webcams BisonCam, NBPro Microsoft LifeCam Studion (TM) ## other connected hardware C-Media Electronics Inc. AKG Ara USB Microphone ## Background First noticed on 20240916 journalctl filling up with ERROR:gl_utils.cc(415)] [.WebGL-0x21680d278700] GL_INVALID_OPERATION: Invalid query Id. this has happened when launching with "Launch with discreet graphics", launching via a simple commandline, or launching "normally" the command from "launch with discreet graphics" /snap/chromium/2943/usr/lib/chromium-browser/chrome --type=gpu-process --crashpad-handler-pid=655636 --enable-crash-reporter=,snap --change- stack-guard-on-fork=enable --gpu- preferences=UAAgAAAEAABgAAEAAQAAABAAEAAIAAgA --shared-files --field-trial- handle=3,i,9141409946131128162,11100357177403877201,262144 --disable- features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed- version ## Info logging snippet INFO:CONSOLE(195)] "WebGL: INVALID_OPERATION: endQuery: target query is not active", source: https://www.gstatic.com/video_effects/effects/673214282/videopipe_bundle.js (195) [666284:666284:0917/082204.295519:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082204.296983:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082210.871019:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [666284:666284:0917/082210.879465:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [666371:103:0917/082217.166630:WARNING:rtcp_receiver.cc(326)] OnPeriodicRttUpdate: Timeout: No RTCP RR received. [666284:666284:0917/082218.676804:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! I don't know if the first line, middle lines, and end lines are related, other than references to Web GL (other than the rtcp_receiver, which i just left because it was there...) ## Reproducer able to reproduce with good logging to commandline with: /snap/chromium/2943/usr/lib/chromium-browser/chrome --enable-crash- reporter=,snap --change-stack-guard-on-fork=enable --shared-files --disable-features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed-version --enable-logging=stderr ## Errata Quest: to make chromium work :) airspeed velocity: African or European? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: ## Info chromium 128.0.6613.119 2943 latest/stablecanonical✓ snapd 2.6321759 latest/stablecanonical✓ Ubuntu 24.04 kernel - 6.8.0-41-generic ## hardware system76 gazelle 14" 2019 model ### GPU NVIDIA GeForce GTX 1660 Ti Driver Version: 535.183.01 ### CPU Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz ## webcams - BisonCam, NBPro + BisonCam, NBPro Microsoft LifeCam Studion (TM) ## other connected hardware C-Media Electronics Inc. AKG Ara USB Microphone ## Background First noticed on 20240916 journalctl filling up with ERROR:gl_utils.cc(415)] [.WebGL-0x21680d278700] GL_INVALID_OPERATION: Invalid query Id. this has happened when launching with "Launch with discreet graphics", launching via a simple commandline, or launching "normally" the command from "launch with discreet graphics" /snap/chromium/2943/usr/lib/chromium-browser/chrome --type=gpu-process --crashpad-handler-pid=655636 --enable-crash-reporter=,snap --change- stack-guard-on-fork=enable --gpu- preferences=UAAgAAAEAABgAAEAAQAAABAAEAAIAAgA --shared-files --field-trial- handle=3,i,9141409946131128162,11100357177403877201,262144 --disable- features=EyeDropper,TFLiteLanguageDetectionEnabled --variations-seed- version ## Info logging snippet INFO:CONSOLE(195)] "WebGL: INVALID_OPERATION: endQuery: target query is not active", source: https://www.gstatic.com/video_effects/effects/673214282/videopipe_bundle.js (195) [666284:666284:0917/082204.295519:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id. [666284:666284:0917/082204.296983:ERROR:gl_utils.cc(415)] [.WebGL-0x33f805216300] GL_INVALID_OPERATION: Invalid query Id.
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
nteodesio: just had the exact same crash, launching Chromium by clicking the icon on the dock (without discreet graphics). I'm in meetings 5-6 hours a day, so I can try just about any fashion you'd like me to launch. i'm also confused about that commandline being unsupported -- that's what clicking on the dock item shows in ps, with the graphics pieces removed, and trying to make it a base launch command not one of the tools (sorry if it's a bit off, as reading browser process trees confuses me sometimes). > airspeed velocity: African or European? it's in the notes about "raising a bug" with helpful commands and all that. guess a maintainer really like Monty Python :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974100] Re: qemu ide/sata disks do not work well with discard/trim
I haven't come across this before. Our builds for the cloud images from
cloud-images.ubuntu.com have the following cleanup code run that should
be preventing this sort of thing:
https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n231
hard to read exact ramifications, but the gist is we create a
filesystem, mount it, create the image, then at the end during clean up
we run
# rootfs_dev_mapper is set in https://git.launchpad.net/livecd-
rootfs/tree/live-build/functions#n62 when mounting an image
e2fsck -y -E discard ${rootfs_dev_mapper}
zerofree ${rootfs_dev_mapper}
before running kpartx to remove the mount
this _should_ be discarding the empty blocks. That matches the
expectation b1 and b2.
But I haven't seen
> The cloudimage extended and used as root grows more lost blocks (seems
like 5 MB above)
so that bears investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974100
Title:
qemu ide/sata disks do not work well with discard/trim
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1974100/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout
Kinetic Vagrant image is available at : https://app.vagrantup.com/ubuntu/boxes/kinetic64 for a fresh install quickly vagrant init ubuntu/kinetic64 vagrant up This image should work on all versions of Vagrant available in Ubuntu archives. I'll spin some VMs and do more testing, but community help is appreciated. Once a few versions of Vagrant and hosts are verified, we'll be able to do an SRU to Jammy Testing ** Host: Ubuntu 22.04 Vagrant: 2.2.19 Virtualbox: 6.1 VBox Guest Additions: 6.0.0 r127566 successful boot and ssh. no errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969664 Title: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072929] Re: Ubuntu cloud image partition numbering
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072929 Title: Ubuntu cloud image partition numbering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072883] Re: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu
`gosu` is a universe package in Ubuntu, and from what i can see was inherited from `side` at version 1.17.1 https://packages.debian.org/sid/gosu I see no open bugs against `gosu` : https://bugs.debian.org/cgi- bin/pkgreport.cgi?src=gosu , and it needs to be confirmed that it's built against golang 1.17 in `debian`. Not my expertise normally the correct move would be to go upstream first. Since i control things on the Ubuntu side for cloud-images, i'll move the ticket around there. I'll also make it public as it's not a new security vulnerability (private security bugs are for new disclosures, not for tracking already announced vulnerabilities). Public Ubuntu tracking of the golang vulnerability: https://ubuntu.com/security/CVE-2024-24790 Note, since this is reported against Noble, i _believe_ this is an incorrect match. I'm working on double checking, but in noble, the golangs have been patched (both 1.21 and 1.22) It's likely a bad version string match. but i've listed this against `gosu` for someone to double check my assertions. `gosu` in noble is building against `golang- go=1.22` http://archive.ubuntu.com/ubuntu/pool/universe/g/gosu/gosu_1.17-1.dsc ** Also affects: gosu (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Invalid ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-24790 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072883 Title: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072929] Re: Ubuntu cloud image partition numbering
** Changed in: cloud-images Status: New => Confirmed ** Changed in: cloud-images/oracular Status: New => Confirmed ** Changed in: cloud-images Importance: Undecided => High ** Changed in: cloud-images/oracular Importance: Undecided => High ** Changed in: cloud-images Assignee: (unassigned) => Simon Poirier (simpoir) ** Changed in: cloud-images/oracular Assignee: (unassigned) => Simon Poirier (simpoir) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072929 Title: Ubuntu cloud image partition numbering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056065] Re: cloud images slow to boot under kvm
** Changed in: cloud-images Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056065 Title: cloud images slow to boot under kvm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
I've set this to incomplete for now. @air-awan, if you have time to give an update related to vmware environments, let me know. i double checked, and the addition of the serial port was requested by the vmware team, so if it's breaking things now due to hypervisor level issues, I'll have to sync with vmware to figure out the appropriate fix. ** Changed in: cloud-images Status: New => Incomplete ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077105] Re: cloud-images do not produce sboms
** Changed in: livecd-rootfs (Ubuntu Noble) Status: New => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress ** Changed in: cloud-images Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077105 Title: cloud-images do not produce sboms To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2077105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080223] Re: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline
adding cloud-images. if multiple artifacts are generated, the CPC pipeline will need to ensure that we download and transport all the livefs-build artifacts. ** Also affects: cloud-images Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080223 Title: Ensure WSL instances do not rely on the Windows launcher by using the new build pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2080223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
@DisasteR -- could you be more specific? Which images are you seeing this in? which cloud, which download from `cloud-images.ubuntu.com`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
Tested working on the image from http://cloud- images.ubuntu.com/releases/jammy/release-20240319/ $ ssh -o "UserKnownHostsFile=/dev/null -o CheckHostIP=no StrictHostKeyChecking no" jchittum@0.0.0.0 -p The authenticity of host '[0.0.0.0]: ([0.0.0.0]:)' can't be established. ED25519 key fingerprint is This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '[0.0.0.0]:' (ED25519) to the list of known hosts. jchittum@0.0.0.0's password: Welcome to Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-101-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro System information as of Mon Apr 1 11:55:56 UTC 2024 $ ls /etc/ssh/sshd_config.d/ 50-cloud-init.conf 60-cloudimg-settings.conf $ sudo cat /etc/ssh/sshd_config.d/50-cloud-init.conf PasswordAuthentication yes $ sudo cat /etc/ssh/sshd_config.d/60-cloudimg-settings.conf PasswordAuthentication no cloud-init and passwords is a bit confusing. here is a working example of a cloud-init: #cloud-config ssh_pwauth: true users: - name: jchittum groups: [adm, lxd, sudo] passwd: sudo: ALL=(ALL) NOPASSWD:ALL shell: /bin/bash lock_passwd: false - name: timmy groups: [adm, lxd, sudo, cdrom, dip] ssh_import_id: lp:jchittum sudo: ALL=(ALL) NOPASSWD:ALL passwd: shell: /bin/bash lock_passwd: false NOTES: passwd was set by running : mkpasswd --method=SHA-512 --rounds=50 lock_passwd: false is _required_ to make this work. otherwise providing a password won't do anything, and you'll never be able to log in. I'm wondering if it's from a different version of cloud-init instead? 20231211: cloud-init 23.3.3-0ubuntu0~22.04.1 20240319: cloud-init 23.4.4-0ubuntu0~22.04.1 i don't see anything related in the changelog[https://github.com/canonical/cloud-init/blob/main/ChangeLog] next steps: try a coud-init config like i have above. If it fails, please provide your cloud-init and outputs (especially helpful with some cloud-init logs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046154] Re: [MIR] libcryptx-perl (libmail-dkim-perl dependency)
Alternative idea, what about instead of writing a wrapper: 1. look at https://packages.ubuntu.com/noble/libnet-ssleay-perl a. libnet-ssleay-perl is in main 2. add eddsa-25519 to the list of constants upstream a. if i'm reading correctly, there's a mapping in a helper_scripts/constants.txt that contains a list of all algorithms, that is then used to autgen C and perl bindings. if libssl or libgrypt on the system already has eddsa-25519, it should "just work" 3. switch to using libnet-ssleay-perl for the backend of these calls a. bonus, you could see if you could switch _everything_. it'd make sense to me... I don't know if this ends up being a heavier or lighter lift. and it takes updating libnet-ssleay-perl upstream, but reading the list of constants, it could benefit from someone going through and fleshing out current libssl and libcrypt support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046154 Title: [MIR] libcryptx-perl (libmail-dkim-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/2046154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
@DisatesR : if you're not seeing a 50-cloud-init.conf file, it indicates to me that cloud-init is failing to parse the cloud_init configuration properly, and thus not adding the required configuration to /etc/ssh/sshd_config.d/ could you provide your entire cloud config? you can also use cloud-init to verify your user-data https://cloudinit.readthedocs.io/en/latest/howto/debug_user_data.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049860 Title: cloud-init cloud-config for ssh broken in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072883] Re: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu
you can check any progress in Ubuntu by checking the issue tracker https://ubuntu.com/security/CVE-2024-24790 https://ubuntu.com/security/CVE-2024-24791 it looks like 2024-24690 is fixed, so may be a false-positive. 24791 is still in needs-triage on the page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072883 Title: Docker scout reports critical and high vulnerabilities for Ubuntu docker images with installed gosu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2072883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046486] Re: units with credentials fail in LXD containers
blech, sorry, misclicks trying to get things added properly marking as affects cloud-images as producers of the lxd images. ** Also affects: systemd Importance: Undecided Status: New ** No longer affects: systemd ** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046486 Title: units with credentials fail in LXD containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2046486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895104] Re: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi
** Changed in: cloud-images Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895104 Title: It hangs during booting after deploy cloud image(.ova) and upgrade hardware vesion in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1895104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
1. what versions of VMware ESXi is this applicable? 2. is this reproducible in other environments, such as Virtualbox? 3. is this error true of all ubuntu images for those versions then? This was added in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1895104 at the request of vmware 4. I have a worry that removing serial port may cause issues in other deployment areas, such as Virtualbox, and possibly other versions of ESXi. Could a full test plan be provided to ensure compatibility? This is also tightly coupled to this ticket, in which i requested a meeting and documentation, and it hasn't occurred yet: https://bugs.launchpad.net/ubuntu/+bug/1898871 NOTE: this is after Release Freeze so there is a change this does _not_ get fixed prior to the 24.04 release next week. If we cannot work out a fix, we will release note this issue and work on releasing as soon as possible ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062552] Re: Ubuntu 24.04 LTS Cloud Image ova error during deployment
Thank you for checking Aditya. I'll leave this open till you get some guidance from VMware regarding any changes in Cloud Director that may be affecting serial console connections. I've also added this to our 24.04 release notes (to be published soon for the clouds). Thank you a bunch for trying out 24.04 so that we can help others if they see this as well! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062552 Title: Ubuntu 24.04 LTS Cloud Image ova error during deployment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2062552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023758] Re: Updating guest additions on ubuntu/focal64 hits timeout
Virtualbox in focal and jammy (20.04 and 22.04) has migrated to 6.1.50-dfsg-1~ubuntu1.20.04.1 reminder that virtualbox is a multiverse package, meaning it relies on community support at this time. Since we ar eon 6.1.x in 22.04 and 20.04, users can expect bugfixes and security fixes from the community through the lifetime of standard support. with extended support via Ubuntu Pro, universe (and multiverse) may also be covered in security updates. Based on previous discussion, it looks like using the Ubuntu supplied GuestAdditions works. this is shipped as part of the image, and works in a matchup with Ubuntu hosts. Vagrant images have community level support, where we do our best to help debug issues. Since it looks like reverting to the Ubuntu version of guest additions works, I'll be closing this ticket. We are also working on having more public docs for the community available here: https://documentation.ubuntu.com/public- images/en/latest/public-images-how-to/ you can see examples of building and running vagrant, as well as more information about what we can best support. We welcome community contributions to the documentation ** Changed in: virtualbox-guest-additions (Ubuntu) Status: New => Invalid ** Changed in: virtualbox (Ubuntu) Status: New => Invalid ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023758 Title: Updating guest additions on ubuntu/focal64 hits timeout To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2023758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971532] [NEW] [snap] Firefox Save File Unable To Paste Into Filename
Public bug reported: related to a few other bug reports: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168 Save File prompt disallows paste to filename. Attached is a screenshot of what pops up. Tested in various directories. Info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy uname -a Linux j5awry-sys76 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux snap version snap2.55.3+22.04ubuntu1 snapd 2.55.3+22.04ubuntu1 series 16 ubuntu 22.04 kernel 5.15.0-27-generic snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: 21 days ago, at 14:48 CDT ... installed: 99.0.1-1 (1232) 163MB - (tracking latest/stable) Reproduction: Download a file to get file prompt Cut the name attempt to paste the name back in Reproducible when targeting ~/Downloads, ~/Documents, and /tmp ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "firefox_paste_disallow.png" https://bugs.launchpad.net/bugs/1971532/+attachment/5586514/+files/firefox_paste_disallow.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971532 Title: [snap] Firefox Save File Unable To Paste Into Filename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971788] Re: Failure to enable SSL out of the box when in fips mode
Data points provided: using an 18.04 Bionic FIPS cloud image, doing ``` apt-get update && apt-get install mysql-server mysql-client ``` successfully installs the server and client, and enables TLS properly for the FIPS environment. There may be a difference in packaging scripts between mysql-5.7 and mysql-8.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971788 Title: Failure to enable SSL out of the box when in fips mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1971788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965180] [NEW] apt-add-repository requires --login for private repos, breaking automated workflows
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 Packages
[3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main Translation-en
[1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${FINGERPRINT}";
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu jammy main"
Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, in
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
429, in _request
raise error
lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
Response headers:
---
-content-encoding: gzip
content-length: 91
content-type: text/plain;charset=utf-8
date: Wed, 16 Mar 2022 19:54:16 GMT
server: gunicorn/19.8.1
status: 404
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
---
Response body:
---
b"Object: ,
name: '$REPO'"
---
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, in
description
return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, in
lpppa
raise ShortcutException(msg)
softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa
'$REPO/proposed' not found (use --login if private)
Impish similarly breaks. Digging through changelogs, I see various
entries in Impish forward, starting with version 0.99.0 where a refactor
was done.
using `--login` is not possible in an automated setup (such as a
builder) as it starts an OAuth dance, which requires human interaction.
this will break existing automation utilizing apt-add-repository for
users when migrating to Jammy
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965180 Title: apt-add-repository requires --login for private repos, breaking automated workflows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
