DIB: unable to build overcloud-hardened-uefi-full image

Bug #1959568 reported by Cédric Jeanneret
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
High
Steve Baker

Bug Description

Hello there,

While trying to build the mentioned image, I hit an issue with lvm and the loop device (see bellow for the extracted data, and attachment for the full log).

Apparently, it's able to create the volume-group, but then fails to create the logical volume. I'm still investigating the actual error reported by the "exec_sudo" ("/dev/vg/lv_root: not found: device not cleared") - but I've never seen this issue so far.

Notes:
- I'm building from within a privileged container (launched as root)
- I don't see any SELinux denials at the time of the build

I'm still investigating, but since I'm also hitting another issue[1], it's taking some more time...

[1] https://bugs.launchpad.net/tripleo/+bug/1959093

Log extract:

2022-01-31 08:24:42.226 | INFO diskimage_builder.block_device.utils [-] Calling [sudo vgcreate vg /dev/mapper/loop0p3 --force]
2022-01-31 08:24:42.286 | DEBUG diskimage_builder.block_device.utils [-] exec_sudo: Not creating system devices file due to existing VGs. exec_sudo /root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/utils.py:135
2022-01-31 08:24:42.288 | DEBUG diskimage_builder.block_device.utils [-] exec_sudo: Volume group "vg" successfully created exec_sudo /root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/utils.py:135
2022-01-31 08:24:42.314 | DEBUG diskimage_builder.block_device.level1.lvm [-] Creating lv command [['lvcreate', '--name', 'lv_root', '-l', '69%VG', 'vg']] _create /root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/level1/lvm.py:204
2022-01-31 08:24:42.314 | INFO diskimage_builder.block_device.utils [-] Calling [sudo lvcreate --name lv_root -l 69%VG vg]
2022-01-31 08:24:42.350 | DEBUG diskimage_builder.block_device.utils [-] exec_sudo: /dev/vg/lv_root: not found: device not cleared exec_sudo /root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/utils.py:135
2022-01-31 08:24:42.351 | DEBUG diskimage_builder.block_device.utils [-] exec_sudo: Aborting. Failed to wipe start of new LV. exec_sudo /root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/utils.py:135
2022-01-31 08:24:42.401 | ERROR diskimage_builder.block_device.blockdevice [-] Create failed; rollback initiated
2022-01-31 08:24:42.401 | Traceback (most recent call last):
2022-01-31 08:24:42.402 | File "/root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/blockdevice.py", line 407, in cmd_create
2022-01-31 08:24:42.402 | node.create()
2022-01-31 08:24:42.402 | File "/root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/level1/lvm.py", line 280, in create
2022-01-31 08:24:42.402 | lvs._create()
2022-01-31 08:24:42.402 | File "/root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/level1/lvm.py", line 205, in _create
2022-01-31 08:24:42.402 | exec_sudo(cmd)
2022-01-31 08:24:42.402 | File "/root/workspace/82142cdf4dd511032b48543abbec9229/venv/lib64/python3.9/site-packages/diskimage_builder/block_device/utils.py", line 143, in exec_sudo
2022-01-31 08:24:42.402 | raise e
2022-01-31 08:24:42.402 | diskimage_builder.block_device.exception.BlockDeviceSetupException: exec_sudo failed

Revision history for this message
Cédric Jeanneret (cjeanner) wrote :
Revision history for this message
Steve Baker (steve-stevebaker) wrote :

> - I'm building from within a privileged container (launched as root)

This is likely the cause. See my comment in #1959093

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.