Red Hat Bugzilla – Bug 1295898
vnc_proxy configuration settings not IPv6 compatible
Last modified: 2016-04-15 09:46:34 EDT
Description of problem:
The current processing of the nova.conf file results in invalid URLs when IPv6 IPs are used. For IPv6 URLs that contain port numbers, it is required that the IP addresses be inside of square brackets to properly differentiate IP addresses from port numbers. This is required because IPv6 addresses can be shortened if there are repeated zeroes, so it can be impossible to differentiate an IP address from an IP/Port combination.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy with IPv6 TripleO Heat templates
/etc/nova.conf novnc URL is in improper format when using IPv6:
The IP in the URL should appear in brackets:
vncproxy.pp will need to be modified. Today it uses the same hiera value for the values that require a raw IP as the ones that require a bracketed IP.
Proposed fix #1:
Today everything is based on the hieradata value of nova::vncproxy::host. We could modify the TripleO Heat templates to provide a new value in the hieradata, which is the host IP with brackets in the case of IPv6, or without brackets in the case of IPv4. This value might be called nova::vncproxy::host_uri.
This new value should be optional, and should override the value of the host if it exists, but only in the places where the URLs are written.
Proposed fix #2:
The puppet modules themselves can determine if the host IP is an IPv6 address, and write the URLs with brackets in the configuration file if so.
This above patches solves the problem in the puppet module.
[root@overcloud-controller-0 heat-admin]# grep novncproxy_base_url /etc/nova/nova.conf
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.