What commands are you running and what do you expect to happen that does
not?
If you've installed via subiquity then you can use:
/usr/lib/grub/grub-multi-install
which is what it used during the install to mount and mirror the primary
esp to secondary devices.
** Changed in: grub2 (Ubuntu)
> From the changelog you dropped fdisk to avoid having it in chroots and
> squashfs'.
Could there not be a chroot-essential set
> But given that fdisk is no longer part of the essential set, packages that
> invoke it should also be fixed to declare a dependency on it.
When do consumers of the
I believe this commit should resolve this:
https://github.com/CanonicalLtd/subiquity/commit/f9eb715108c1289eb19f48946f7216964373b91f
I'm not sure if that's been published in edge yet.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity
I'm marking the curtin task invalid; we believe the subiquity change
should resolve this issue.
** Changed in: curtin
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
grub-multi-install is affected by this as well.
** Also affects: grub2 (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/1876258
Title:
ubuntu
Probert PR to drop --mknodes:
https://github.com/canonical/probert/pull/88
Curtin MP to drop --mknodes
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/383141
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for filing the bug.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** 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.
Looking at the journal, I can see that networkd attempts to bring wlan0
online; at this point I do not believe this is a cloud-init bug.
I did see this netplan issue yesterday, which may be where you are at:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1874377
** Changed in:
I don't think this is the right fix. We need to test that it doesn't
prevent vgscan from finding and creating /dev/vg/lv device files outside
of of multipath.
The real fix involves:
1) omitting the call to vgmknodes if there are no volume groups present
2) if vgnodes are present,
Note, the whitespace damage in the patch is not needed, just my text
client cleaning up trailing whitespace.
With this patch applied, vgscan --mknodes no longer creates block
devices in /dev/mapper
root@ubuntu:/dev/mapper# ls -al
total 0
drwxr-xr-x 2 root root 120 Apr 28 16:31 .
drwxr-xr-x
This patch configures the dm_task to use the
DM_UDEV_DISABLE_LIBRARY_FALLBACK udev flag to prevent calls to
dm_mknodes() from using the library fallback code.
Another possible fix would be to obtain a different return code from
vgscan.c where it does not detect any VGs and then calls the mknode
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
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
> 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 happening.
Note
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
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.
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
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:
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
@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
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
** 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:
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
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
** 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
*** 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
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-
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
https://github.com/CanonicalLtd/probert/pull/78
** Changed in: probert (Ubuntu)
Importance: Undecided => High
** Changed in: probert (Ubuntu)
Status: New => In Progress
** Changed in: curtin
Importance: Wishlist => High
** Changed in: curtin
Status: Triaged => In Progress
After walking through the code in gdb; I realize now that the --remove-
duplicates only operates on the BootOrder variable; not any of the
actual entries.
root@ubuntu:/home/ubuntu# efibootmgr -v --bootorder 0,1,2,2,2
BootNext: 0001
Timeout: 0 seconds
BootOrder: ,0001,0002,0002,0002
Boot*
This is still broken on 17
** Bug watch added: github.com/rhboot/efibootmgr/issues #125
https://github.com/rhboot/efibootmgr/issues/125
** Also affects: efibootmgr via
https://github.com/rhboot/efibootmgr/issues/125
Importance: Unknown
Status: Unknown
--
You received this bug
printf is a shell built-in which does not exec a new process like echo;
I believe this is a reasonable replacement for use of echo -n
printf "%s" ${1}
Alternatively, if you drop the /bin/echo and use bash's built-in echo;
that also will work as it won't exec a new process.
--
You received this
Here's the upstream changes to growpart I'm suggesting:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-
utils/+merge/379177
I've also proposed on modifications to cloud-init's cc_growpart as a further
method
to aid debugging if this hit as well as some mitigation around the race.
** Summary changed:
- sru curtin 2020-01-30 - 19.3-17-g50ffca46-0ubuntu1
+ sru curtin 2020-02-14 - 19.3-26-g82f23e3d-0ubuntu1
--
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
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
- - multipath removal handling
- - centos8 support
We've had some verifications fail:
https://bugs.launchpad.net/curtin/+bug/1862971
https://bugs.launchpad.net/curtin/+bug/1862973
https://bugs.launchpad.net/subiquity/+bug/1862846
I'll upload a new curtin to -proposed and restart this SRU.
--
You received this bug notification because you are a
> Above are equivalent configs. As far as I understand one of them is newer
> than the other, and one of them is prefered than the other, both are
> supported for legacy reasons.
They are equivalent. Storage config is newer than the grub namespace in
curtin config. Curtin will prefer storage
** Changed in: curtin
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/1862849
Title:
scan for dasd drives
To manage notifications about this bug go to:
The kernel cmdline reader for network-config= expects base64 input,
however documentation suggests that network-config is *optionally*
base64 encoded.
Disabling Network Configuration
===
On Thu, Feb 13, 2020 at 6:20 AM Balint Reczey
wrote:
> @raharper I agree with the concern regarding the manipulation of sshd
> config. To minimize the collision with cloud-init this package does not
> change /etc/ssh/sshd_config like cloud-init does, but overrides the
> configuration value with
** Changed in: curtin (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: curtin (Ubuntu Focal)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: efibootmgr (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: efibootmgr (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: efibootmgr (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
1.
# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
2.
# apt-cache policy efibootmgr
efibootmgr:
Installed: 15-1
Candidate: 15-1
Version table:
*** 15-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
@Lee Thanks for tracking down the util-linux bug.
Since this is broken in 2.34 (eoan/focal); I'm thinking we should use
sysfs to find the parent via device name walking;
Given a kname (nvme0n1p1) of the target partition
# look up sysfs path from kname
% realpath /sys/class/block/nvme0n1p1
@Alberto
> I thought the installer would work similarly to what the desktop installer
> does with btrfs, where it creates subvolumes for / and /home in the root
> partition (as @ and @home).
>
> On my desktop, when I upgrade I just move @ out of the way (by renaming it)
> and the installer
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-ff-incoming
** Also affects: util-linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: High
Status: Triaged
** Also
OK, I think I've found the bug; there are two issues;
if [ "${#grubdevs_new[@]}" -eq 1 ] && [ -f "${grubdevs_new[0]}" ]; then
# Currently UEFI can only be pointed to one system partition. If
# for some reason multiple install locations are given only use the
# first.
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (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/1862846
Title:
Crash and
We only see this failure on shim/secure-boot enabled setups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
To manage notifications about this bug
Hrm, this is a strange install.
The storage config has some strange settings..., first nothing is
modified at all, all disks and partitions are marked preserve = true, as
well as all filesystems. There is this strange mount:
{
"device": "format-0",
"id": "mount-0",
"path": "",
@Lee
The efi_dev parsing code from the centos8 branch isn't happy:
Command: ['sh', '-c', 'exec "$0" "$@" 2>&1', 'install-grub', '--uefi',
'--update-nvram', '--os-family=debian', '/target', '/dev/sda1']
Exit code: 1
Reason: -
Stdout: carryover command line params ''
setting
** Attachment added: "curtin vmtest from bionic-proposed console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5327445/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "curtin vmtest from eoan-proposed console log"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5327447/+files/curtin-vmtest-proposed-e-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "curtin vmtest from eoan-proposed artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5327448/+files/curtin-vmtest-proposed-e-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "curtin vmtest from bionic-proposed artifacts"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452/+attachment/5327446/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
101 - 200 of 1546 matches
Mail list logo
