Bug 1880443 - broken machine pool management on OpenStack
Summary: broken machine pool management on OpenStack
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hive
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Joel Diaz
QA Contact: wang lin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-18 14:35 UTC by Joel Diaz
Modified: 2021-02-24 15:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:18:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift hive pull 1141 0 None closed Bug 1880443: fix Openstack machinesets 2021-01-21 10:29:41 UTC
Github openshift installer pull 4196 0 None closed Bug 1880443: allow providing client options when generating OpenStack MachineSets 2021-01-21 10:29:41 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:20:53 UTC

Description Joel Diaz 2020-09-18 14:35:47 UTC
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:

Comment 2 wang lin 2020-11-26 06:47:36 UTC
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

Comment 4 Jeana Routh 2021-02-11 15:04:19 UTC
No doc update per Greg

Comment 6 errata-xmlrpc 2021-02-24 15:18:37 UTC
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


Note You need to log in before you can comment on or make changes to this bug.