Description of problem: It's not possible to deploy a NetApp back end for Cinder in OSP-11 (Ocata). The hieradata (/etc/puppet/hieradata/cinder_netapp_data.json) is malformed, and none of the relevant settings appear in the driver portion of /etc/cinder/cinder.conf. Other Cinder back end drivers (Dell EMC Ps, SC and ScaleIO) have been converted for composable roles, but the NetApp driver has not been converted. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy an overcloud using an environment file that enables the NetApp Cinder back end 2. 3. Actual results: The back end is not enabled (valid settings do not appear in the back end driver section of /etc/cinder/cinder.conf Expected results: Additional info:
Good catch here. I don't think we have anything solid in place to catch this for partners that have added OOO deployment for at least Cinder. Is there any way to check if there are other similar issues to catch now in the OSP11/ocata?
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Paul, no we currently don't have upstream CI jobs that test netapp and other vendors integration in TripleO.
I think I can help out with this.
Merged on master, proposed backport: https://review.openstack.org/#/c/456264/
Backport to stable/ocata is stuck due to upstream bug that is blocking CI (https://bugs.launchpad.net/tripleo/+bug/1682001) When it lands lands in stable/ocata, will it need to be explicitly backported to OSP-11 or will/can it be picked up by the next rebase?
Upstream patch just merged. Moving to POST.
Note to QE: Please be sure to focus on the OSP-10 to OSP-11 upgrade path. See my note to the Doc team for details. Note to Doc team: Section 3.4.2 of the upgrade document [1] covers situations where the customer is deploying modified overcloud templates, and section 3 of the NetApp Block Storage Back End Guide [2] directs the operator to do just that. In order to successfully upgrade OSP-10 to OSP-11 with a NetApp back end, the customer will need to sync their modified version of environments/cinder-netapp-config.yaml with the new version in OSP-11. Specifically, they need to _replace_ this line (applicable in OSP-10): OS::TripleO::ControllerExtraConfigPre: ../puppet/extraconfig/pre_deploy/controller/cinder-netapp.yaml With this (applicable in OSP-11): OS::TripleO::Services::CinderBackendNetApp: ../puppet/services/cinder-backend-netapp.yaml The guide [2] explains the path to the .yaml file needs to be updated from a relative path ("../puppet") to an absolute path. This applies to the new cinder-backend-netapp.yaml file in OSP-11. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/upgrading_red_hat_openstack_platform/ [2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/netapp_block_storage_back_end_guide/index
The doc notes I outline in comment #9 are being incorporated into the overall upgrade documentation.
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. https://access.redhat.com/errata/RHEA-2017:1245