--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054827
Title:
[regression] GUI crashed after installed proposed package after mesa
updates
To manage notifications about this bug go to:
Public bug reported:
During an impish build of ubuntu-cpc images with magic-proxy enabled,
the installation of certain packages tried to reach an internet endpoint
(specifically http://169.254.169.254/latest/meta-data/instance-id -
which appears to be used for EC2 metadata)
The magic-proxy log
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-done-hirsute
** Tags added: verification-needed-hirsute
** Tags removed: verification-done-bionic verification-done-focal
** Tags added: verification-needed-bionic verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
** Tags removed: verification-needed-bionic
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic
do you mind providing your grub configuration? (I know you said it was
system default in the other bug), but I'd like to compare it against our
fresh VM boot just to see if anything was awry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have been looking into why this has been happening on Azure Ubuntu
VMs, but I have not been able to reproduce:
I'm running:
az vm create --name bug-test --resource-group canonical-patviafore
--location southcentralus --image Canonical:0001-com-ubuntu-server-
focal:20_04-lts:20.04.202107200
@abaealter: I'm trying to reproduce the issue on Azure as that will give
us an environment to investigate this bug a bit better, and I was not
able to. Do you mind providing a little more information about your
Azure environment?
Do you have the URN that you are running with (if you don't know
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when deploying Impish 21.10
To manage notifications about this bug go to:
Public bug reported:
During cloud builds of riscv64 (impish), we do a u-boot-update inside
our chroot.
With version 4.0.3ubuntu1, the command fails with the following error
message:
/usr/sbin/u-boot-update: line 92: syntax error near unexpected token
`<<<'
We did not see this error with
I have done testing on minimal images built from 2.664.19 livecd-rootfs
and run them through qemu to verify they still boot. I have also tested
cloud-specific images to make sure they do not double boot as part of
this change.
** Tags removed: verification-needed verification-needed-focal
** Tags
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Pat Viafore (patviafore)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920043
Title:
Latest Focal Minimal disk images f
Commit 4c504f678178104eceaf5b3aae40bcff20863235 needs to be backported
to Focal to fix this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920043
Title:
Latest Focal Minimal disk images from
Public bug reported:
[Impact]
* Minimal images built from livecd-rootfs after March 12th do not boot.
There are no broken images on cloud-images.ubuntu.com, but no further
images will be published until this is fixed. Cloud-specific minimal
images are unaffected, as they do the proper steps in
I have tested the changes in livecd-rootfs 2.664.18. Generic cloud
images (qcow2, kvm, etc) cloud images now boot with an initramfs and
don't have a double boot (tested with QEMU). I've also tested various
cloud images (AWS, Google, Azure, Oracle) that have custom cloud kernels
(which make use of
** Description changed:
- A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
- 20.04 by “do-release-upgrade –d”.
+ [Impact]
+ Generic cloud images will boot without initramfs, fail, and then fall back,
resulting in a double boot performance hit
+
+ [Test Case]
+ Load up cloud
As an update to this bug:
The work to SRU has stalled, as we have found a regression
(https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1902260).
Once a fix is SRU'd to Groovy, I'll pick up the fix and SRU it back to
Focal.
--
You received this bug notification because you are a
Hi richmbx,
I am currently working this, and currently doing testing to make sure it
has integrated with Focal correctly. I expect it to begin the SRU
process in the next day or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've confirmed that this has been fixed in the latest Xenial 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/1580596
Title:
Xenial & bionic vagrant box disk size is too small
To manage
Version 2.408.65 of livecd-rootfs has fixed this issue.
Test case:
Built a box with the version of livecd-rootfs
vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name xenial-test
vagrant init xenial-test
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk
Version 2.525.48 of livecd-rootfs has fixed this issue.
Test case:
Built a box with the version of livecd-rootfs
vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name bionic-test
vagrant init bionic-test
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk
Public bug reported:
We have most reliably reproduced this on a Standard_B1s in Azure in the
North Europe region (>80% of the time). Tests in other regions/VM types
do not show this failure as often (<1%). We have reproduced this in
Xenial, Bionic, Focal, and Groovy. We saw an increase of test
Thank you @ianchanning for the recovery notes through the portal.
I'll also add in a few links that might help.
For users looking for general recovery steps :
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Recovery
For users looking how to mitigate this before
We are seeing some failures still in Eoan (not Focal) with tracebacks
involving growpart:
2020-05-29 10:14:29,218 - util.py[DEBUG]: Running module growpart () failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 851, in
_run_modules
** Description changed:
[Impact]
Users could not use vagrant boxes as a full computer (or anything requiring
more than 10G of memory). This was a regression from our behavior in 14.04
[Test Case]
vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64
as
** Description changed:
- The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with
- the trusty box.
+ [Impact]
+ Users could not use vagrant boxes as a full computer (or anything requiring
more than 10G of memory). This was a regression from our behavior in 14.04
+
+ [Test Case]
** Merge proposal unlinked:
https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/384634
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596
Title:
Xenial & bionic
** Also affects: cloud-images/bb-series
Importance: Undecided
Status: New
** Also affects: cloud-images/x-series
Importance: Undecided
Status: New
** No longer affects: cloud-images/bb-series
** No longer affects: cloud-images/x-series
--
You received this bug notification
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Pat Viafore (patviafore)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596
Title:
Xenial & bionic vagrant box di
This is now fixed, thank you
** 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/1876139
Title:
Groovy cloud-images failing during growpart
To
We're wary of fdisk being in a seed for cloud-image, because we want to
make sure we remain consistent with the rest of the distro and bringing
an old package forward with us (say if we as a distro move towards
gdisk).
I'm good with cloud-init depending on fdisk (or sometime in the future,
gdisk)
Yes, we see it on Eoan and blocking tests, so if you could SRU it there,
it'd be much appreciated. We have never seen it on Bionic to my
knowledge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, we were waiting on a bug regarding dictionary keys being modified
to resolve before we could verify this. We have not seen this in the
past couple of runs in our testing, so I think we're good to proceed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We are no longer seeing this issue with the latest images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V] KVP daemon fails to start on first boot of disco VM
To manage
Nouveau was blacklisted in our images, so I am no longer seeing this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841827
Title:
Install of linux-modules-nvidia requires a reboot before
Adding in a passing version of journalctl
** Attachment added: "passing_journalctl_output.txt"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5326024/+files/passing_journalctl_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm attaching the output of a failing build
** Attachment added: "failing_journalctl_output.txt"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5325941/+files/failing_journalctl_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have tested in Bionic, Xenial and Eoan.
I've done reboot testing, verified that waagent is running, and that
waagent booted with no errors. I have also performed our automated
Azure testing suite on each image.
It looks good from our end.
--
You received this bug notification because you
I can get that going, and will report back on this bug when I have more
information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
To manage
For those looking for a workaround in the meantime, I've found that
lxqt-config-brightness -i and lxqt-config-brightness -d on the command
line are still able to control the screen brightness in my setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have run our tests and am satisfied with the results. Our tests very
closely matches what mruffell posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial images won't reboot
I have re-ran my test cases and the package you provided fixes the
original issue that we saw.
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial images won't reboot if
I have tested this package in bionic-proposed, and all of my test cases
passed.
Tests cases:
Testing NVIDIA drivers install on non-GPU instance does nothing
Testing NVIDIA drivers install on GPU instance
Specifying different versions for NVIDIA drivers install
--
You received this bug
So after doing a little more digging:
A modprobe -r nouveau will fix this. After issuing this command, an
install does not require a reboot for nvidia-smi to find the driver.
We are planning on blacklisting the module in our cloud images to
address this.
--
You received this bug notification
Public bug reported:
When installing linux-modules-nvidia-418-generic using apt, I expect the
nvidia driver to be available immediately after the install completes.
However, I must reboot before nvidia-smi returns driver information.
AS a side note: sudo udevadm control --reload && sudo udevadm
** Description changed:
CPC team has recently converted Xenial images to use GPT instead of MBR.
However, after booting an instance that has a disk size of 2049 GB or
higher, we hang on the next subsequent boot (Logs indicate it hanging on
"Booting Hard Disk 0".
This works on Bionic,
At first I thought it was related to
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=1e19b01be31fc5264a84d246023ecf29e44949df=25=0=0,
and later I thought it was related to
https://bugs.launchpad.net/bugs/1762748. However, I added the bionic
archives to my Xenial instance and
Public bug reported:
Relevant system information here:
https://pastebin.canonical.com/p/q6XqWt6THQ/
I was expecting that when I installed linux-modules-nvidia-generic-418
that I would get an option to accept or reject a EULA. However, on
installation, no prompt is given to me, and after a
Public bug reported:
CPC team has recently converted Xenial images to use GPT instead of MBR.
However, after booting an instance that has a disk size of 2049 GB or
higher, we hang on the next subsequent boot (Logs indicate it hanging on
"Booting Hard Disk 0".
This works on Bionic, but what makes
Tests performed:
- Booted a VM and checked proper package version
- Checked to make sure waagent was running and that the /var/log/waagent.log
was error-free
- Rebooted the VM and confirmed that waagent was still running and log was
error-free
- Verified that cloud-init still worked
- Ran
60 matches
Mail list logo
