Bug 1863917 - [OSP] All machinesets have the same name
Summary: [OSP] All machinesets have the same name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Mike Fedosin
QA Contact: David Sanz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-03 17:40 UTC by Mike Fedosin
Modified: 2020-10-27 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:22:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 4000 0 None closed Bug 1863917: give unique names for machinesets in different AZs 2020-10-01 08:10:35 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:22:57 UTC

Description Mike Fedosin 2020-08-03 17:40:23 UTC
Description of problem:

When I use multiple availability zones all generated machinesets have the same name. Since they are created in the same namespace, it leads to the fact that only one machineset can exist.

Comment 3 David Sanz 2020-09-10 11:44:19 UTC
[morenod@morenod-laptop ~]$ oc get machineset
NAME                        DESIRED   CURRENT   READY   AVAILABLE   AGE
mrnd-16-az-cb6b5-worker-0   2         2         2       2           20m
mrnd-16-az-cb6b5-worker-1   2         2         2       2           20m
mrnd-16-az-cb6b5-worker-2   2         2         2       2           20m
[morenod@morenod-laptop ~]$ oc get machines
NAME                              PHASE     TYPE        REGION      ZONE   AGE
mrnd-16-az-cb6b5-master-0         Running   m4.xlarge   regionOne   AZ1    20m
mrnd-16-az-cb6b5-master-1         Running   m4.xlarge   regionOne   AZ2    20m
mrnd-16-az-cb6b5-master-2         Running   m4.xlarge   regionOne   AZ3    20m
mrnd-16-az-cb6b5-worker-0-8nc2c   Running   m4.xlarge   regionOne   AZ1    11m
mrnd-16-az-cb6b5-worker-0-9tjq5   Running   m4.xlarge   regionOne   AZ1    12m
mrnd-16-az-cb6b5-worker-1-hsr64   Running   m4.xlarge   regionOne   AZ2    12m
mrnd-16-az-cb6b5-worker-1-wtqn7   Running   m4.xlarge   regionOne   AZ2    11m
mrnd-16-az-cb6b5-worker-2-282ms   Running   m4.xlarge   regionOne   AZ3    10m
mrnd-16-az-cb6b5-worker-2-fbbjp   Running   m4.xlarge   regionOne   AZ3    10m
[morenod@morenod-laptop ~]$ oc get nodes
NAME                              STATUS   ROLES    AGE     VERSION
mrnd-16-az-cb6b5-master-0         Ready    master   18m     v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-master-1         Ready    master   18m     v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-master-2         Ready    master   18m     v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-0-8nc2c   Ready    worker   2m53s   v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-0-9tjq5   Ready    worker   3m25s   v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-1-hsr64   Ready    worker   3m20s   v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-1-wtqn7   Ready    worker   2m23s   v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-2-282ms   Ready    worker   87s     v1.19.0-rc.2+fc4c489
mrnd-16-az-cb6b5-worker-2-fbbjp   Ready    worker   80s     v1.19.0-rc.2+fc4c489

Comment 5 errata-xmlrpc 2020-10-27 16:22:34 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196


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