Bug 1943809
| Summary: | [Tracker] NetworkManager doesn't initialize an interface, reports startup complete when booting for the first time | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ken Young <keyoung> |
| Component: | Unknown | Assignee: | Ken Young <keyoung> |
| Status: | CLOSED NOTABUG | QA Contact: | Gowrishankar Rajaiyan <grajaiya> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | aos-bugs, bradnichols, eparis, jokerman, ykashtan |
| Target Milestone: | --- | Keywords: | Tracking |
| Target Release: | --- | ||
| 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-05-27 17:15:15 UTC | Type: | --- |
| 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: | 1917773 | ||
| Bug Blocks: | |||
|
Description
Ken Young
2021-03-27 16:17:50 UTC
@ykashtan What are the next steps here? Is this a fix we can absorb? /KenY I think there's already a BZ on OCP to utilize this new behavior. I also think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1946079 (among others) and I believe the right solution would be to augment installer/MCO so that node will wait for either ipv4 or ipv6 based on cluster IPs (ie if api ip is ipv4, wait for ipv4, if it's ipv6 wait for ipv6) @ykashtan, > I think there's already a BZ on OCP to utilize this new behavior. Do you have a specific one we should track? > I also think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1946079 (among others) We should track this one? > and I believe the right solution would be to augment installer/MCO so that node will wait for either ipv4 or ipv6 based on cluster IPs (ie if api ip is ipv4, wait for ipv4, if it's ipv6 wait for ipv6) How do we promote this as the right solution? What do we do with this bug in the meantime? /KenY Closing. OCP engineering has requested we use an alternative method for trackers. |