-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
3
-
Important
-
None
-
aarch64
-
QA
-
None
-
None
-
Rejected
-
Metal Platform 275
-
1
-
Done
-
Known Issue
-
-
None
-
None
-
None
-
None
Description of problem:
Inspection step fails when the bmcAddress of the BMH resource is IPv6 for a SuperMicro ARS-111GL-NHR server. The node is unable to boot into the virtual media for the inspection image and the virtual media does not appear in the boot menu as a source. Manually hitting connect in the BMC gives a file not found error, but running `curl -kILs` on the iso address in the BMC returns a 200 code. Redeploying with an IPv4 address while using single-stack IPv6 for the node itself succeeds. It does not appear to be a simple connectivity issue since the BMH only starts inspecting after it is able to confirm connection to the BMC over IPv6, confirmed in the metal3-ironic logs as there are regular successful requests.
Version-Release number of selected component (if applicable):
4.20.0-0.nightly-2025-07-20-021531
How reproducible:
100%
Steps to Reproduce:
1. Apply a BareMetalHost referencing the IPv6 address of a SuperMicro ARS-111GL-NHR 2. Wait for inspection to start. Connectivity to BMC is confirmed but server reboots into disk with old cluster installation 3. Try to connect to the virtual media
Actual results:
VirtualMedia does not appear in SuperMicro BMC but can be curled. metal3-ironic logs show 202 response to providing virtual media
Expected results:
VirtualMedia appears in SuperMicro BMC and can be booted into
Additional info:
- links to