Bug 1966525
| Summary: | Switch from Disabled to Managed mode IPv6: ScaleUP fails InsertMedia returned code 500 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aleksandra Malykhin <amalykhi> |
| Component: | Bare Metal Hardware Provisioning | Assignee: | Derek Higgins <derekh> |
| Bare Metal Hardware Provisioning sub component: | cluster-baremetal-operator | QA Contact: | Amit Ugol <augol> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, beth.white, derekh, kiran, osher |
| Version: | 4.8 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-21 06:36:11 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: | 1927068 | ||
> 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.