Bug 1932108
| Summary: | [4.7] [DOC ONLY] OVS configuration service unable to clone NetworkManager's connections in the overlay FS | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tim Rozet <trozet> |
| Component: | Machine Config Operator | Assignee: | Tim Rozet <trozet> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Michael Nguyen <mnguyen> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.7 | CC: | anbhat, behoward, brad, jboxman, mkrejci, mnguyen, odepaz, trozet |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause:
When deploying to some platforms, including Bare Metal and VSphere, and the deployment is using static IP addressing on the node's default gateway interface, ovs-configuration.service may fail to properly configure host networking.
Consequence:
The deployment will fail.
Workaround (if any):
Use ignition to create Network Manager keyfiles for setting up the required connections. This will avoid ovs-configuration.service from executing the its configuration code. Another workaround is to use DHCP instead of static IP addressing, when possible.
Result:
Deployment succeeds.
|
Story Points: | --- |
| Clone Of: | 1927405 | Environment: | |
| Last Closed: | 2021-02-24 01:27:38 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: | 1927366, 1927405 | ||
| Bug Blocks: | |||
|
Comment 4
Red Hat Bugzilla
2023-09-15 01:02:01 UTC
|