a workaround of course is to rename the LVs in the old VGs ... but that
may be sub-optimal for some workflows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088061
Title:
Fail configuring lvm_parti
subiquity debug log
** Attachment added: "jammy_installer_subiquitydebug.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2088061/+attachment/5836866/+files/jammy_installer_subiquitydebug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
curtin log
** Attachment added: "jammy_installer_curtin.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2088061/+attachment/5836867/+files/jammy_installer_curtin.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
When curtin compares the size of the Logical Volume (LV) against what is
specified in autoinstall.yaml; it does not specify which Volume Group
(VG) to use.
In a machine with multiple different VGs each containing LVs with the
same names (e.g. "root" on old system disks) this
Brilliant! This seems to have solved the issues on our new Dell OptiPlex
7090s too .
Apologies if this is obvious ... but does this fix end up being back-
ported into HWE (I seem to recall reading that it may do that after 3
weeks or something?)
Thanks!
--
You received this bug notification bec
