Description of problem:
Due to insufficient internal validation, the NUMA resources operator can allow defining NodeGroups that map to more than a single MachineConfigPool. The operator was however designed in such a way that a NodeGroup must not map to more than a single pool of nodes. Users that wishes to manage more than a single pool should instead use more node groups.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
not enough data. Issue discovered internally through code review.
Steps to Reproduce:
1. TBD 2. 3.
Actual results:
The issue manifests itself with multiple MachineConfigPools reported in status when a single NodeGroup is configured in spec
Expected results:
Each NodeGroup must match one pool, so the number of MachineConfigPools in status must match the number of NodeGroups in spec.
Additional info: