Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1635690

Summary:	ControllerStorageNFS role has the wrong name
Product:	Red Hat OpenStack	Reporter:	Tom Barron <tbarron>
Component:	openstack-tripleo-heat-templates	Assignee:	Tom Barron <tbarron>
Status:	CLOSED ERRATA	QA Contact:	Dustin Schoenbrun <dschoenb>
Severity:	low	Docs Contact:
Priority:	low
Version:	13.0 (Queens)	CC:	lmarsh, mburns
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.0.4-35.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-13 22:29:59 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 Tom Barron 2018-10-03 13:38:57 UTC

Description of problem:  The ControllerStorageNFS role defined at openstack-tripleo-heat-templates/roles/ControllerStorageNfs.yaml has 'name: Controller' rather than 'name: ControllerStorageNfs'.  Although deployments in general succeed because the role is quite close to the base Controller role, InfraRed (rightly) uses this field in its composable role code and breaks.


Version-Release number of selected component (if applicable):


How reproducible:

Run an InfraRed deployment 


Actual results: InfraRed deployment fails


Expected results:  IR deployment will succeed, or at least not fail because of this issue.


Additional info:

Comment 1 Shelley Dunne 2018-10-12 15:36:29 UTC

Updating Target Milestone to z3 for all Modified low bugs

Comment 9 errata-xmlrpc 2018-11-13 22:29:59 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:3587