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

Bug 908900

Summary:	CONFIG_SWIFT_STORAGE_HOSTS format handling is badly parsed
Product:	Red Hat OpenStack	Reporter:	Jaroslav Henner <jhenner>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Henner <jhenner>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.0 (Folsom)	CC:	aortega, derekh, 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:26 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 20:08:56 UTC

Description of problem:

CONFIG_SWIFT_STORAGE_HOSTS is described as:
# A comma separated list of IP addresses on which to install the
# Swift Storage services, each entry should take the format
# <ipaddress>[/dev], for example 127.0.0.1/vdb will install /dev/vdb
# on 127.0.0.1 as a swift storage device, if /dev is omitted Packstack
# will create a loopback device for a test setup

Which means I cannot use any file outside of /dev.

ALso, anything behind the second slash seems to be ignored, so
CONFIG_SWIFT_STORAGE_HOSTS=1.2.3.2/vg_system/swift

will result in this in fstab:
/dev/vg_system	/srv/node/device2	ext4	noatime,nodiratime,nobarrier,user_xattr	0	0


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


How reproducible:
1/1


Steps to Reproduce:
1. Follow the Description.
  

Actual results:


Expected results:
The config
CONFIG_SWIFT_STORAGE_HOSTS=1.2.3.2/dev/vg_system/swift

causes following in fstab
/dev/vg_system/swift	/srv/node/device2	ext4	noatime,nodiratime,nobarrier,user_xattr	0	0


Additional info:

Comment 2 Jaroslav Henner 2013-02-07 20:15:57 UTC

See also BZ#908846

Comment 3 Derek Higgins 2013-02-21 14:05:36 UTC

Fix for the multiple slash bug now posted upstream
https://review.openstack.org/22548

I'm not sure using devices outside of /dev would be a case we want to support but if you think it should can you open a different ticket as a RFE as this behavior was by design.

Comment 4 Derek Higgins 2013-02-21 15:59:38 UTC

Wrong link, Martin Magr beat me to it
https://review.openstack.org/#/c/22296/

Comment 6 Jaroslav Henner 2013-03-12 12:20:11 UTC

Well done.

CONFIG_SWIFT_STORAGE_HOSTS=10.34.69.157/vg_test/lv1, 10.34.69.157/vg_test/lv2

resulted in 

/dev/mapper/vg_test-lv2 on /srv/node/device2 type ext4 (rw,noatime,nodiratime,nobarrier,user_xattr)
/dev/mapper/vg_test-lv1 on /srv/node/device1 type ext4 (rw,noatime,nodiratime,nobarrier,user_xattr)

Comment 9 errata-xmlrpc 2013-03-21 18:23:26 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