Description of the problem: scaling the machineset of an openshift 4.7.9 hosted on vmware and attached to ACM as the local-cluster gets reverted shortly after Release version: 2.2 Operator snapshot version: 2.2.3 OCP version: 4.7.9 Browser Info: Steps to reproduce: 1. scale machineset with ` oc edit machineset -n openshift-machine-api`, editing replicas in spec section 2. 3. Actual results: the scaling happens and moments later is reverted automatically Expected results: the scaling stays Additional info: more info as private attachments
On the local-cluster, the machine set that reverted, how was this cluster deployed? My hunch is from hive. Hive has a Machinepool that I suspect is being constantly reconciled by the Hive operator as the MachinePool is the parent(guide) for remote MachineSets. Can you confirm that local-cluster came from a Hive deployment?
The customer confirmed that this was deployed from Hive.
1) So when your deploying a cluster, you can press the YAML button and delete the machinePool YAML definition. In which case you can modify the MachineSets directly. 2) You can also choose to deploy a cluster with 0 worker nodes, and then create MachineSets or a MachinePool.
No response in over 4 weeks. Closing. Please reopen if further assistance is required.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days