Bug 1966525 - Switch from Disabled to Managed mode IPv6: ScaleUP fails InsertMedia returned code 500
Summary: Switch from Disabled to Managed mode IPv6: ScaleUP fails InsertMedia returne...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Derek Higgins
QA Contact: Amit Ugol
Depends On:
Blocks: 1927068
TreeView+ depends on / blocked
Reported: 2021-06-01 10:40 UTC by Aleksandra Malykhin
Modified: 2021-07-21 06:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-21 06:36:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

Comment 1 Derek Higgins 2021-06-01 13:37:37 UTC
>  HTTP POST https://[fd2e:6f44:5dd8::1]:8000/redfish/v1/Managers/e46202f9-5647-4188-a0ef-3e520a061ac2/VirtualMedia/Cd/Actions/VirtualMedia.InsertMedia returned code 500. Base.1.0.GeneralError: Failed fetching image from URL http://[fd00:1101:0:1::3]:6180/redfish/boot-91499985-2979-44d8-894a-fc0c738de7c9.iso?filename=tmp71_k6yzg.iso: HTTPConnectionPool(host='fd00:1101:0:1::3', port=6180): Max retries exceeded with url: /redfish/boot-91499985-2979-44d8-894a-fc0c738de7c9.iso?filename=tmp71_k6yzg.iso (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb2cd47b6d8>: Failed to establish a new connection: [Errno 101] Network is unreachable',))

This error suggests that the BMC (in your case sushy-tools?) isn't able to contact the masters IPv6 address on the provisioning network, 

I was able to reproduce this with the instructions you provided, in my case the problem was that my provisioning bridge on the virt host didn't have an IP on the fd00:1101:0:1::/64 range, It did have one on the 
fd00:1101::/64 range (the dev-scripts default) but your not using the default range.

I'm guessing the system your using to setup the virt infrastructure isn't setting up the provisioning bridge with a IPv6 as its run with a provisioning network Disabled and doesn't expect it to be re-enabled after the fact. Can you see if giving your provisioning bridge an IP in the fd00:1101:0:1::/64 range solves the problem.

Note You need to log in before you can comment on or make changes to this bug.