Bug 2023765

Summary: [BM] [IPI] [Dual Stack] Installer must ensure ipv6 short forms too if clusterprovisioning IP is specified as ipv6 address [4.8]
Product: OpenShift Container Platform Reporter: Bob Fournier <bfournie>
Component: Bare Metal Hardware ProvisioningAssignee: 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, awolff, beth.white, bfournie, dmoessne, jmalde, lshilin, nchavan, shardy, tsedovic, vvoronko
Version: 4.8Keywords: Triaged
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: x86_64   
OS: Linux   
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: 2023748 Environment:
Last Closed: 2022-01-05 16:11:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2023748    
Bug Blocks:    

Comment 3 Adina Wolff 2021-12-07 18:00:36 UTC
Deployment failed on the specified version:

[kni@provisionhost-0-0 ~]$ oc get clusterversion
version             False       True          109m    Unable to apply 4.8.0-0.nightly-2021-12-06-234030: some cluster operators have not yet rolled out

Comment 4 Bob Fournier 2021-12-07 18:08:14 UTC
Is there any indication the short form IPv6 address is not being used and is the reason for the failure?
Is what is being logged in the ironic log in long form e.g.:
 2021-10-04T14:00:29.841756101Z Waiting for fd8a:216d:178e:c1df:0000:0000:0000:0003 to be configured on an interface

Different than what is being reported for the interface in short form?

Comment 5 Adina Wolff 2021-12-07 18:21:58 UTC
The log shows the following message:
Waiting for fd00:1101:0000:0001:0000:0000:0000:0003/64 to be configured on an interface

Comment 6 Adina Wolff 2021-12-08 09:25:09 UTC
Deployment on the same version with short-form ipv6 is successful


[kni@provisionhost-0-0 ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-12-06-234030   True        False         8m31s   Cluster version is 4.8.0-0.nightly-2021-12-06-234030

    provisioningNetworkInterface: enp0s3
    provisioningNetworkCIDR: fd00:1101:0:1::/64
    bootstrapOSImage: http://registry.ocp-edge-cluster-0.qe.lab.redhat.com:8080/images/rhcos-48.84.202109241901-0-qemu.x86_64.qcow2.gz?sha256=50377ba9c5cb92c649c7d9e31b508185241a3c204b34dd991fcb3cf0adc53983

Comment 7 Bob Fournier 2021-12-08 17:44:10 UTC
Thanks Adina. Debugging with Adina showed that the problem is only occurring and logged for ironic-inspector. This is because ironic-conductor and inspector used different images in 4.8 so will need to make the corresponding change to https://github.com/openshift/ironic-inspector-image/blob/release-4.8/scripts/ironic-common.sh#L9

Comment 10 Adina Wolff 2021-12-19 12:10:14 UTC
Deployment was successful with version 4.8.0-0.nightly-2021-12-18-022810.
Relevant part of install-config was:

    provisioningNetworkInterface: enp0s3
    provisioningNetworkCIDR: fd00:1101:0000:0001:0000:0000:0000:0000/64
    bootstrapProvisioningIP: fd00:1101:0000:0001:0000:0000:0000:0002
    clusterProvisioningIP: fd00:1101:0000:0001:0000:0000:0000:0003

Comment 13 errata-xmlrpc 2022-01-05 16:11:41 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 (OpenShift Container Platform 4.8.25 bug fix 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.