Bug 1963101

Summary:	scaling the machineset of a openshift 4.7.9 attached as local-cluster hosted on vmware causes the scaling to get reverted
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Felix Dewaleyne <fdewaley>
Component:	Cluster Lifecycle	Assignee:	Joshua Packer <jpacker>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Derek Ho <dho>
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	unspecified
Version:	rhacm-2.2	CC:	cahl, fdewaley, gekis, jpacker, juhsu, mheppler
Target Milestone:	---	Flags:	ming: rhacm-2.2.z+ ming: needinfo+
Target Release:	rhacm-2.2.6
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-04 20:25:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Felix Dewaleyne 2021-05-21 12:43:12 UTC

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

Comment 8 Joshua Packer 2021-06-17 14:49:55 UTC

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?

Comment 10 Felix Dewaleyne 2021-06-22 09:00:56 UTC

The customer confirmed that this was deployed from Hive.

Comment 16 Joshua Packer 2021-06-24 12:56:54 UTC

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.

Comment 26 juhsu 2021-08-04 20:25:13 UTC

No response in over 4 weeks.  Closing.  Please reopen if further assistance is required.

Comment 29 Red Hat Bugzilla 2023-09-15 01:07:01 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days