Using composable roles for deploying Dell SC and PS Block Storage backend caused errors. The backends could only be deploying using 'cinder::config::cinder_config' hiera data.
With this update, the composable role support for deploying the Dell SC and PS Block Storage backends is updated. As a result, they can be now deployed using composable roles.
Description of problem:
When TripleO support for deploying Dell SC and PS Cinder backends was upgraded to support composable roles, a couple of pieces were missed when backported to OSP-10.  is the patch that fixed things on ocata, and a variant of the patch will be required for OSP-10.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Deploy overcloud using the cinder-dellsc-config.yaml or cinder-dellps-config.yaml environment files.
The corresponding Dell SC or PS Cinder backend is not deployed. The deployment will appear to succeed, but the backend settings are completely missing in the controller's /etc/cinder/cinder.conf.
The Dell SC or PS backend settings are present in cinder.conf
The puppet/services/cinder-backend-dellsc.yaml and cinder-backend-dellps.yaml heat template version is wrong. Both files reference Ocata, and need to reference Newton to work in OSP-10.
*** Bug 1553229 has been marked as a duplicate of this bug. ***
Any update on this issue. Hitting this with my customer in their labs after updating undercloud. Is there an rpm avail?
This is targeted for the upcoming 10z8.
Verified in installation
installed RPM package
RHOS10 installation been deployed using the following heat templates
After installation the cinder.conf was checked and verified that
[tripleo_dellsc] or [tripleo_dellps] sections were added to the configuration file.
No tested been preformed with Dell storage as backend due the lack of hardware
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.
Nothing to automate/test as I don't have access to such storage systems.
Plus specific to these backends only.