Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1801909

Summary:	ironic_inspector healthcheck is failing when using IPv6 provisioning address
Product:	Red Hat OpenStack	Reporter:	Bob Fournier <bfournie>
Component:	openstack-tripleo-common	Assignee:	Bob Fournier <bfournie>
Status:	CLOSED ERRATA	QA Contact:	Alistair Tonner <atonner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	mburns, slinaber
Target Milestone:	z2	Keywords:	Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-11.3.3-0.20200302055419.89a7df0.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-14 12:15:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bob Fournier 2020-02-11 22:08:17 UTC

Description of problem:

When using an IPv6 provisioning address the ironic_inspector healthcheck if failing because the IPv6 address is not bracketed.

Feb 11 10:06:38 hardprov-dl360-g9-01 podman[66358]: curl: (3) IPv6 numerical address used in URL without brackets
Feb 11 10:06:38 hardprov-dl360-g9-01 podman[66358]: Error: non zero exit code: 1: OCI runtime error
Feb 11 10:06:38 hardprov-dl360-g9-01 systemd[1]: tripleo_ironic_inspector_healthcheck.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 10:06:38 hardprov-dl360-g9-01 systemd[1]: tripleo_ironic_inspector_healthcheck.service: Failed with result 'exit-code'.

Comment 1 Bob Fournier 2020-04-15 18:04:30 UTC

Verified that this is no longer failing because of the IPv6 brackets.

Comment 4 errata-xmlrpc 2020-05-14 12:15:31 UTC

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-2020:2114