Bug 1581070

Summary:	cinder-netapp-config.yaml maps to non-existent resource file
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED DUPLICATE	QA Contact:	Gurenko Alex <agurenko>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	abishop, aschultz, mburns
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-23 14:12:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Udi Kalifon 2018-05-22 06:30:18 UTC

Description of problem:
In environments/storage/cinder-netapp-config.yaml you find this resource mapping:

resource_registry:
  OS::TripleO::ControllerExtraConfigPre: ../../puppet/extraconfig/pre_deploy/controller/cinder-netapp.yaml

This file does not exist. Adding environments/storage/cinder-netapp-config.yaml to the plan breaks the GUI and would fail the deployment. This is the environment file for "Cinder NetApp backend".


Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-8.0.2-22.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. In the GUI, add the environment "Cinder NetApp backend"
2. Switch to the "Properties" tab


Actual results:
Deployment parameters could not be loaded
404 Client Error: Not Found for url: https://192.168.24.2:13808/v1/AUTH_3f103b9322854540baeafbc9d73cc1bf/overcloud/puppet/extraconfig/pre_deploy/controller/cinder-netapp.yaml

Comment 1 Udi Kalifon 2018-05-22 06:58:23 UTC

Also related to https://bugzilla.redhat.com/show_bug.cgi?id=1567893 - see comment #4. There might already be a fix.

Comment 2 Alan Bishop 2018-05-23 14:12:16 UTC


*** This bug has been marked as a duplicate of bug 1567893 ***