You'll find the whole build log attached there - for the initial build, on a clean env.
Once the initial failure is hit, a dangling vg, pv and loops are kept - you'll be able to see that in the attached build log.
Also, here are some of the LVM related things that are still present on the node after the failure:
[root@gw-rh build-oc-images]# vgdisplay
--- Volume group ---
VG Name vg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size <5.59 GiB
PE Size 4.00 MiB
Total PE 1430
Alloc PE / Size 0 / 0
Free PE / Size 1430 / <5.59 GiB
VG UUID TlSTf1-NvLo-ZF5N-czwc-j7Ce-gq81-ql8Gkq
--- Volume group ---
VG Name fedora_fedora
[...]
[root@gw-rh build-oc-images]# pvdisplay
--- Physical volume ---
PV Name /dev/mapper/loop1p3
VG Name vg
PV Size <5.59 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 1430
Free PE 1430
Allocated PE 0
PV UUID 321Zp0-lylz-K7l4-c41Z-UuHD-VI2y-ihIC8C
--- Physical volume ---
PV Name /dev/nvme0n1p3
VG Name fedora_fedora
[...]
"/dev/mapper/loop2p3" is a new physical volume of "<5.59 GiB"
--- NEW Physical volume ---
PV Name /dev/mapper/loop2p3
VG Name
PV Size <5.59 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID szN2Rx-4rVM-rWHG-wrAd-K2hp-SZLt-e6U66f
As well as loop devices:
[root@gw-rh build-oc-images]# losetup --list
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC
/dev/loop1 0 0 1 0 /image0.raw (deleted) 0 512
/dev/loop2 0 0 1 0 /image0.raw (deleted) 0 512
/dev/loop0 0 0 0 0 /tmp/tmp.ZgSDIyoRGD/ZwGPFf.raw (deleted) 0 512
Hello Steve,
So, it's still my containerized thing[1], trying to get the overcloud- hardened- uefi-full built.
The initial failure is weird, and described in this other LP: /bugs.launchpad .net/tripleo/ +bug/1959568
https:/
You'll find the whole build log attached there - for the initial build, on a clean env.
Once the initial failure is hit, a dangling vg, pv and loops are kept - you'll be able to see that in the attached build log.
Also, here are some of the LVM related things that are still present on the node after the failure:
[root@gw-rh build-oc-images]# vgdisplay NvLo-ZF5N- czwc-j7Ce- gq81-ql8Gkq
--- Volume group ---
VG Name vg
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size <5.59 GiB
PE Size 4.00 MiB
Total PE 1430
Alloc PE / Size 0 / 0
Free PE / Size 1430 / <5.59 GiB
VG UUID TlSTf1-
--- Volume group ---
VG Name fedora_fedora
[...]
[root@gw-rh build-oc-images]# pvdisplay lylz-K7l4- c41Z-UuHD- VI2y-ihIC8C
--- Physical volume ---
PV Name /dev/mapper/loop1p3
VG Name vg
PV Size <5.59 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 1430
Free PE 1430
Allocated PE 0
PV UUID 321Zp0-
--- Physical volume ---
PV Name /dev/nvme0n1p3
VG Name fedora_fedora
[...]
"/dev/ mapper/ loop2p3" is a new physical volume of "<5.59 GiB" 4rVM-rWHG- wrAd-K2hp- SZLt-e6U66f
--- NEW Physical volume ---
PV Name /dev/mapper/loop2p3
VG Name
PV Size <5.59 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID szN2Rx-
As well as loop devices: ZgSDIyoRGD/ ZwGPFf. raw (deleted) 0 512
[root@gw-rh build-oc-images]# losetup --list
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC
/dev/loop1 0 0 1 0 /image0.raw (deleted) 0 512
/dev/loop2 0 0 1 0 /image0.raw (deleted) 0 512
/dev/loop0 0 0 0 0 /tmp/tmp.
And device manager content fedora- containers (253:2)
[root@gw-rh build-oc-images]# dmsetup ls
fedora_
fedora_fedora-home (253:1)
fedora_fedora-root (253:0)
loop0p1 (253:3)
loop1p1 (253:4)
loop1p2 (253:5)
loop1p3 (253:6)
loop2p1 (253:7)
loop2p2 (253:8)
loop2p3 (253:9)