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.
[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
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