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

Bug 908846

Summary:	answer file options values doesn't allow white-spaces
Product:	Red Hat OpenStack	Reporter:	Jaroslav Henner <jhenner>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED ERRATA	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.0 (Folsom)	CC:	aortega, derekh, mmagr, ykaul
Target Milestone:	snapshot4	Keywords:	Triaged
Target Release:	2.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-packstack-2012.2.3-0.1.dev454	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-21 18:23:22 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 Jaroslav Henner 2013-02-07 16:38:14 UTC

Description of problem:
When having 
CONFIG_SWIFT_STORAGE_HOSTS=11.22.33.2/sda2, 11.22.33.3/sda2
I got:
ERROR:root:ssh: Could not resolve hostname  11.22.33.3: Name or service not known

After changing it to
CONFIG_SWIFT_STORAGE_HOSTS=11.22.33.2/sda2,11.22.33.3/sda2
it seems working fine. 


Version-Release number of selected component (if applicable):
openstack-packstack-2012.2.2-0.8.dev346.el6ost.noarch

How reproducible:
3/3


Steps to Reproduce:
1. Follow the Description
  
Actual results:
fail

Expected results:
success

I suggest separating the values by space or stripping the white-spaces or something similar, as it is seems to me more intuitive to ignore the WS.


Additional info:
It is nice weather out there.

Comment 3 Nir Magnezi 2013-03-05 12:57:21 UTC

Verified NVR: openstack-packstack-2012.2.3-0.1.dev454.el6ost.noarch

Tested OK with packstack, Using answers file with CONFIG_SWIFT_STORAGE_HOSTS with white spaces.
both Storage hosts were installed with no errors.

Comment 6 errata-xmlrpc 2013-03-21 18:23:22 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/RHSA-2013-0671.html