-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.13, 4.14, 4.15.0
In MGMT-10869, validations were added to assisted-service to forbid the user specifying multiple machineNetworks per address family in the AgentClusterInstall. mkowalsk@redhat.com confirmed that this is due to a design limitation in assisted-service.
However, in OpenShift in general, it is permissible and supported to have multiple machineNetworks for a single address family. This was only documented in https://docs.openshift.com/container-platform/4.14/nodes/edge/nodes-edge-remote-workers.html relatively recently (by HCIDOCS-69), but the docs were backported because this has long been the case.
There are no validations in openshift-installer that prevent multiple machineNetworks, so if a user specifies this in their install-config then an agent-based install will fail to complete, and only debugging the rendezvous host logs will show why.
Since this is a supported and reasonably common topology, ideally it would be allowed. It is not yet clear what other implications this would have for assisted-service. This may extend to other validations, such as the one that checks for connectivity between hosts.
- blocks
-
OCPSTRAT-1700 Baremetal IPI/ABI Close Feature Gaps
- New
- causes
-
RFE-5378 Allow specifying multiple MachineNetworks in "install-config.yaml" instead of "agent-config.yaml"
- Accepted
- is depended on by
-
OCPBUGS-30730 Remote worker nodes should be allowed with baremetal agent installer
- Closed
- is related to
-
OCPBUGS-30233 Agent install validations require connectivity on every interface
- ASSIGNED
- relates to
-
OCPBUGS-26955 Agent installer should return error if multiple machine networks defined for single stack
- Closed
- links to