Comment 4 for bug 1859641

Revision history for this message
Joseph Richard (josephrichard) wrote :

That helm chart issue was a separate issue affecting an ipv6 lab, and has been fixed.

mariadb is correctly binding to 0.0.0.0 [1] even in ipv6 configs. This can be overwritten by a change in the mariadb helm plugin [2] to override this in an ipv6 environment.

There is also a bug in openstack-helm-infra [3] that it will not enclose ipv6 addresses in square brackets resulting in them being unable to be parsed.

[1] https://github.com/openstack/openstack-helm-infra/blob/master/mariadb/values.yaml#L322
[2] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/helm/mariadb.py
[3] https://github.com/openstack/openstack-helm-infra/blame/master/mariadb/files/nginx.tmpl#L476