Description of problem: When using IPv6 versions of the isolated network TripleO Heat templates, the deployment fails due to a Swift error: Version-Release number of selected component (if applicable): OSP 8 beta openstack-swift.noarch 2.5.1-dev134.el7.centos openstack-swift-account.noarch 2.5.1-dev134.el7.centos openstack-swift-container.noarch 2.5.1-dev134.el7.centos openstack-swift-object.noarch 2.5.1-dev134.el7.centos openstack-swift-plugin-swift3.noarch 1.7-4.el7 openstack-swift-proxy.noarch 2.5.1-dev134.el7.centos How reproducible: 100% Steps to Reproduce: 1. Deploy using IPv6 templates (https://etherpad.openstack.org/p/tripleo-ipv6-support) 2. 3. Actual results: Error: Parameter name failed on Ring_object_device[fd00:fd00:fd00:4000:f816:3eff:fe60:33a0:6000/d1]: Validate method failed for class name: the scheme http does not accept registry part: fd00:fd00:fd00:4000:f816:3eff:fe60:33a0:6000 (or bad hostname?) at /var/lib/heat-config/heat-config-puppet/ab0769c5-06fe-4ee9-acc9-c29dccbec687.pp:42\nWrapped exception:\nValidate method failed for class name: the scheme http does not accept registry part: fd00:fd00:fd00:4000:f816:3eff:fe60:33a0:6000 (or bad hostname?) Expected results: The Swift ringbuilder should build the rings. Additional info: I can't figure out for the life of me where the URL for the Swift ringbuilder is stored. Maybe it isn't, and when Puppet runs it just reads the hieradata, but there I couldn't find anything stored anywhere on the controller which contains a URL with fd00:fd00:fd00:4000:f816:3eff:fe60:33a0:6000. I do see this in /etc/puppet/hieradata/swift_devices_and_proxy.yaml: swift::proxy::cache::memcache_servers: ['fd00:fd00:fd00:2000:f816:3eff:fec4:ed44:11211'] tripleo::ringbuilder::devices: r1z1-fd00:fd00:fd00:4000:f816:3eff:fe60:33a0:%PORT%/d1, If the above is part of a URL, then the IP address should have a bracket around it, separating it from the port number. If it is part of a URL, though, I can't figure out what the r1z1- prefix is about. Please help me figure out how to make Swift ringbuilder work with IPv6 IP addresses.
*** This bug has been marked as a duplicate of bug 1296701 ***