Red Hat Bugzilla – Bug 908900
CONFIG_SWIFT_STORAGE_HOSTS format handling is badly parsed
Last modified: 2013-03-21 14:23:26 EDT
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:
See also BZ#908846
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.
Wrong link, Martin Magr beat me to it https://review.openstack.org/#/c/22296/
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)
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