Bug 1034637

Summary:	PackStack prompt for installing Heat needs to be expanded.
Product:	Red Hat OpenStack	Reporter:	Bruce Reeler <breeler>
Component:	openstack-packstack	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED ERRATA	QA Contact:	Martin Magr <mmagr>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	aortega, derekh, hateya, mmagr, rlandman, yeylon
Target Milestone:	rc	Keywords:	OtherQA, Triaged
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-packstack-2013.2.1-0.14.dev919.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-20 00:39:05 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:

Description Bruce Reeler 2013-11-26 09:10:58 UTC

Description of problem:
PackStack prompt for installing Heat needs to be expanded.
Currently, PackStack prompts for installing services are for example:
"Should Packstack install OpenStack Object Storage service (Swift)"
however, prompt for installing Heat does not describe service, just says:
"Should Packstack install Heat"

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

How reproducible:
Running PackStack interactively and accepting defaults.

Steps to Reproduce:
1. # packstack
2. Accept defaults for installing each service.

Actual results:
Should Packstack install Heat [y|n] [n] :


Expected results:
Should Packstack install OpenStack Orchestration service (Heat) [y|n] [n] :

Comment 2 Alvaro Lopez Ortega 2013-11-26 17:37:50 UTC

It's fixed upstream, although it's still pending to be released in a new package.
https://review.openstack.org/#/c/56743

Comment 3 Scott Lewis 2013-12-09 15:30:47 UTC

Adding OtherQA for bugs in MODIFIED

Comment 5 Martin Magr 2013-12-12 16:37:20 UTC

Should Packstack install OpenStack Orchestration (Heat) [y|n]  [n] :

Comment 7 errata-xmlrpc 2013-12-20 00:39:05 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html