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 causes the installer
to FAIL.
"finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring lvm_partition: lvm-partition-root"
This occurs even when specifying which VG to use in autoinstall.yaml.
=== command output used by curtin ===
root@holly-b:/# lvdisplay -C --separator = --noheadings -o lv_name,lv_size
--units=B
root=86973087744B
scratch=904099004416B
swap=8589934592B
root=99996401664B
scratch=892203958272B
swap=7998537728B
root=99996401664B
scratch=1891861790720B
swap=7998537728B
============================================
=== proposal of command to use instead - specifying the VG ===
root@holly-b:/# lvdisplay -C --separator = --noheadings -o lv_name,lv_size
--units=B HollybSys00
root=99996401664B
scratch=1891861790720B
swap=7998537728B
============================================
=== snippet from autoinstall.yml ===
- device: disk-nvme0n1
id: partition-lvm
number: 3
preserve: true
size: 1999858827264
type: partition
- devices:
- partition-lvm
id: lvm-volgroup-HollybSys00
name: HollybSys00
preserve: true
type: lvm_volgroup
- id: lvm-partition-root
name: root
preserve: true
size: 99996401664B
type: lvm_partition
volgroup: lvm-volgroup-HollybSys00
wipe: superblock
============================================
=== snippet from curtin log ===
Running command ['vgchange', '--activate=y'] with allowed return codes [0]
(capture=True)
3 logical volume(s) in volume group "HolidaySys00-old" now active
3 logical volume(s) in volume group "HolidaySys00" now active
3 logical volume(s) in volume group "HollybSys00" now active
Running command ['pvdisplay', '-C', '--separator', '=', '--noheadings',
'-o', 'vg_name,pv_name'] with allowed return codes [0] (capture=True)
Verifying lvm volgroup HollybSys00 members, expected
{'/dev/nvme0n1p3'}, found {'/dev/nvme0n1p3'}
lvm_volgroup HollybSys00 already present, skipping create
Running command ['pvscan'] with allowed return codes [0] (capture=True)
Running command ['vgscan'] with allowed return codes [0] (capture=True)
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: SUCCESS:
configuring lvm_volgroup: lvm-volgroup-HollybSys00
start: cmd-install/stage-partitioning/builtin/cmd-block-meta:
configuring lvm_partition: lvm-partition-root
Running command ['lvdisplay', '-C', '--separator', '=', '--noheadings',
'-o', 'vg_name,lv_name'] with allowed return codes [0] (capture=True)
Verifying root logical volume is in HollybSys00 volume group, found
['root', 'scratch', 'swap']
Running command ['lvdisplay', '-C', '--separator', '=', '--noheadings',
'-o', 'lv_name,lv_size', '--units=B'] with allowed return codes [0]
(capture=True)
Verifying root logical value is size bytes 99996401664, found
86973087744
An error occured handling 'lvm-partition-root': RuntimeError -
Verifying root logical value is size bytes 99996401664, found 86973087744
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring lvm_partition: lvm-partition-root
============================================
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: curtin jammy subiquity
--
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_partition when multiple LVs of same name exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2088061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
