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

Bug 1299227

Summary:	Swift Ringbuilder errors when using IPv6 address
Product:	Red Hat OpenStack	Reporter:	Mike Burns <mburns>
Component:	openstack-tripleo-heat-templates	Assignee:	Marios Andreou <mandreou>
Status:	CLOSED ERRATA	QA Contact:	Mike Abrams <mabrams>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	8.0 (Liberty)	CC:	achernet, derekh, dsneddon, hbrock, jcoufal, jslagle, mandreou, mburns, mcornea, rhel-osp-director-maint, sgotliv, yeylon, zaitcev
Target Milestone:	ga	Keywords:	Triaged
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-0.8.11-1.el7ost	Doc Type:	Bug Fix
Doc Text:	Prior to this update, the swift_device and swift_proxy_memcache URIs used for the swift ringbuilder and the swift proxy memcache server respectively were not properly formatted for IPv6 addresses, lacking the expected '[]' delimiting the IPv6 address. As a consequence, when deploying with IPv6 enabled for the overcloud, the deploy failed with "Error: Parameter name failed on Ring_object_device ...". Now, when IPv6 is enabled, the IP addresses used as part of the swift_device and swift_proxy_memcache URIs are correctly delimited with '[]'. As a result, deploying with IPv6 no longer fails on incorrect formatting for swift_device or swift_proxy_memcache.	Story Points:	---
Clone Of:	1296701	Environment:
Last Closed:	2016-04-07 21:46:07 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:
Bug Depends On:	1296701
Bug Blocks:

Comment 6 errata-xmlrpc 2016-04-07 21:46:07 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://rhn.redhat.com/errata/RHEA-2016-0604.html