-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
CORENET Sprint 275
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
If a Layer3 UserDefinedNetwork exists in the cluster having a configuration that limits the number of nodes when the cluster is expanded or scaled out the nodes not receiving the subnet of that UDN remain in `NotReady` status and the related ovnkube-node pod get into CrashLoopBackOff. In this scenario a project admin has the possibility of break the cluster or make impossible to scale it out.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Always
Steps to Reproduce:
1. Install a cluster with 6 nodes.
2. Create L3 P-UDN configuration that can allow 8 nodes.
3. Expand the cluster to have more than 8 nodes.
Actual results:
The 9th and subsequent nodes join the cluster but remain in `NotReady` status and the related ovnkube-node pod get into CrashLoopBackOff.
Expected results:
The node should be able to join the cluster and only the UDN should fail.