Bug 1905134
Summary: | Unable to create a MachineSet when the nodes to create are in a different subnet | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Emmanuel Kasper <ekasprzy> |
Component: | Machine Config Operator | Assignee: | Antonio Murdaca <amurdaca> |
Status: | CLOSED DUPLICATE | QA Contact: | Michael Nguyen <mnguyen> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.5 | CC: | jpasztor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-10 17:25:49 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
Emmanuel Kasper
2020-12-07 15:58:18 UTC
Looking at the code in https://github.com/openshift/machine-config-operator/blob/3add4b96e379d34aa953c8bde82bf0c61054be6d/pkg/operator/bootstrap.go#L256 the keepalived.conf template is stored at filename: "ovirt/static-pod-resources/keepalived/keepalived.conf.tmpl", so I suppose it is a static pod Now if this is a static pod, I can't see how the feature "[ovirt] support network interfaces in machine spec" as implemented in https://bugzilla.redhat.com/show_bug.cgi?id=1830852 should work, as if the worker node is created in a different subnet, keepalived will fail on startup, and the node won't come up. But maybe I am missing something. Thank you for submitting this bug report. I'm investigating if this scenario is actually supported. It may be the case that we need to be able to move the VIP from the master to the worker nodes, or we might have to run two different sets of keepaliveds for the two VIPs. I'll get back to you as soon as I have an answer. I might have not been very clear, but actually I suppose the problem here is I suppose is that the VIP for the Ingress Controller are potentially assigned to all worker nodes, hence the requirement to have keepalived on all worker nodes. I don't see indeed why we would want to have the VIP for the API server on the worker nodes. *** This bug has been marked as a duplicate of bug 1894539 *** |