Bug 2006556

Verified on:
openstack-cinder-15.6.1-2.20220112174913.c093eda.el8ost.noarch

Bump up default volume backup count
openstack quota set --backups 1010 admin
openstack quota set --backup-gigabytes 1010 admin

Created an empty volume to backup:
(overcloud) [stack@undercloud-0 ~]$ cinder list
+--------------------------------------+-----------+------+------+-------------+----------+-------------+
| ID                                   | Status    | Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+------+------+-------------+----------+-------------+
| f8e53acb-3866-4a86-a6a5-4050f19564cf | available | volA | 1    | tripleo     | false    |             |
+--------------------------------------+-----------+------+------+-------------+----------+-------------+


Then I created an empty volume, using a simple bash for loop to created 1005 backups

#!/usr/bin/env bash
. overcloudrc

for i in {1..1005} 
 do
   cinder backup-create f8e53acb-3866-4a86-a6a5-4050f19564cf --name backup$i --description 'Backup of vol'
   sleep 40 
 done


Resulting backup list columns are fully populated as expected even after the 1000th line, good to verify.

(overcloud) [stack@undercloud-0 ~]$ openstack volume backup list | more
+--------------------------------------+------------+---------------+-----------+------+
| ID                                   | Name       | Description   | Status    | Size |
+--------------------------------------+------------+---------------+-----------+------+
| 359c005a-c19d-4f74-a348-d27861e55bd9 | backup1005 | Backup of vol | available |    1 |
| 18fb8ead-5524-442f-acfa-43f0187d5268 | backup1004 | Backup of vol | available |    1 |
| e1a6fb57-d700-4ced-a201-f21bfac66fc9 | backup1003 | Backup of vol | available |    1 |
| 2967c53a-c2aa-4636-a95a-0440608fd240 | backup1002 | Backup of vol | available |    1 |
| c5e0c934-6950-457e-9eef-469b458d843d | backup1001 | Backup of vol | available |    1 | --> missing data before now shows up.
| bb360938-925a-4f91-801c-5b8fbf25c7e8 | backup1000 | Backup of vol | available |    1 |  
| 561e4ccb-efda-4084-8a69-4618a5ae11ca | backup999  | Backup of vol | available |    1 |
| 9d43299b-a93d-46c2-a306-634ef19e696d | backup999  | Backup of vol | available |    1 |
| 129bd060-9e12-442e-86e1-a052e3059d7e | backup998  | Backup of vol | available |    1 
...
| 3d3ae79e-1b6a-4c6b-91d0-1f4ea9892642 | backup4    | Backup of vol | available |    1 |
| 7b8a614a-3951-44cb-9380-74cd120fb5d8 | backup3    | Backup of vol | available |    1 |
| a79c41a7-45e5-4aad-a0fd-3154ff4243ec | backup2    | Backup of vol | available |    1 |
| dcd78b88-5227-4068-ae39-08949e6a5481 | backup1    | Backup of vol | available |    1 |
+--------------------------------------+------------+---------------+-----------+------+

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 (Release of components for Red Hat OpenStack Platform 16.2.2), 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-2022:1001