Comment 6 for bug 1959093

This is almost certainly caused by building inside a container, I would advise against that until there is an upstream CI job which builds an LVM based in a container build.

I have all the image build projects installed to a python venv called 'dib' and it works very well. Here is my script for building overcloud-hardened-uefi-full:

pushd /httpboot
source /home/steveb/dev/localstack/envs/dib/bin/activate

export DIB_RELEASE=9-stream
export DIB_DEBUG_TRACE=2

# from https://cloud.centos.org/centos/9-stream/x86_64/images/
export DIB_LOCAL_IMAGE=./CentOS-Stream-GenericCloud-9-20220120.0.x86_64.qcow2
export break=before-pre-finalise
# export break=before-install
branch=master
repo=current
repodir="/httpboot/repos-$branch-$repo"
mkdir $repodir || true
tripleo-repos --output-path $repodir -d centos9 -b $branch $repo ceph deps

export DIB_YUM_REPO_CONF="$repodir/*"

export ELEMENTS_PATH="/home/steveb/dev/localstack/envs/dib/share/tripleo-puppet-elements:/home/steveb/dev/localstack/envs/dib/share/tripleo-image-elements:/home/steveb/dev/localstack/envs/dib/share/ironic-python-agent-builder/dib"

rm -rf overcloud-hardened-uefi-full.*

openstack overcloud image build --verbose --debug --no-package-install \
    --image-name overcloud-hardened-uefi-full \
    --config-file /home/steveb/dev/localstack/envs/dib/share/tripleo-common/image-yaml/overcloud-hardened-images-uefi-python3.yaml \
    --config-file /home/steveb/dev/localstack/envs/dib/share/tripleo-common/image-yaml/overcloud-hardened-images-uefi-centos8.yaml