This backport adds the configuration option rbd_exclusive_cinder_pool, which defaults to True. This option improves statistics collection for large numbers of RBD volumes. This option should be set to False if your pool is not used exclusively by Cinder.
rbd_exclusive_cinder_pool should be enabled by default.
The backport described in https://bugzilla.redhat.com/show_bug.cgi?id=1560068 was completed successfully. This backport adds a configuration option, rbd_exclusive_cinder_pool, which if enabled improves statistics collection for large numbers of RBD volumes. Ideally this flag would be set to the ideal default value (True) in TripleO. However, in the meantime, it is a superior customer experience for the majority of customers if this configuration option is set in the project defaults, as is already the case in RHOS 11 and RHOS 12.
Updating Target Milestone to z3 for all Modified medium bugs
FYI Some inconsistency with fixed-in puddle date.
On my puddle 2018-10-30.1 > than the BuildID puddle 2018-10-22.4
I've still got a too early of a Cinder version
openstack-cinder-12.0.3-2.el7ost.noarch < openstack-cinder-12.0.3-4.el7ost
Trying a newer puddle 2018-11-01.1
Don't want this to slip by 13z3 release date.
Puddle 2018-11-01.1 still produces a premature
openstack-cinder-12.0.3-2.el7ost.noarch < fixed-in 12.0.3-4
Anything we can do to check this our, or just wait for newer puddle?
build ID: puddle=2018-10-22.4 is clearly wrong.
New puddle(2018-11-05.3) just landed, I'll redeploy and update once I have news.
On cinder.conf I confirm default vaule of true is set for this config option.
grep rbd_exclusive_cinder_pool /var/lib/config-data/puppet-generated/cinder/etc/cinder/cinder.conf
#rbd_exclusive_cinder_pool = true
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.