** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1918970
Title:
Unable to netboot Ubuntu 18.04 and
Upstream bug reported at
https://gitlab.freedesktop.org/upower/upower/-/issues/136
** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #136
https://gitlab.freedesktop.org/upower/upower/-/issues/136
--
You received this bug notification because you are a member of Ubuntu
Touch
I've been monitoring upower and I think the problem is it is incorrectly
detecting the number of batteries in my laptop. I only have one yet
upower detects 5 power sources. One of them is a DisplayDevice which
normally shows the same amount of battery as my system battery.
Sometimes that drops to
Public bug reported:
Whenever I go on battery after 20-30 minutes upower will very abruptly
think my battery is at 1% and force my laptop to hibernate. This seems
to happen at random times, I've seen it when my battery was reported to
be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up
** No longer affects: util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Changed in: maas/2.7
Importance: Undecided => Critical
** Changed in: maas/2.7
Assignee: (unassigned) => Lee Trager (ltrager)
--
You received this bug notification because you are a member of Ubuntu
Touch
* Changed in: maas/2.8
Importance: Undecided => High
** Changed in: maas
Importance: High => Critical
** Changed in: maas/2.8
Importance: High => Critical
** Changed in: maas
Milestone: None => 2.9.0b1
** Changed in: maas
Assignee: (unassigned) => Lee Trager (ltrager)
I was able to reproduce this bug by emulating an IDE in QEMU device and
running the smartctl-validate test. I have filed an upstream bug as
well.
https://github.com/karelzak/util-linux/issues/1098
** Bug watch added: github.com/karelzak/util-linux/issues #1098
MAAS contains a way to automatically install drivers. Every region has a
file, /etc/maas/drivers.yaml, which specifies drivers which should be
automatically installed. I don't have access to any test hardware but I
*think* this should work. One thing I noticed is there isn't a meta
package for the
That makes sense based on the other information in this bug.
MAAS sends the test runner a list of storage devices to run hardware
tests on. The test runner uses the model and serial to map to a block
device name. This block device name is passed to the smartctl-validate
script. smartctl-validate
NetworkManager isn't installed in the base MAAS Focal image.
Are you using the default image from images.maas.io?
What cloud-init user-data are you sending to the install?
Have you modified the preseed file at all?
** Changed in: maas
Status: New => Incomplete
--
You received this bug
I spoke with the LXD team and they're passing through the name they get
from the kernel. It seems like this may be a bug that was introduced to
util-linux with RAID devices. I tried running lsblk on Focal against two
NVME drives and I do not see an underscore used in model names.
@cees - Can you
Ryan has updated Curtin to no longer require that util-linux feature. I
do think it would be good to carry that patch in Ubuntu as it other
users will be effected by that regression.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Bug watch added: Debian Bug tracker #951217
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217
** Also affects: util-linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217
Importance: Unknown
Status: Unknown
--
You received this bug notification
I tested a Disco image today with multipath-tools installed and I still
get the same thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1813227
Title:
lvm2-pvscan
** Attachment added: "lsblk output"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233345/+files/lsblk.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
The MAAS ephemeral environment does not have the multipath kernel module
nor multipath-tools. To get this log I had to install both.
** Attachment added: "multipath.log"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5233346/+files/multipath.log
--
You received this
** Description changed:
The lvm2-pvscan service fails to start in the MAAS ephemeral
environment. The service takes ~3 minutes to fail, blocking boot until
- failure.
+ failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM.
Release: 18.10(18.04 does not currently boot on
** Attachment added: "jourctl output of lvm2"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5232337/+files/lvm.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Public bug reported:
The lvm2-pvscan service fails to start in the MAAS ephemeral
environment. The service takes ~3 minutes to fail, blocking boot until
failure.
Release: 18.10(18.04 does not currently boot on S390X DPM)
Kernel: 4.18.0-13-generic
LVM: 2.02.176-4.1ubuntu3
root@node3:~# lvm
I'm having trouble coming up with a simpler test case myself. Here is
how you can reproduce with lp:maas-images on Zesty with
bash-4.4-1ubuntu1
mkdir maas-images
cd maas-images
bzr init
bzr branch lp:maas-images
cd
export PATH=/home/ubuntu/maas-images/trunk/bin:$PATH
wget
Public bug reported:
The MAAS team uses a script, lp:maas-images, which generates the images
available at images.maas.io. As part of this process we use the
following to convert a SquashFS image to an ext4 image.
sudo bash -ec 'src="$1"; img="$2"; trgmp="$3";
mounts=""
cleanup() { for m
I'm running into the same issue. My network doesn't have IPv6 although
its configured to try, turning off IPv6 had no effect.
If I direct all traffic through the VPN ('Use this connection only for
resources on its network' in the routes window is left unchecked) I get
a DNS server but its not
23 matches
Mail list logo
