Public bug reported:
If you enable fraction scaling and then login using an X11 session, the
mouse cursor that existed on the login screen (gdm3) will persist after
logging in. This mouse cursor continues to exist at the same pixel
coordinates as when the login was completed. A new mouse cursor
Thanks for the bug report and pointer to the shlex.quote().
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It doesn’t work for me either. I downloaded latest image and booted live. It
didn’t work there either.
I’m not sure why it was marked fix when it never worked for me. I was the one
who first reported the bug.
Sent from my iPhone
> On Apr 24, 2020, at 1:21 AM, You-Sheng Yang
Public bug reported:
Tried installing Ubuntu 20.04 on a mid-204 MBP, file checks showed 1
error. Installer crashed when trying to install. No other partitions on
this MBP
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic
Public bug reported:
Description:Ubuntu 20.04 LTS
Release:20.04
# apt-cache policy multipath-tools
multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
*** 0.8.3-1ubuntu2 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x
Following up my question; we should see both events in all kernels.
The first event is when the /dev/bcache0 is joined with a cache device,
and emitts the CACHED_UUID value in the uevent; the UUID is the *backing
device bcache metadata UUID* it is not related to the content contained
within the
So, this looks like the bug to me:
Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0:
/usr/lib/udev/rules.d/60-persistent-storage.rules:112 LINK
'disk/by-uuid/30b28bee-6a1e-423d-9d53-32c78ba5454a'
Apr 21 14:15:43 ubuntu-focal systemd-udevd[1916]: bcache0: Updating old name,
Do we have any more information on why we now get two events in Focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
To manage
Sorry, I said 4.2-3ubuntu6 but meant 1:4.2-3ubuntu6~ppa5 from the PPA
(which works). Sounds like Colin got 1:4.2-3ubuntu6 from the PPA; I
will test 1:4.2-3ubuntu6 from -proposed to be sure.
$ apt-cache policy qemu-system-misc
qemu-system-misc:
Installed: 1:4.2-3ubuntu6~ppa5
Candidate:
Yep, 1:4.2-3ubuntu6 from focal-proposed test case works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872945
Title:
risc-v doubles getting clobbered somehow
To manage notifications about
@Paolo, test kernel didn't work for me. I had to reinstall official
Realtek driver again like i did in #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871182
Title:
[RTL810xE] No ethernet
Confirmed qemu 4.2-3ubuntu6 fixes the OpenSSH sshd hang on riscv64
guest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872945
Title:
risc-v doubles getting clobbered somehow
To manage
Will this fix make it to ubuntu2~18.04.3 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/1859509
Title:
wsl-integration.sh shows error when .cache/ can't be created
To manage notifications
Yes, adding realtek to /etc/modules makes the ethernet work. I'm not
sure if thats the actual bug.
$ systemd-analyze
Startup finished in 9.434s (firmware) + 4.866s (loader) + 3min 22.039s (kernel)
+ 56.143s (userspace) = 4min 32.483s
graphical.target reached after 55.830s in userspace
System
Still having issues even after update to 5.4.0-24 today. found a work
around by downloading latest driver from realtek here
https://www.realtek.com/en/component/zoo/category/network-interface-
controllers-10-100m-fast-ethernet-pci-express-software. followed
directions from here with latest drivers
Public bug reported:
The pictures displayed in the 'Global Theme' section of the System
Settings still displays the same preview image for Kubuntu 19.10. This
should be updated so that it will be an accurate representation of the
default theme used in Plasma 5.18 LTS.
I've attached a screenshot
** Attachment added: "Screenshot of Dolphin depicting how post-install defaults
should be: symbols on all user folders"
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1872382/+attachment/5352942/+files/Screenshot_20200412_212325.png
--
You received this bug notification because
Public bug reported:
In Kubuntu 20.04 LTS, there is a visual inconsistency present with the
default set of folders in the user's home directory. Note in the
screenshot (or in a fresh installation) how most of the folders in the
home directory have folder icons with a symbols representing the use
> This is in an integration lab so these hosts (including maas) are stopped,
> MAAS is reinstalled, and the systems are redeployed without any release
> or option to wipe during a MAAS release.
> Then MAAS deploys Bionic on these hosts thinking they are completely new
> systems but in reality they
>
> Ryan,
> We believe this is a bug as we expect curtin to wipe the disks. In this
> case it's failing to wipe the disks and occasionally that causes issues
> with our automation deploying ceph on those disks.
I'm still confused about what the actual error you believe is
I've bisected the problem down to commit
c35a4a858d0616e7817026d88f377c7201ad449a ("block: fix an integer
overflow in logical block size", upstream
ad6bf88a6c19a39fb3b0045d78ea880325dfcf15).
I don't know what the exact problem is with the commit, but seems to be
in the area of fs/block_dev.c
During a clear-holders operation we do not need to catch any failure;
we're attempting to destroy the devices in question. The destruction of
a device is explicitly requested in the config via a wipe: value[1]
present on one or more devices that are members of the LV.
1.
I'm on Focal desktop, running kvm like so
qemu-system-x86_64 -smp 2 -m 1024 --enable-kvm \
-drive id=disk0,if=none,format=qcow2,file=bionic-bcache-links.qcow2 \
-device virtio-blk-pci,drive=disk0,bootindex=0 \
-drive id=disk1,if=none,format=raw,file=bcache1.img \
-device
It appears that it's always been a touch racy. Curtin does not create
bcaches like the script does (make-bcache --wipe-bcache -C /dev/sdc -B
/dev/sdb), rather we make the cache-dev and backing dev separately, and
then attach them by echoing the cacheset uuid into the bcache device
attach sysfs
Requested output on bionic release image (4.15-20)
** Attachment added: "bcache-release-4.15-20.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861941/+attachment/5350481/+files/bcache-release-4.15-20.txt
--
You received this bug notification because you are a member
Requested data from a daily cloud image with 4.15-76
** Attachment added: "bcache-daily-4.15-76.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861941/+attachment/5350483/+files/bcache-daily-4.15-76.txt
--
You received this bug notification because you are a member of
This is related to the initramfs tools package
** Also affects: cloud-initramfs-tools
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
BTW, for future searchers, I've uploaded dmesg.202004081903 separately,
and pasted the crash here:
[ 194.36] bcache: bch_journal_replay() journal replay done, 3 keys in 6
entries, seq 23285862
[ 194.444622] bcache: register_cache() registered cache device sdb1
[ 194.448381] bcache:
If you can, please run 'cloud-init collect-logs' and attach the tarball
it creates? ; You'll need to unpack and repack the tarball as the cloud-
init.log will have the network-config unredacted and I see you redacted
your wifi password. Sorry for the trouble there.
--
You received this bug
Please move this back to New once you've attached the requested
information.
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here you go: https://www.finnie.org/stuff/lp1867916-crashdump.tar.xz
(138MB)
Some notes on the process:
- Also blacklisted it87 (DKMS) so the running kernel wasn't "tainted"
- Also disabled the relevant crypttab entry for this group
- 768M produced "crashkernel reservation failed - No suitable
I'm marking curtin task invalid; this looks like kernel/platform issue
at this point. Please reopen curtin task if curtin needs to fix
something.
** Changed in: curtin
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The current error looks like /target got unmounted ... or there was some
corruption that forced the mount into read-only mode...
Running command ['sh', '-c', 'mkdir -p "$2" && cd "$2" && rsync -aXHAS
--one-file-system "$1/" .', '--', '/media/filesystem', '/target'] with allowed
return codes
Can we get the /var/log/installer/block/probe-data*.json files?
Also, if you have the var-crash from your failed UEFI install, that would help
me fix the UEFI install.
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New => Incomplete
I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way. Here's my layout:
-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
>
This is still occurring daily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
To manage notifications about this bug go to:
Public bug reported:
ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors
in log with realtek. long boot up. No problems with live-USB or fresh
install, only after update.
sudo lspci -vnvn > lspci-vnvn.log
pcilib: sysfs_read_vpd: read failed: Input/output error
ProblemType:
Thanks Benno. Yeah, I've tested that works (albeit with s,'\r',CR_CODE,
on the - line since focal is currently 4.8). I've asked -release if
it's possible to get a sync exception for 4.9.1-1 from sid since focal
is past the freeze, rather than trying to SRU this (and e.g. LP:
#1866820 crash);
** Summary changed:
- Multi-line paste broken between kitty ~0.15 and nano 8.4 [focal]
+ Multi-line paste broken between kitty and nano 4.8 [focal]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ubuntu 20.04 Focal beta (as of 2020-04-04)
nano 4.8-1
What I expect to happen: multi-line paste into nano via kitty pastes
multiple lines.
What happens instead: pasted multi-line text is one line with no line
breaks.
There is a bit of a spat between the developers of kitty
I believed I narrowed down the issue to how gnome-shell uses Xorg.
As said before GDM did not have any issues, and (i may be seriously
wrong here) GDM uses Wayland by default. When I launch the Ubuntu
desktop with Wayland, the graphical issue went away and is running
smoothly.
So I narrowed down
No problem!
When I change wallpapers the issue appears goes away but on reboot or
switching back the issue persists. it appears to not affect other
applications such as Firefox even when in full screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
problems appear on the desktop and lock screen (not in gdm)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture:
https://github.com/canonical/cloud-init/pull/306
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1870421
Title:
cloud-init
The docs need updating, we do copying netplan through to target, and emit a
warning.
Ubuntu Server images have a default policy of not configuring wifi with
networkd, but
letting network-manager do that. That said, you can override this policy with
a change
to your netplan provided.
I think
^^ ignore this, my 4 year old found my keyboard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859509
Title:
wsl-integration.sh shows error when .cache/ can't be created
To manage notifications
+1 for me. MySQL starts with that error and does run but is not stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859509
Title:
wsl-integration.sh shows error when .cache/ can't be created
To
@Balint,
Apologies for not responding sooner.
Perf-wise, the delta between with and without worst-case values from your
results:
(0.959 - 0.624) = .335s
is a non-trivial amount (almost 50% more) overhead for a single
connection.
Users (or programs) may run concurrent ssh sessions, which I
** Branch unlinked: lp:~fo0bar/livecd-rootfs/livecd-rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580326
Title:
Add raspi3 subarch
To manage notifications about this bug go to:
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
2. % apt-cache policy python-pip-whl
python-pip-whl:
Installed: 20.0.2-2
Candidate: 20.0.2-2
Version table:
*** 20.0.2-2 500
500
I've queued up these changes for the upstream package in Debian for the
-2 revision: https://salsa.debian.org/science-team/meshlab (I've
actually added `%F` since it can handle multiple files)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866563
Title:
I can confirm that davidaf's work around worked. Though the interesting
thing to me was that in 19.10 I didn't have to put the file in initrafs.
After upgrading to the 20.04 daily builds this became necessary. Not
sure if that means anything or not. Just thought I'd provide an extra
data point.
Ah, from the journal.log:
Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1008-azure
root=PARTUUID=1261a2c6-48ca-43ee-9b70-197f5b89b82c ro console=tty1
console=ttyS0 earlyprintk=ttyS0 panic=-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
None of the VMs will be using spinning disks, it's all SSD; and virtual
disks anyhow.
I would not expect much timing difference on virtual hardware; there
aren't real device or pci timing delays; though the kernel may wait for
them; however, it should be consistent.
In terms of the things that
Still a major laptop usability problem in eoan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
Desktop unable to Suspend when Inactive
To manage notifications about this bug go to:
Public bug reported:
traps: gnome-shell[123022] trap int3 ip:7f15b03dc0d5 sp:7ffe1bfdf010
error:0 in libglib-2.0.so.0.6400.1[7f15b03a+84000]
% dmesg | grep trap
[18311.547270] traps: gnome-shell[12034] trap int3 ip:7f33128f30d5
sp:7fff3a3b0be0 error:0 in
I've created a PPA with the upstream patch from #6 included.
https://launchpad.net/~raharper/+archive/ubuntu/lp1864506
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864506
Title:
gnome-flashback
On my Thinkpad X1 Carbon 4th Gen, I was able to work around this issue
by disabling the security module (TPM) in bios. After that
suspend/resume works.
Suspend/resume had worked fine for years on this laptop. It stopped
working correctly on the upgrade to a 5.X kernel.
--
You received this bug
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Tags added: uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867029
Title:
Package ifupdown breaks
What is this?
> netcfg/do_not_use_netplan=true
And none of your network interfaces are up; in a curtin install, it would have
written out
the maas network config into the target system.
Do you have the curtin verbose install log?
https://discourse.maas.io/t/getting-curtin-debug-logs/169
If a
In particular, user passed in cloud-config for augmenting ssh
configuration in the guest (setting user ssh keys) however, it was
unknown that the centos/8/cloud image did not have sshd installed.
If I'm building a template and install cloud-init; I can see either
path, cloud-init does not
source issue where this came up.
https://github.com/lxc/lxc-ci/issues/132#issuecomment-596254076
** Bug watch added: github.com/lxc/lxc-ci/issues #132
https://github.com/lxc/lxc-ci/issues/132
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
cloud-init expects that sshd is installed in images but it does not
directly depend on it. We should explicitly enumerate this to ensure
that when images are built that the cloud-init package pulls in the sshd
service.
** Affects: cloud-init (Ubuntu)
Importance:
Public bug reported:
In some images, centos/8/cloud image in LXD for example, there is not
hostname binary and cloud-init expects to have the hostname binary
present. The centos/8/cloud image does have hostnamectl which has a
--set-hostname parameter which can be used instead.
% lxc launch
On Thu, Mar 5, 2020 at 1:53 PM Bryce Harrington <
bryce.harring...@canonical.com> wrote:
> As followup to our retrospective, this past year I've found and played
> with several tools, that I thought might be worth show-and-telling
> about, and given our corona-sprint we're in will do so via
** Attachment added: "slapd.conf"
https://bugs.launchpad.net/bugs/1866303/+attachment/5334194/+files/slapd.conf
** Attachment added: "data.ldif"
https://bugs.launchpad.net/bugs/1866303/+attachment/5334195/+files/data.ldif
** Attachment added: "samba.schema"
Public bug reported:
Hello,
Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue
in the ppolicy overlay that can crash slapd. Please also consider SRUing
the patch after it has had some testing time.
Upstream: https://openldap.org/its/?findid=9171
Debian:
Attaching first 1300 lines of dmesg
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1866191/+attachment/5333894/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After performing the release upgrade from 19.4 to 19.10, my system is no
longer booting.
After unlocking the disk encryption, the system begins loading and
freezes with:
'''
aufs aufs_fill_super:920:mount[3405]: no arg
overlayfs: missing 'lowerdir'
'''
I was able to add
*** This bug is a duplicate of bug 1863261 ***
https://bugs.launchpad.net/bugs/1863261
I do not believe this is a duplicate; It is more likely a *packaging*
issue. The question remains for this bug, why does it only appear in
the focal kernels; but not Eoan or older?
And if someone could
An easy recreate:
lxc launch ubuntu-daily:focal f1
lxc exec f1 bash
apt update && apt install linux-generic
This does not fail on eoan or bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note, by fail, we mean depmod emits the error message mentioned in bug
title; there is nothing *functionally* wrong; just scary/noisy output
which it did not use to produce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can recreate the issue inside an LXC container on focal only (bionic,
disco, eoan) and without any dpkg-divert of update-initramfs; as such
I'm marking the curtin task invalid.
** Changed in: curtin
Status: Incomplete => Invalid
--
You received this bug notification because you are a
My bad, I thought this was fixed by the sync, but it looks like it got
caught up by the debian import freeze.
** Changed in: opensmtpd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The primary concern is time before rootfs mounting and executing
/sbin/init. For the spots after that, that falls into systemd
territory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858495
Title:
> 14:48:15> this slowness is happening with a particular
instance type?
I've not tested extensively across all types; but it's common for any of
the "fast" types which have SSD backing. I've seen this DS1_v2, DS2_v2,
DS3_v3, D4-v2, B2s, A2s, L4s
> 14:49:38> the slowness is happening across
here is some debug data I captured:
-rw-rw-r-- 1 ubuntu ubuntu 729 Dec 16 12:15
bug-bionic-baseline-after-templating-Standard-DS2-v2.csv
drwxrwxr-x 12 ubuntu ubuntu 22 Dec 16 12:15
bug-bionic-baseline-after-templating-Standard-DS2-v2.csv.debug/
-rw-rw-r-- 1 ubuntu ubuntu 721 Dec 16 13:07
** Changed in: curtin (Ubuntu)
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/1861452
Title:
sru curtin 2020-02-14 - 19.3-26-g82f23e3d-0ubuntu1
To manage
Sorry for missing the questions earlier.
Azure has two "machine types" gen1 which boots a non-uefi based virtual
hardware platform and gen2 which is UEFI with newer virtual hardware,
details here:
https://azure.microsoft.com/en-us/updates/generation-2-virtual-machines-
** Changed in: opensmtpd (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: opensmtpd (Ubuntu Eoan)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
OpenBSD 6.6 errata 021, February 24, 2020:
An out of bounds read in smtpd allows an attacker to inject arbitrary
commands into the envelope file which are then executed as root.
Separately, missing privilege revocation in smtpctl allows arbitrary
commands to be run with the
On Tue, Feb 25, 2020 at 2:35 PM Scott Moser
wrote:
> this seemed to "just work" for me.
> http://paste.ubuntu.com/p/93dWDPZfZT/
Ah, I didn't check that there was an existing ubuntu/devel branch. Sorry.
I've pushed a MR here:
@Scott,
cloud-utils isn't quite new-upstream-snapshot out of the box; the debian
dir does not contain the changelog; however, I think I've got this
sorted out. I've a MP I can put up; but it only will show the add of
the changelog file. I'll attach a debdiff and a source package.
--
You
** Attachment added: "tarball of source package to upload"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330895/+files/cloud-utils_0.31-7-gd99b2d76-source.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "debdiff showing the changes to upload to fix the bug."
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330894/+files/cloud-utils_0.31-6_to_0.31-7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That sounds like a good fix. It will trip in bionic, but ubuntu images
don't include multipath package by default (which pulls in sg3-utils).
If you install this in bionic, I suspect it will fail just the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "Xenial vmtest console log from rerunning tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330713/+files/curtin-vmtest-proposed-x-console-v2.log
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Eoan vmtest artifacts from rerunning timedout tests"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330717/+files/curtin-vmtest-proposed-x-artifacts-v2.tar.xz
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports
** Attachment added: "Eoan vmtest console log, including rerun of timed out
tests."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330715/+files/curtin-vmtest-proposed-e-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330711/+files/curtin-vmtest-proposed-b-console-v2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Eoan vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330716/+files/curtin-vmtest-proposed-e-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Xenial vmtest artifacts from rerunning tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330714/+files/curtin-vmtest-proposed-x-artifacts-v2.tar.xz
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Bionic vmtest console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330709/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330712/+files/curtin-vmtest-proposed-b-artifacts-v2.tar.xz
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Bionic curtin vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330710/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Xenial vmtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330667/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Xenial vmtest console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330655/+files/curtin-vmtest-proposed-x-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "MAAS QA results for curtin-proposed-bionic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330654/+files/maas-qa-curtin-sru-bionic.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "MAAS QA results for curtin-proposed-xenial"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5330653/+files/maas-qa-curtin-sru-xenial.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
301 - 400 of 9903 matches
Mail list logo
