*** Bug 1833357 has been marked as a duplicate of this bug. ***
Closing. No longer plan to backport this to 4.4. Works in 4.5.
Validated on version - [miyadav@miyadav bugaws]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-06-08-032819 True False 28m Cluster version is 4.4.0-0.nightly-2020-06-08-032819 Reproducible Always Steps: 1.create IPI install AWS env. 2.Create DHCP Options set 3.Update VPC with new DHCP options set 4.scale machineset - oc scale machineset miyadav-0806-kl9rb-worker-us-east-2c --replicas=2 5.once the node is attached to the new provisioned machine - [miyadav@miyadav bugaws]$ oc get machines -o wide NAME PHASE TYPE REGION ZONE AGE NODE PROVIDERID STATE miyadav-0806-kl9rb-master-0 Running m4.xlarge us-east-2 us-east-2a 36m ip-10-0-145-125.us-east-2.compute.internal aws:///us-east-2a/i-09d9838463b9c2db0 running miyadav-0806-kl9rb-master-1 Running m4.xlarge us-east-2 us-east-2b 36m ip-10-0-182-113.us-east-2.compute.internal aws:///us-east-2b/i-0a5dec738b71bad26 running miyadav-0806-kl9rb-master-2 Running m4.xlarge us-east-2 us-east-2c 36m ip-10-0-220-102.us-east-2.compute.internal aws:///us-east-2c/i-0ea9012a960cddaa0 running miyadav-0806-kl9rb-worker-us-east-2a-pxg8x Running m4.large us-east-2 us-east-2a 27m ip-10-0-149-65.us-east-2.compute.internal aws:///us-east-2a/i-0744ed63ddb02e8a2 running miyadav-0806-kl9rb-worker-us-east-2b-xksmz Running m4.large us-east-2 us-east-2b 27m ip-10-0-166-26.us-east-2.compute.internal aws:///us-east-2b/i-0f29760d6b8e301fd running miyadav-0806-kl9rb-worker-us-east-2c-nmjnt Running m4.large us-east-2 us-east-2c 27m ip-10-0-210-93.us-east-2.compute.internal aws:///us-east-2c/i-06326fe41a1c04583 running miyadav-0806-kl9rb-worker-us-east-2c-v59rd Running m4.large us-east-2 us-east-2c 4m49s ip-10-0-200-52.us-east-2.compute.internal aws:///us-east-2c/i-0e208ce27ce837325 running 6.get csrs [miyadav@miyadav bugaws]$ oc get csr NAME AGE REQUESTOR CONDITION csr-2gskn 23m system:serviceaccount:openshift-machine-config-operator:node-bootstrapper Approved,Issued csr-4v2xv 85s system:node:ip-10-0-200-52.us-east-2.compute.internal Approved,Issued csr-8rtbv 35m system:node:ip-10-0-220-102.us-east-2.compute.internal Approved,Issued csr-ftznb 98s system:serviceaccount:openshift-machine-config-operator:node-bootstrapper Approved,Issued . . 7.describe the newest crs (created because of new node added to cluster ) oc describe csr csr-4v2xv Name: csr-4v2xv Labels: <none> Annotations: <none> CreationTimestamp: Mon, 08 Jun 2020 16:03:34 +0530 Requesting User: system:node:ip-10-0-200-52.us-east-2.compute.internal Status: Approved,Issued Subject: Common Name: system:node:ip-10-0-200-52.us-east-2.compute.internal Serial Number: Organization: system:nodes Subject Alternative Names: DNS Names: ip-10-0-200-52.example.com IP Addresses: 10.0.200.52 Events: <none> Actual & Expected : domain name created in DHCP options set is added to Alternative names 8.oc get machine miyadav-0806-kl9rb-worker-us-east-2c-v59rd -o yaml (status will contain the domain as used in dhcp options set) Actual & Expected : . . status: addresses: - address: 10.0.200.52 type: InternalIP - address: ip-10-0-200-52.us-east-2.compute.internal type: InternalDNS - address: ip-10-0-200-52.us-east-2.compute.internal type: Hostname - address: ip-10-0-200-52.example.com type: InternalDNS lastUpdated: "2020-06-08T10:34:44Z" nodeRef: kind: Node name: ip-10-0-200-52.us-east-2.compute.internal uid: aa4dd9a1-5d09-431c-98cf-2b1c6bd8349b phase: Running providerStatus: apiVersion: awsproviderconfig.openshift.io/v1beta1 conditions: - lastProbeTime: "2020-06-08T10:30:03Z" lastTransitionTime: "2020-06-08T10:30:03Z" message: machine successfully created reason: MachineCreationSucceeded status: "True" type: MachineCreation instanceId: i-0e208ce27ce837325 instanceState: running kind: AWSMachineProviderStatus Additional Info: None Moving to VERIFIED
*** Bug 1846735 has been marked as a duplicate of this bug. ***
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, 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:2445