Description of problem: When using IPv6 as public endpoint on the undercloud, deployment fails on swift_ringbuilder Version-Release number of selected component (if applicable): Puddle: 2019-04-10.1 How reproducible: 100% Steps to Reproduce: 1. Set undercloud public ip to IPv6 address 2. Update public endpoints to IPv6 3. Start deployment with pre-deployed servers Actual results: "Error: /Stage[main]/Tripleo::Profile::Base::Swift::Ringbuilder/Exec[upload_swift_ring_tarball]: Failed to call refresh: curl --insecure --silent --retry 3 -X PUT 'https://[2001:db8::b2]:13808/v1/AUTH_81810eb37b2247ab8c337296b6c666d7/overcloud-swift-rings/swift-rings.tar.gz?temp_url_sig=436b0190f2ed17c0adc0ba2d9f04c6631bf9305f&temp_url_expires=1555419574' --data-binary @/tmp/swift-rings.tar.gz returned 3 instead of one of [0]", "Error: /Stage[main]/Tripleo::Profile::Base::Swift::Ringbuilder/Exec[upload_swift_ring_tarball]: curl --insecure --silent --retry 3 -X PUT 'https://[2001:db8::b2]:13808/v1/AUTH_81810eb37b2247ab8c337296b6c666d7/overcloud-swift-rings/swift-rings.tar.gz?temp_url_sig=436b0190f2ed17c0adc0ba2d9f04c6631bf9305f&temp_url_expires=1555419574' --data-binary @/tmp/swift-rings.tar.gz returned 3 instead of one of [0]", Expected results: Deployment succeed Additional info: Seems like the upstream has a fix for rocky, we need a backport to OSP13
Verified on puddle 2019-06-28.1 [stack@undercloud-0 ~]$ rpm -q puppet-tripleo puppet-tripleo-8.4.1-14.el7ost.noarch
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://access.redhat.com/errata/RHBA-2019:1738