** Description changed:
- Google Instances deployed with the Ubuntu 12.10 Daily images are
+ Google Instances deployed with the Ubuntu 21.10 Daily images are
inaccessible via SSH.
gcloud compute instances create sf-impish-v20200720 --zone us-west1-a
--network "default"
Verification steps:
1. Enabled Confidential Compute
2. Change image to daily-ubuntu-2104-hirsute-v20210510 (last working image)
3. Launched image
4. Enabled proposed
5. Updated system https://paste.ubuntu.com/p/mNrZNkVYtB/
6. Rebooted sucessfully! https://paste.ubuntu.com/p/G9CmvhW9tx/
Marking
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/nwcjCSVTRD/
uEFI+Secure Boot:
# Steps to reproduce
1. $ multipass launch bionic --name b1
2. $ multipass exec b1 bash
3. $ sudo apt update
4. $ sudo apt install aide
5. At the MTA configuration select "No configuration"
6. $ sudo run-parts /etc/cron.daily
7. $ sudo run-parts /etc/cron.daily
8. $ sudo ls /run/aide
At this
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/K2DpvcbYNG/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/kqjn5YbYCb/
uEFI+Secure Boot:
# Xenial AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/ys4hgfTfRm/
c6g.metal: https://paste.ubuntu.com/p/2RFYbCmFxh/
Marking verification done
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
# Bionic Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/
c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/
After verifying that the "error" messages in #15 is ignorable, marking
this verification done.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug
Testing complete, if someone can explain the error messages in comment
#15 we can mark this verification-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930742
Title:
cloud images in xenial do
# GCE Verification
## Test Steps
Booted GCE amd64 systems with uEFI-only and uEFI+Secure Boot
Ran the following script: https://paste.ubuntu.com/p/BDwhF4KHZ2/
Ensure system successfully reboots
## Xenial Results
uEFI only: https://paste.ubuntu.com/p/vhxkYy5F43/
uEFI+Secure Boot:
# Bionic AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/
c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/
# Xenial AWS Verification
## Test Steps
Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots
## Results
Both systems successfully updated grub from proposed and rebooted
t4g.medium:
Public bug reported:
# Overview
Hirsute and Impish daily builds are currently not booting on Google
Confidential Compute. Confidential compute is Google's platform that
enables the use of Secure Encrypted Virtualization extension via AMD
EPYC CPUs. Booting an image with version 1.45 works, but
Launched c6g.metal, a1.metal, and t4g.medium instance with Xenial
(20210429) on upgrade of all three I got the following error:
grub-install: error: relocation 0x113 is not implemented yet.
Failed: grub-install --target=arm64-efi
WARNING: Bootloader is not properly installed, system may not be
Google has confirmed that the SRU has successfully passed their tests
and previously failing tests are now consistently passing. Marking fixed
verified.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
Test images were delivered to Google with images with the following
versions:
* bionic-livecd.ubuntu-cpc.gce.devel.manifest
google-compute-engine-oslogin20210429.00-0ubuntu1~18.04.0
* focal-livecd.ubuntu-cpc.gce.devel.manifest
google-compute-engine-oslogin
Marking verification-done for all releases.
Images were successfully generated with the following versions of
google-guest-agent from proposed:
bionic: 20210414.00-0ubuntu1~18.04.0
focal: 20210414.00-0ubuntu1~20.04.0
groovy: 20210414.00-0ubuntu1~20.10.0
hirsute: 20210414.00-0ubuntu1
These
Per the diff there are two merge issues
https://launchpadlibrarian.net/536068009/u-boot-
menu_4.0.2ubuntu5_4.0.3ubuntu1.diff.gz
fwiw this is blocking impish builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking confirmed
# Steps to reproduce
1. wget
http://cloud-images.ubuntu.com/daily/server/buildd/daily/xenial/current/xenial-server-cloudimg-amd64-disk.img
2. Modify /etc/boot/grub.cfg to add "console=ttyS0" to kernel command line
3. Boot using the following qemu CLI:
qemu-system-x86_64 \
# Upgrading Xenial to Bionic on GCE
Running again with the correct, newer release-upgrader version from
today
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel
# Upgrading Xenial to Bionic on GCE (again with more logs this time)
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04
--classic
# update /etc/update-manager/release-upgrades to Prompt=normal
$ sudo snap info google-cloud-sdk
name: google-cloud-sdk
summary: Google Cloud SDK
publisher: Cloud SDK (google-cloud-sdk✓)
store-url: https://snapcraft.io/google-cloud-sdk
license: unset
description: |
Command-line
# Upgrading Xenial to Bionic on GCE
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
name: google-cloud-sdk
summary: Command-line interface for Google Cloud Platform products and
services
publisher: Cloud SDK
# Upgrading Xenial to Bionic on GCE (again with more logs this time)
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap install google-cloud-sdk --channel latest/stable/ubuntu-16.04
--classic
# Upgrading Bionic to Focal on GCE
1. Launched GCE instance
2. Installed google-cloud-sdk snap
3. Updated system
4. Verified the tracking channel was updated
$ sudo snap info google-cloud-sdk
name: google-cloud-sdk
summary: Google Cloud SDK
publisher: Cloud SDK (google-cloud-sdk✓)
Marking affects linux, so the kernel folks can weigh in on this.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925008
Investigating your other bug caused me to find:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-
rootfs/+merge/398027
Which will set up a custom grub config without quiet. Looking at a
hirsute image, this appears to be the case already. What is remaining is
the SRU back to
Adding livecd-rootfs as this is where I believe this would be changed.
In livecd-rootfs, CPC images get a 50-cloudimg-settings.cfg where
GRUB_CMDLINE_LINUX_DEFAULT is set without quiet. Similarly, ubuntu-core
does something similar in their hooks.
--
You received this bug notification because
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923868
Title:
Bootable buildd images silent on both graphical and
The reason I am looking into this is that we are stating we support
cloud image upgrades from LTS to LTS now. As such, I would hope that the
upgrade process would upgrade the snap channels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't see why ubuntu-desktop is required in either of those bugs. Is
there a defined policy that says we only do snap upgrades on systems
with that package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
# Overview
Recent changes in boot logic moved grub from "removable disk" path to
"/efi/ubuntu" in order to fix grub package updates. This had the side-effect of
adding a 5-second boot delay in images. This was discovered in GCE images
booting Bionic or newer.
# Expected
Public bug reported:
# Overview
Per LP: #1827951 and LP: #1748581, it would appear that if a snap is
tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a
do-release-upgrade the snap channel should update to the new release.
Testing of a Google cloud image, from 20.10 to 21.04
# Summary
All man pages appear to show up as expected, marking all releases as
verification-done.
# Test Steps
All SRUs were tested using an LXD instance from ubuntu-daily. Proposed
was added and cloud-init updated. The apt-cache policy is shown below
and then a directory listing of the man
There was one build failure on xenial: "powerpc: Failed to build".
However, this arch is not a target of this package in images and can be
ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1.
>From my own testing, I used the latest
fwiw LP: #1912835 is tracking this and is already checked in:
https://git.launchpad.net/livecd-rootfs/commit/?id=33b7272a2331279b4c7aa8de73ed8a9069d0bd39
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in 20210222 daily images. Marking fix released.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911059
Title:
gce:
** Description changed:
[Availability]
python-aws-requests-auth was introduced in Bionic as a sync from Debian and
carries no patches. It only depends on packages provided in main (python and
python-requests). The package builds an architecture-independent package (all).
[Rationale]
Public bug reported:
[Availability]
python-aws-requests-auth was introduced in Bionic as a sync from Debian and
carries no patches. It only depends on packages provided in main (python and
python-requests). The package builds an architecture-independent package (all).
[Rationale]
This package
There are build failures in Xenial on powerpc and Focal on riscv64.
These packages are not used on these architectures at all as the Google
cloud does not support these architectures. Additionally, these are new
packages that have not existed before, so this is not a regression.
--
You received
@balint
Here are my logs following the test case:
https://pastebin.ubuntu.com/p/wrjK5nx8cW/
google-compute-engine gets held back, but not gce-compute-image-packages
as the test case says.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Build logs from Groovy package in proposed:
https://launchpadlibrarian.net/517240236/buildlog_ubuntu-groovy-amd64.google-osconfig-agent_20210112.00-0ubuntu1~20.10.0_BUILDING.txt.gz
Verify the build flags:
dh_auto_build -O--buildsystem=golang -- -ldflags="-s -w -X
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1.
>From my own testing images were produced
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1.
>From my own testing images were produced
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1.
>From my own testing images were produced
Based on comments from Google, the initial MIR issues are resolved with
the code found in the following tag:
https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20210202.00
The next steps would be to package that version up, upload the new
version into proposed, and get a re-review.
--
I am adding docker.io package to the affects, as the versions in bionic
(19.03.6) and focal (19.03.8) are just behind the 19.03.9 version
required with a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Thanks for the link about libseccomp. After reading that link and a
couple of bugs on Github about this it seems the root cause is due to
containers of newer releases (e.g. 20.04), which make syscalls that
hosts with older software might not know about.
To resolve then, users need to:
1)
agreed - I can't mark it as won't fix so I will mark it invalid.
** Changed in: google-guest-agent (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901042
Title:
Marking verification done for versions 1.13.8-1ubuntu1~16.04.2 and
1.13.8-1ubuntu1~18.04.2
Steps were the same as previously:
1. Added proposed universe
2. Installed golang-1.13
3. Verified version output from test case
4. Git cloned google guest-agent
Marking verification done for xenial, logs:
https://pastebin.ubuntu.com/p/YkDsDygz9k/
Same steps as above for bionic.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are
Marking verification done for bionic, logs:
https://pastebin.ubuntu.com/p/zKqJMq22BC/
1. Added proposed universe
2. Installed golang-1.13
3. Verified version output from test case
4. Git cloned google guest-agent
(https://github.com/GoogleCloudPlatform/guest-agent)
5. Built package successfully
The regression that was previously seen with the SRU is now fixed [1]
and therefore I am marking this as verification-done-xenial.
[1]
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/l/livecd-
Greater output of journalctl:
https://pastebin.canonical.com/p/XJzPMHrSbx/
** Description changed:
Summary
===
On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud
instance to loose network access.
Expected Result
===
Working network access
Actual
$ sudo journalctl --no-pager -u systemd-networkd-wait-online.service
-- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11
22:01:17 UTC. --
Jan 11 21:30:35 ubuntu systemd[1]: Starting Wait for Network to be Configured...
Jan 11 21:30:37 ubuntu systemd-networkd-wait-online[416]:
Public bug reported:
Summary
===
On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud
instance to loose network access.
Expected Result
===
Working network access
Actual Result
===
After upgrade, network access is lost and serial console is filled with
messages about
This is not limited to GCE cloud images, but also the KVM images from:
https://cloud-images.ubuntu.com/hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911050
Title:
AttributeError:
Public bug reported:
Summary
===
Landscape client MOTD is throwing an exception Hirsuite, which shows up in the
MOTD on launch.
Expected Result
===
No Exceptions
Actual result
===
In the MOTD, the following is printed:
=> There were exceptions while processing one or more plugins. See
** Changed in: tomcat7 (Ubuntu Trusty)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu Zesty)
Assignee: Joshua Powers (powersj) => (unassigned)
** Changed in: tomcat8 (Ubuntu Xenial)
Assignee: Joshua Powers (powersj) => (unassigned)
*
Hi! The packages were released into the archive on December 15, 2020.
Our last build of 2020 was on December 10. The first daily builds of
2021 should have this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I run `sudo snap refresh`, even when there are no snaps out of
date, the google-cloud-sdk snap will say that it is refreshed:
❯ date && sudo snap refresh --list
Wed Dec 30 08:52:43 PM PST 2020
All snaps up to date.
~ took 2s
❯ date && sudo snap refresh
Wed Dec 30
Public bug reported:
Master has manpages [1] and even the debian directory file for including
the manpages [2], however, it looks like the packaging branches do not
have the required debian/manpages file. Please include this file so
future SRUs can have man pages included.
[1]
The xenial verification has failed as once again the package names are
not correct. I have an MP up [1] which reverts back to the original
behavior. Xenial's behavior around shim is not the same as later
releases. This work is not something scheduled till next year.
Bionic [2] and Focal [3] are
Hi Eric, I like the idea and have a few questions about how the client's
behavior would interact with unattended-upgrades:
For example, how should the client determine what status to report? If
the user has at least the default config enabled is that enough for the
client to report yes? What if
Updating the tags so this turns green on the SRU board.
Was `verificiaton-complete` but it should be `verification-done` :)
** Tags removed: verification-complete verification-complete-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699913
Title:
/var/lib/apt/lists has content in partner-images/Docker tarballs,
which
I am going to mark this as won't fix for cloud-images.
grub-legacy-ec2 is only shipped in Xenial and Bionic. In Cosmic it was
removed from the seed, so releases after that do not even have it.
Xenial is coming to end of standard support and needs it for HVM
support. I don't see any major changes
And by HVM support, I actually mean PV support, doh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756420
Title:
replace grub-legacy-ec2 with pv-grub-menu
To manage notifications about this bug
Hi,
Thanks for taking the time to file a bug. I am going to add the cloud-
init project to this bug and mark it incomplete. Given artful was a
while ago and no longer supported, if you are still having your issue,
could you provide some logs?
Thanks!
** Also affects: cloud-init (Ubuntu)
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767131
Title:
Pre-seeded snaps are not necessarily available for use in cloud-init
** Changed in: cloud-images
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882374
Title:
Support inclusion of snap from specific track/channel/branch
To
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880853
Title:
libc6-lse lets update-initramfs fail on AWS m6g instances
To manage
** Changed in: cloud-images
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896604
Title:
Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on
** Changed in: cloud-images
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896443
Title:
The latest Ubuntu base image for armhf return random values for
date/time
# journalctl -u systemd-networkd
https://paste.ubuntu.com/p/9M3xwgwgMj/
# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: failed (Result:
Here are my notes from using a Groovy LXD container:
Expected Results
---
$ resolvectl status | grep "DNS Server"
Current DNS Server: 192.168.100.1
DNS Servers: 192.168.100.1
Actual Results
---
$ resolvectl status
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS
** Attachment added: "journal short-precise"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401580/+files/journal.short
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journal from lxd"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401579/+files/journal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891716
Thanks for the analysis! systemd appears to set this value in:
./sysctl.d/50-pid-max.conf:kernel.pid_max = 4194304
One possible solution is we could override this in our minimal images
only by setting the value to the lower value in
/etc/sysctl.d/90-override.conf
** Also affects: cloud-images
Based on the update above, #17, I am adding the open-iscsi package task.
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Similar to bug 1888000, it appears this failure has also always been
present. I verified this against the focal 20200423 (oldest release with
5.4.0-1009-kvm) and 20200703 (newest release with 5.4.0-1018-kvm)
serials.
While this is no longer blocking image publication, is this something
that could
Thanks for the review, it turns out that this failure has always been
present.
Going back to the Bionic 20180705 and Xenial 20180705, which were the
first releases of minimal, also showed that the system "Failed to find
module 'ib_iser'".
Is this something that could be fixed in order to prevent
Apport info was collected and attached... moving to confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888001
Title:
Apport info was collected and attached... moving to confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888000
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393621/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888000
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393619/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888000
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393613/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393617/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888000
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393615/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393611/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1888000/+attachment/5393612/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888000
Public bug reported:
Overview
---
This is *blocking* new minimal image promotion. Starting on or around 20200714,
the Bionic and Xenial minimal cloud images reported they failed to load kernel
modules.
Expected results
---
$ sudo systemctl list-units --failed --no-legend
# Return no failed
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393620/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888001
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393616/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393622/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888001
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393614/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393618/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888001
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1888001/+attachment/5393610/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888001
1 - 100 of 1833 matches
Mail list logo
