Description of problem: When installing OpenShift on top of OpenStack, the post-installation management of MachinePools (which translate into MachineSets in the target cluster) is not functioning. Version-Release number of selected component (if applicable): lates How reproducible: 100% Steps to Reproduce: 1. Install OpenShift onto an OpenStack environment 2. After installation, modify a MachinePool (raise the replica count) 3. Actual results: Hive doesn't update the MachineSet definition in the target cluster is not updated to reflect the changes made to the MachinePool. Expected results: Hive updates the MachineSet. Additional info:
Tested on registry.svc.ci.openshift.org/ocp/release:4.7.0-0.nightly-2020-11-25-114114 hive commit id: 7a4ece8ca2d02cd619da7 1. Install OpenShift onto an OpenStack environment 2. After installation, modify a MachinePool, change replica count from 3 to 2 $ oc get machinepool lwanosphive-worker NAME POOLNAME CLUSTERDEPLOYMENT REPLICAS lwanosphive-worker worker lwanosphive 2 3. check on target cluster, machinesets count scale down from 3 to 2 $ oc get machineset -n openshift-machine-api NAME DESIRED CURRENT READY AVAILABLE AGE lwanosphive-jkc5n-worker-0 2 2 2 2 3h 4. change replica count from 2 to 3 again, check on target cluster, machinesets scale up to 3 again $ oc get machineset -n openshift-machine-api NAME DESIRED CURRENT READY AVAILABLE AGE lwanosphive-jkc5n-worker-0 3 3 3 3 3h7m
No doc update per Greg
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633