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

Bug 2119095

Summary:	OpenStack deploy failed due to ipv6 address on discovered provisioning server
Product:	Red Hat OpenStack	Reporter:	Udi Shkalim <ushkalim>
Component:	osp-director-agent-container	Assignee:	Andrew Bays <abays>
Status:	CLOSED ERRATA	QA Contact:	OSP Team <rhos-maint>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	abays, astillma, jschluet, mburns, mschuppe
Target Milestone:	z4	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	osp-director-agent-container-1.3.0-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-13 11:11:47 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 Udi Shkalim 2022-08-17 13:55:00 UTC

Description of problem:

OSP installation failed on:
[root@titan132 ~]# oc get bmh -A
NAMESPACE               NAME                 STATE          CONSUMER                      ONLINE   ERROR
openshift-machine-api   openshift-worker-3   provisioning   compute                       true     provisioning error
openshift-machine-api   openshift-worker-4   provisioning   compute                       true
openshift-machine-api   ostest-master-0      unmanaged      ostest-nfxxs-master-0         true
openshift-machine-api   ostest-master-1      unmanaged      ostest-nfxxs-master-1         true
openshift-machine-api   ostest-master-2      unmanaged      ostest-nfxxs-master-2         true
openshift-machine-api   ostest-worker-0      unmanaged      ostest-nfxxs-worker-0-2wfxl   true
openshift-machine-api   ostest-worker-1      unmanaged      ostest-nfxxs-worker-0-6ldlf   true
openshift-machine-api   ostest-worker-2      unmanaged      ostest-nfxxs-worker-0-jmjdp   true


Looking on the error I see the image server is binding ipv6 addr
Events:
  Type    Reason                  Age    From                         Message
  ----    ------                  ----   ----                         -------
  Normal  Registered              19m    metal3-baremetal-controller  Registered new host
  Normal  BMCAccessValidated      19m    metal3-baremetal-controller  Verified access to BMC
  Normal  InspectionStarted       19m    metal3-baremetal-controller  Hardware inspection started
  Normal  InspectionComplete      14m    metal3-baremetal-controller  Hardware inspection completed
  Normal  ProfileSet              14m    metal3-baremetal-controller  Hardware profile set: unknown
  Normal  ProvisioningStarted     14m    metal3-baremetal-controller  Image provisioning started for http://fe80::3efd:feff:fe78:cd12:8080/images/rhel-guest-image-8.4-992.x86_64.qcow2/compressed-rhel-guest-image-8.4-992.x86_64.qcow2
  Normal  ProvisioningError       14m    metal3-baremetal-controller  Image provisioning failed: Failed to prepare to deploy: Validation of image href http://fe80::3efd:feff:fe78:cd12:8080/images/rhel-guest-image-8.4-992.x86_64.qcow2/compressed-rhel-guest-image-8.4-992.x86_64.qcow2 failed, reason: Failed to parse: fe80::3efd:feff:fe78:cd12:8080

Version-Release number of selected component (if applicable):
master branch

How reproducible:
Race

Steps to Reproduce:
1. Deploy OSP with ipv4 
2.
3.

Actual results:
Deploy failed on provisioning machines

Expected results:
Deploy failed

Additional info:

Comment 15 errata-xmlrpc 2022-12-13 11:11:47 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 (Release of containers for Red Hat OpenStack Platform 16.2.4 director operator), 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-2022:8952

Comment 16 Red Hat Bugzilla 2023-09-18 04:44:58 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days