given the specific error overcloud.AllNodesDeploySteps.ControllerDeployment_Step5.0: resource_type: OS::Heat::StructuredDeployment physical_resource_id: bb111b79-92fa-40e4-b3bc-ffa7728cad46 status: CREATE_FAILED status_reason: | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 deploy_stdout: | ... "d4c5defb60c6: Verifying Checksum", "d4c5defb60c6: Download complete", "stderr: failed to register layer: Error processing tar file(exit status 1): write /var/lib/rpm/Packages: no space left on device" It appears to be issue with the partition size /var is 100% [root@controller-0 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg-lv_root 6.0G 2.9G 3.2G 48% / devtmpfs 16G 0 16G 0% /dev tmpfs 16G 54M 16G 1% /dev/shm tmpfs 16G 11M 16G 1% /run tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/mapper/vg-lv_home 213M 12M 202M 6% /home /dev/mapper/vg-lv_tmp 873M 33M 841M 4% /tmp /dev/mapper/vg-lv_var 8.6G 8.6G 25M 100% /var
Backporting fixes from Rocky to Queens
Environment: openstack-tripleo-common-8.6.6-16.el7ost.noarch openstack-tripleo-common-containers-8.6.6-16.el7ost.noarch grep SIZE /usr/share/openstack-tripleo-common/image-yaml/overcloud-hardened-images.yaml DIB_IMAGE_SIZE: '40' [root@controller-0 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 40G 0 disk ├─vda1 252:1 0 8M 0 part /boot/efi ├─vda2 252:2 0 8M 0 part ├─vda3 252:3 0 37.3G 0 part │ ├─vg-lv_root 253:0 0 8.6G 0 lvm / │ ├─vg-lv_tmp 253:1 0 1.5G 0 lvm /tmp │ ├─vg-lv_var 253:2 0 16.8G 0 lvm /var │ ├─vg-lv_log 253:3 0 8.6G 0 lvm /var/log │ ├─vg-lv_audit 253:4 0 1.5G 0 lvm /var/log/audit │ └─vg-lv_home 253:5 0 380M 0 lvm /home └─vda4 252:4 0 65M 0 part loop2 7:2 0 16G 0 loop ├─cinder--volumes-cinder--volumes--pool_tmeta 253:6 0 16M 0 lvm │ └─cinder--volumes-cinder--volumes--pool 253:8 0 15.2G 0 lvm └─cinder--volumes-cinder--volumes--pool_tdata 253:7 0 15.2G 0 lvm └─cinder--volumes-cinder--volumes--pool 253:8 0 15.2G 0 lvm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0448