-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
No
-
None
-
None
-
None
-
CNF Compute Sprint 268, CNF Compute Sprint 269
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Upon changes to node groups that targets different nodes than those were initially, config map for the old groupand NRTs for the old target nodes are not cleaned up.
Version-Release number of selected component (if applicable):
all
How reproducible:
always
Steps to Reproduce:
1. cluster with 2 MCPs for workers with machine count > 0: mcp-1, mcp-2 2. configure NROP CR with mcp-1; CM and NRTs (following RTEs) will be cretaed for the targetted nodes by mcp-1 3. update NROP CR to point to a mcp-2 An easy way to reproduce is also: 1. configure NROP with node group that targets at least 1 node 2. delete the NROP CR -> old CM and NRTs are kept
Actual results:
1. new NRTs are created for the missing nodes as expected 2. old CM is not deleted 3. old NRTs are not deleted
Expected results:
1. new NRTs are created for the missing nodes as expected 2. old CM and NRTs should be cleaned up
Additional info:
workaround is to delete old (dangling) objects manually
- is related to
-
OCPBUGS-51261 NROP controller doesn't create new CM on node groups updates
-
- Closed
-