Bug 1612342 - NetApp Cinder back end does not deploy in RHOSP13 (Queens)
Summary: NetApp Cinder back end does not deploy in RHOSP13 (Queens)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: z2
: 13.0 (Queens)
Assignee: Alan Bishop
QA Contact: Tzach Shefi
Kim Nylander
URL:
Whiteboard:
Depends On:
Blocks: 1585362
TreeView+ depends on / blocked
 
Reported: 2018-08-03 17:22 UTC by Alan Bishop
Modified: 2021-12-10 17:03 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.0.4-10.el7ost
Doc Type: Bug Fix
Doc Text:
The TripleO environment files used for deploying Cinder's Netapp backend were out of date and contained incorrect data. This resulted in failed overcloud deployment. The Cinder Netapp environment files have been updated and are now correct. You can now deploy an overcloud with a Cinder Netapp backend.
Clone Of: 1585362
Environment:
Last Closed: 2018-08-29 16:39:25 UTC
Target Upstream Version:
Embargoed:
tshefi: automate_bug+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1779397 0 None None None 2018-08-03 17:22:58 UTC
OpenStack gerrit 579237 0 'None' MERGED Clean up env files for Cinder's Netapp backend 2021-02-08 23:58:16 UTC
Red Hat Issue Tracker OSP-11532 0 None None None 2021-12-10 17:03:37 UTC
Red Hat Product Errata RHBA-2018:2574 0 None None None 2018-08-29 16:40:05 UTC

Description Alan Bishop 2018-08-03 17:22:58 UTC
+++ This bug was initially created as a clone of Bug #1585362 +++

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):
openstack-tripleo-heat-templates-7.0.3-22.el7ost.noarch

How reproducible:
100%
Looks similar to this 2 bugs: 1439895 (Ocata) and 1567893 (Queens).

--- Additional comment from Alan Bishop on 2018-06-13 08:35:45 EDT ---

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.

--- Additional comment from Alan Bishop on 2018-06-18 10:00:08 EDT ---

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 [1]).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1567893#c5

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
(OS::TripleO::Services::CinderBackendNetApp)

Comment 5 errata-xmlrpc 2018-08-29 16:39:25 UTC
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:2574


Note You need to log in before you can comment on or make changes to this bug.