Description of problem: When trying to set public endpoints to serve over IPv6, stackrc creation fails due to missing logic for parsing IPv6 address for OS_AUTH_URL Version-Release number of selected component (if applicable): OSP13, puddle 2019-03-18.1 How reproducible: 100% Steps to Reproduce: 1. Add undercloud_public_host = <IPv6 address> 2. run openstack undercloud install Actual results: 2019-04-02 12:04:04,679 INFO: Failed to discover available identity versions when contacting https://2001:db8::b2:13000/. Attempting to parse version from URL. 2019-04-02 12:04:04,680 INFO: Could not determine a suitable URL for the plugin 2019-04-02 12:04:04,724 INFO: + openstack quota set --cores -1 --instances -1 --ram -1 2019-04-02 12:04:05,450 INFO: Failed to discover available identity versions when contacting https://2001:db8::b2:13000/. Attempting to parse version from URL. 2019-04-02 12:04:05,450 INFO: Could not determine a suitable URL for the plugin 2019-04-02 12:04:05,498 INFO: [2019-04-02 12:04:05,498] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/post-configure.d']' returned non-zero exit status 1] 2019-04-02 12:04:05,498 INFO: 2019-04-02 12:04:05,498 INFO: [2019-04-02 12:04:05,498] (os-refresh-config) [ERROR] Aborting... 2019-04-02 12:04:05,507 DEBUG: An exception occurred Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 2389, in install _run_orc(instack_env) File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1604, in _run_orc _run_live_command(args, instack_env, 'os-refresh-config') File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 673, in _run_live_command raise RuntimeError('%s failed. See log for details.' % name) RuntimeError: os-refresh-config failed. See log for details. 2019-04-02 12:04:05,508 ERROR: ############################################################################# Undercloud install failed. Reason: os-refresh-config failed. See log for details. See the previous output for details about what went wrong. The full install log can be found at /home/stack/.instack/install-undercloud.log. ############################################################################# Expected results: Undercloud install complete Additional info: The issue is cause by link string OS_AUTH_URL=https://{{public_host}}:13000/ (for HTTPS) or OS_AUTH_URL=https://{{public_host}}:5000/ (for HTTP) in /usr/share/instack-undercloud/undercloud-install/os-apply-config/root/stackrc. Manually modifying these url to include [] for IPv6 address fixes the issue.
Looks like we need to add a public-host-wrapped env setting. However note that IPv6 on the provisioning network isn't supported in OSP-13. There are some fixes for it but its not planned until OSP-16 - https://bugzilla.redhat.com/show_bug.cgi?id=1459187. Its likely that you'll encounter other problems once you got by this in OSP-13. Note that OSP-16 doesn't use instack-undercloud so this fix probably isn't needed there.
Alex - can this be retargeted to OSP-16 to match support for IPv6 on provisioning network - https://bugzilla.redhat.com/show_bug.cgi?id=1459187?
Thanks Alex. OK, its different if we don't need IPv6 provisioning network. With this fix does it complete? Agreed its an easy fix and we can get it in.
(In reply to Bob Fournier from comment #7) > Thanks Alex. OK, its different if we don't need IPv6 provisioning network. > With this fix does it complete? Agreed its an easy fix and we can get it in. There are other pending BZs that prevents getting a smooth experience, but with all BZs worked around it does get deployed, yes.
Hi Alex - if you are testing IPv6 with OSP-13 it would be great if you can also test one. Thanks.
Verified on puddle 2019-06-28.1 [stack@undercloud-0 ~]$ rpm -q instack-undercloud instack-undercloud-8.4.7-10.el7ost.noarch stackrc file generated properly and works as expected.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days