The TripleO environment files used for deploying Cinder's Netapp backend have been updated in this release to allow successful deployment of a Cinder Netapp backend.
Prior to this update, obsolete data caused the overcloud deployment to fail.
Description of problem:
RHOSP12 fails to deploy with following error:
ERROR: Property error: : resources.Controller<nested_stack>.resources.0<https://10.7.40.249:13808/v1/AUTH_ed4febd9c93c4178ac5386b97222c862/overcloud/puppet/controller-role.yaml>.resources.ControllerExtraConfigPre.properties: : Unknown Property server\"
Version-Release number of selected component (if applicable):
Looks similar to this 2 bugs: 1439895 (Ocata) and 1567893 (Queens).
The reference to ControllerExtraConfigPre makes me suspect the problem is the deployment command is trying to deploy the Netapp backend using the old non-composable role technique, which has been deprecated.
I looked through the customer case and see a lot of template files have been made available, but I need to see the full deployment command.
Siggy, please ask the customer to add the deployment command to the case.
Latest data in the case confirms my suspicion. The cinder-netapp-config.yaml
file used in the deployment is based on
tht/environments/storage/cinder-netapp-config.yaml. That file is one of the
sample environment generator files that has not been maintained, and the
problem is it's referencing ControllerExtraConfigPre which was made obsolete
when the Netapp backend was migrated to a composable service.
Unfortunately, the presence of these stale environment files has caused other
people some trouble, and this needs to be clean up upstream (see ).
So, for OSP-12 (and onward), use tht/enviornments/cinder-netapp-config.yaml
(not the one in the "storage" subdirectory) as the basis for deploying the
Netapp backend. Note that it references the backend's composable service
Siggy, can you please check again with the info from Alan in https://bugzilla.redhat.com/show_bug.cgi?id=1585362#c3 ? Thanks!
Patch merged on upstream master, starting upstream backports.
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.