-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.15
-
None
-
Important
-
No
-
CNF RAN Sprint 248, CNF RAN Sprint 249, CNF RAN Sprint 250, CNF RAN Sprint 251
-
4
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-27504. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-27428. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-27031. The following is the description of the original issue:
—
Description of problem:
If one tries to over-ride the NMStateConfig CR by providing a Node level crTemplate, the resulting CRs does not include the NMStateConfig CR because of logic flaw where we ignore that CR's generation if the user did not include the networking details in spec.clusters.nodes.NodeNetwork.Config and pec.clusters.nodes.NodeNetwork.Interfaces parts of the siteConfig. The user did not include them because they are including it as part of the NMStateConfig over-ride.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Remove the spec.clusters.nodes.NodeNetwork.Config and pec.clusters.nodes.NodeNetwork.Interfaces parts of the siteConfig and include crTemplate at the node level to over-ride the NMStateConfig CR
2. run the siteConfigGenrator tool
3. Observe the output
Actual results:
The NMStateConfig CR is missing from the generated CRs
Expected results:
The output CRs includes a NMStateConfig CR
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to