+++ This bug was initially created as a clone of Bug #1599759 +++ Description of problem: When using CinderNetappBackendName in the cinder-netapp-config template, the name provided is not reflected in the deployed environment. This is because THT/puppet/services/cinder-backend-netapp.yaml passes CinderNetappBackendName to cinder::backend::netapp::title instead of the correct parameter cinder::backend::netapp::volume_backend_name Version-Release number of selected component (if applicable): 12 How reproducible: Everytime Steps to Reproduce: 1. Include name other than tripleo_netapp in environment files via CinderNetappBackendName param. Actual results: Backend name will still be tripleo_netapp Expected results: Provided backend name is utilized in cinder.conf Additional info: Upstream Bug: https://bugs.launchpad.net/tripleo/+bug/1779500
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/RHBA-2018:3587
Verified (a moment too late) on: openstack-tripleo-heat-templates-8.0.7-4.el7ost.noarch 1. I'd had a working OC with default name of tripleo_netapp 2. Changed name to triple_dataontap on strorage yaml 3. Reran overcloud_deploy.sh The update changed netapp's backend name as expected. | cinder-volume | hostgroup@tripleo_dataontap | nova | enabled | up | 2018-11-13T22:30:16.000000 | - | | cinder-volume | hostgroup@tripleo_iscsi | nova | enabled | up | 2018-11-13T22:30:23.000000 | - | | cinder-volume | hostgroup@tripleo_netapp | nova | enabled | down