Bug 2010698

Summary:	[BM] [IPI] [Dual Stack] Installer must ensure ipv6 short forms too if clusterprovisioning IP is specified as ipv6 address
Product:	OpenShift Container Platform	Reporter:	Jatan Malde <jmalde>
Component:	Bare Metal Hardware Provisioning	Assignee:	Bob Fournier <bfournie>
Bare Metal Hardware Provisioning sub component:	ironic	QA Contact:	Adina Wolff <awolff>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	asadawar, augol, beth.white, bfournie, dmoessne, lshilin, omichael, shardy, tmulquee, vvoronko
Version:	4.8	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.10.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The user entered a long form IPv6 address in the installation configuration file, e.g. 2001:0db8:85a3:0000:0000:8a2e:0370:7334 Consequence: The installation failed as Ironic could not find an interface matching this IP address. Fix: The fix was to convert the IPv6 address to short form, e.g. 2001:db8:85a3::8a2e:370:7334 Result: The installation was successful.	Story Points:	---
Clone Of:
Clones:	2023748 (view as bug list)		Environment:
Last Closed:	2022-03-10 16:17:15 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:
Bug Depends On:
Bug Blocks:	2023748

Comment 2 Steven Hardy 2021-10-05 12:54:49 UTC

> where the provisioning network is on ipv6 and ipv4

To clarify, the provisioning network does not support dual stack - it must be either ipv4 or ipv6.

> https://github.com/openshift/ironic-image/blob/master/scripts/ironic-common.sh#L27

Yes it does appear that this assumes the short form ipv6 address, but if you use the short form in the install-config everything works OK?

Comment 3 Niket Chavan 2021-10-05 14:02:53 UTC

> Yes it does appear that this assumes the short form ipv6 address, but if you
> use the short form in the install-config everything works OK?

My colleague @Jatan was on remote session when he encountered this issue, as per remote session activity notes;
-------
- We scaled down the cluster-baremetal-operator and changed the PROVISIONING_IP environment variable in all the containers under metal3 pod deployment.  <--- changed to short form
- The new metal3 pod started the ironic agent properly and we could see all the ironic services up and running.
-------

We have suggested customer to change the clusterprovisioningip in the install-config to a short form value of IPv6 and then check if the installation goes through or not, customer is yet to update on that. 

-Niket

Comment 8 Adina Wolff 2021-10-14 18:18:11 UTC

Verified on version 4.10.0-0.nightly-2021-10-14-061552


install-config.yaml:
...
    provisioningNetworkCIDR: fd00:1101:0:1::/64
    bootstrapProvisioningIP: fd00:1101:0000:0001:0000:0000:0000:0002
    clusterProvisioningIP: fd00:1101:0000:0001:0000:0000:0000:0003
...

Installation completes successfully.

Comment 10 Tony Mulqueen 2022-01-11 11:26:03 UTC

@bfournier Bob, can we please have Doc Text to assist in developing a Release Notes entry for this bug?
Thanks!

Comment 11 Bob Fournier 2022-01-11 12:05:47 UTC

Tony - the doc text was added on January 6, let me know if more is needed.

Comment 14 errata-xmlrpc 2022-03-10 16:17:15 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056