** 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 membe
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 Kernel
Packages, which is subscribed to linux-az
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 fai
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 Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launch
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 Kernel
Packages, w
We are no longer seeing this issue with the latest images.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V] KVP daemon fails to start on first boot of disco VM
St
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 Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1841827
Title:
Install of linux-modules-nv
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 Kernel
Packages, which
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 Kernel
Packages, whic
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 Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with ude
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 Kernel
Packages, which is
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 b
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 t
** 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&context=25&ignorews=0&dt=0,
and later I thought it was related to
https://bugs.launchpad.net/bugs/1762748. However, I added the bionic
archives to my Xenial
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 reboot
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
18 matches
Mail list logo
