Bug 1902584
| Summary: | RHCOS fails to activate static VLAN IP when first booting from disk during installation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ondrej Faměra <ofamera> |
| Component: | RHCOS | Assignee: | Dusty Mabe <dustymabe> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Nguyen <mnguyen> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5 | CC: | bbreard, imcleod, jligon, miabbott, nstielau, pchavan |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Failure to properly tear down network interfaces in the initrd before switching to the real root
Consequence: Static IP assignment to a VLAN interface may not be successfully activated in the real root.
Fix: Change how network interfaces are torn down in the initrd
Result: Static IP assignments to VLAN interfaces are successfully activated in the real root.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-10 20:15:44 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
Ondrej Faměra
2020-11-30 06:30:58 UTC
Targeting for 4.7 with medium priority; if a fix is needed in 4.6, we will need to clone the BZ accordingly. I believe this is a duplicate of BZ#1860060 (fixed in 4.6). See comment https://bugzilla.redhat.com/show_bug.cgi?id=1860060#c3 for details. Hi Dusty, Checking on BZ#1860060 it really feels like that addresses it - as mentioned in description the 4.6 works fine, the 4.5 is affected. In short: 1. Is there consideration to bring the fix from 4.6 into 4.5? (yes/no) (if yes, we will wait with support on updates here) 2. If not, then can we treat this as documentation BUG to improve docs mentioning this behaviour as "known limitation that was improved in 4.6 release" ideally mentioning the workaround (additional manual reboot needed for RHCOS to pick up the address)? Thank you. (In reply to Ondrej Faměra from comment #5) > Hi Dusty, > > Checking on BZ#1860060 it really feels like that addresses it - as mentioned > in description the 4.6 works fine, the 4.5 is affected. > In short: > > 1. Is there consideration to bring the fix from 4.6 into 4.5? (yes/no) > (if yes, we will wait with support on updates here) There were significant changes to how networking was handled in the initrd as part of 4.6, so I don't believe a simple backport is possible. Additionally, changing how the initrd operates in 4.5 would require rebuilding all of the RHCOS boot media as part of a 4.5.z release, which is something we avoid unless absolutely necessary (i.e. to mitigate a CVE). Therefore, we are not considering backporting this fix into 4.5 without additional justification. > 2. If not, then can we treat this as documentation BUG to improve docs > mentioning this behaviour as "known limitation that was improved in 4.6 > release" ideally mentioning the workaround (additional manual reboot needed > for RHCOS to pick up the address)? We can pursue updating the docs for this issue; if you could identify where in the docs we could make an update, that would be useful. > > Thank you. This bug needs more information. It is not scheduled to be worked on in the current sprint. Hi Dusty, Thank you for answer and sorry for delay. I think that adding 'Note' at the end of 'Configure advanced networking' section (https://docs.openshift.com/container-platform/4.5/installing/installing_bare_metal/installing-bare-metal.html#installation-user-infra-machines-static-network_installing-bare-metal) would make most sense for me. Text could be something like: ~~~ Note: When using some of the advanced networking options, such as `vlan=`, you may encounter issue where on first RHCOS boot the statically configured address is not present/activated properly. In such case you can try manually rebooting the machine (use ctrl+alt+delete or sending reset signal to machine depending on your environment). In RHCOS 4.6 the network code was significantly overhauled so these kind of issues should be resolved there. ~~~ (above is just suggestion, feel free to edit) Thank you @Ondrej, thank you for the suggestion. I've made a PR to the docs for OCP 4.5 to suggest the workaround - https://github.com/openshift/openshift-docs/pull/28036 I'm going to close this as CURRENTRELEASE based on comment #5 |