Bug 2034527
Summary: | IPI deployment fails 'timeout reached while inspecting the node' when provisioning network ipv6 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Lubov <lshilin> |
Component: | Installer | Assignee: | Derek Higgins <derekh> |
Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Lubov <lshilin> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | urgent | CC: | achernet, aguclu, jniu, rpittau, stbenjam, vvoronko, yjoseph, ykashtan, zbitter |
Version: | 4.10 | Keywords: | AutomationBlocker, Triaged |
Target Milestone: | --- | ||
Target Release: | 4.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
job=periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-ovn-dualstack=all
|
|
Last Closed: | 2022-03-10 16:35:46 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
Lubov
2021-12-21 08:36:35 UTC
Could you log into the machine's virtual console to see what is happening there? Okay, got it. So we're seeing a failure to connect to the rootfs location. Now I wonder if it's a DHCP issue or an issue with routing. The address it is trying to use, do you expect it to be reachable from the machine? @vvoronko, can you help with DHCP question, please reproduced for 4.10.0-0.nightly-2021-12-21-130047 bm ipv4 provisioning ipv6 https://s3.upshift.redhat.com/DH-PROD-OCP-EDGE-QE-CI/Infra/must-gather/1191/index.html *** Bug 2035219 has been marked as a duplicate of this bug. *** *** Bug 2037419 has been marked as a duplicate of this bug. *** as far as I can see ip=dhcp is being included in the kernel params, this is what we had in dualstack pre METAL-1, but the provisioning network is ipv6 so RHCOS doesn't boot and cant inspect. I think pre metal-1 this was fine because ip=dhcp wasn't being set on the the IPA image, now it is (as its now using RHCOS) so it is attempting to boot with ip=dhcp and then can't download the rootfs at http://[fd00:1101::2]:80/images/ironic-python-agent.rootfs This is breaking dual-stack, even in CI, so it is definitely a release blocker. The cluster is now provisioning in CI but some of the tests are failing, new bz opened https://bugzilla.redhat.com/show_bug.cgi?id=2040671 verified on 4.10.0-0.nightly-2022-01-15-092722 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 (Moderate: OpenShift Container Platform 4.10.3 security 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. https://access.redhat.com/errata/RHSA-2022:0056 |