Control plane backup fails

Issue

• While taking backup of overcloud/control plane nodes, execution fails at "TASK [backup-and-restore : Create the node backup]" with below mentioned errors:

TASK [backup-and-restore : Create the node backup] *****************************************************************************************************
fatal: [controller-0]: FAILED! => {"changed": true, "cmd": ["rear", "-d", "-v", "mkbackup"], "delta": "0:00:11.589767", "end": "2022-08-30 14:10:57.713378", "msg": "non-zero return code", "rc": -15, "start": "2022-08-30 14:10:46.123611", "stderr": "LVM no 'lvmvol /dev/cinder-volumes' for 'lvmdev /dev/cinder-volumes'
ERROR:
====================
BUG in /usr/share/rear/layout/save/default/950_verify_disklayout_file.sh line 254:
'Entries in /var/lib/rear/layout/disklayout.conf are broken ('rear recover' would fail)'
--------------------
Please report this issue at https://github.com/rear/rear/issues
and include the relevant parts from /var/log/rear/rear-controller-0.log
preferably with full debug information via 'rear -D mkbackup'
====================
Some latest log messages since the last called script 950_verify_disklayout_file.sh:
  2022-08-30 14:10:54.382216906 Verifying that the 'part' entries for /dev/sda in /var/lib/rear/layout/disklayout.conf are correct
  1048576
  1048576
  1200208027136
  2097152
  2022-08-30 14:10:54.384666556 Verifying that the 'part' entries for /dev/sda in /var/lib/rear/layout/disklayout.conf specify consecutive partitions
  2022-08-30 14:10:54.388488648 Verifying that the 'lvm...' entries in /var/lib/rear/layout/disklayout.conf are correct
  2022-08-30 14:10:54.394896536 LVM no 'lvmvol /dev/cinder-volumes' for 'lvmdev /dev/cinder-volumes'
Aborting due to an error, check /var/log/rear/rear-controller-0.log for details", "stderr_lines": ["LVM no 'lvmvol /dev/cinder-volumes' for 'lvmdev /dev/cinder-volumes'", "ERROR: ", "====================", "BUG in /usr/share/rear/layout/save/default/950_verify_disklayout_file.sh line 254:", "'Entries in /var/lib/rear/layout/disklayout.conf are broken ('rear recover' would fail)'", "--------------------", "Please report this issue at https://github.com/rear/rear/issues", "and include the relevant parts from /var/log/rear/rear-controller-0.log", "preferably with full debug information via 'rear -D mkbackup'", "====================", "Some latest log messages since the last called script 950_verify_disklayout_file.sh:", "  2022-08-30 14:10:54.382216906 Verifying that the 'part' entries for /dev/sda in /var/lib/rear/layout/disklayout.conf are correct", "  1048576", "  1048576", "  1200208027136", "  2097152", "  2022-08-30 14:10:54.384666556 Verifying that the 'part' entries for /dev/sda in /var/lib/rear/layout/disklayout.conf specify consecutive partitions", "  2022-08-30 14:10:54.388488648 Verifying that the 'lvm...' entries in /var/lib/rear/layout/disklayout.conf are correct", "  2022-08-30 14:10:54.394896536 LVM no 'lvmvol /dev/cinder-volumes' for 'lvmdev /dev/cinder-volumes'", "Aborting due to an error, check /var/log/rear/rear-controller-0.log for details"], "stdout": "Relax-and-Recover 2.6 / 2020-06-17
Running rear mkbackup (PID 497639)
Using log file: /var/log/rear/rear-controller-0.log
Running workflow mkbackup on the normal/original system
Using backup archive '/tmp/rear.zHJwLe5ZJVpJmH3/outputfs/controller-0/controller-0-202208301410.tar.gz'
Using autodetected kernel '/boot/vmlinuz-4.18.0-305.40.2.el8_4.x86_64' as kernel in the recovery system
Creating disk layout
Overwriting existing disk layout file /var/lib/rear/layout/disklayout.conf
Using guessed bootloader 'GRUB' (found in first bytes on /dev/sda)
Verifying that the entries in /var/lib/rear/layout/disklayout.conf are correct ...
Exiting rear mkbackup (PID 497639) and its descendant processes ...
Running exit tasks
You should also rm -Rf --one-file-system /tmp/rear.zHJwLe5ZJVpJmH3", "stdout_lines": ["Relax-and-Recover 2.6 / 2020-06-17", "Running rear mkbackup (PID 497639)", "Using log file: /var/log/rear/rear-controller-0.log", "Running workflow mkbackup on the normal/original system", "Using backup archive '/tmp/rear.zHJwLe5ZJVpJmH3/outputfs/controller-0/controller-0-202208301410.tar.gz'", "Using autodetected kernel '/boot/vmlinuz-4.18.0-305.40.2.el8_4.x86_64' as kernel in the recovery system", "Creating disk layout", "Overwriting existing disk layout file /var/lib/rear/layout/disklayout.conf", "Using guessed bootloader 'GRUB' (found in first bytes on /dev/sda)", "Verifying that the entries in /var/lib/rear/layout/disklayout.conf are correct ...", "Exiting rear mkbackup (PID 497639) and its descendant processes ...", "Running exit tasks", "You should also rm -Rf --one-file-system /tmp/rear.zHJwLe5ZJVpJmH3"]}

• Executed Command: openstack overcloud backup --inventory /home/stack/tripleo-inventory.yaml