Bug 1932967
Summary: | [on-prem] Unable to deploy additional machinesets on separate subnets | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
Component: | Machine Config Operator | Assignee: | Martin André <m.andre> |
Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.7 | CC: | dgautam, ekasprzy, fmarting, javier.ordax, mkrejci, simore |
Target Milestone: | --- | ||
Target Release: | 4.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: For all on-premise platforms, when discovering the node IP, baremetal-runtimecfg wrongly assumed the nodes are always attached to a subnet that includes the VIP and looked for an address in this IP range.
Consequence: Nodes fail to generate configuration files with baremetal-runtimcfg.
Fix: Fallback to the IP address associated with default route.
Result: New compute nodes can join the cluster when deployed on separate subnets.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-03-16 23:22:18 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: | 1894539 | ||
Bug Blocks: |
Comment 2
weiwei jiang
2021-03-08 04:19:57 UTC
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 (OpenShift Container Platform 4.6.21 bug fix 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/RHBA-2021:0753 |