Bug 1834965
| Summary: | VMware UPI - Machine is in phase & machine does not have valid node reference" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Morgan Peterman <morgan.peterman> |
| Component: | Unknown | Assignee: | Sudha Ponnaganti <sponnaga> |
| Status: | CLOSED DUPLICATE | QA Contact: | jima |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, eparis, jima, jokerman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-12 20:27:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1834966 *** |
Description of problem: After deploying OCP 4.4.3 on VMware the following alerts are present upon login: May 12, 2:29 pm machine openshift-dj2bm-master-0 is in phase May 12, 2:29 pm machine openshift-dj2bm-master-1 is in phase May 12, 2:29 pm machine openshift-dj2bm-master-2 is in phase May 12, 2:29 pm machine openshift-dj2bm-master-0 does not have valid node reference May 12, 2:29 pm machine openshift-dj2bm-master-1 does not have valid node reference May 12, 2:29 pm machine openshift-dj2bm-master-2 does not have valid node reference The following Machines are created: $ oc get machines -o wide NAME PHASE TYPE REGION ZONE AGE NODE PROVIDERID STATE openshift-dj2bm-master-0 33m openshift-dj2bm-master-1 33m openshift-dj2bm-master-2 33m $ oc describe machine openshift-dj2bm-master-0 Name: openshift-dj2bm-master-0 Namespace: openshift-machine-api Labels: machine.openshift.io/cluster-api-cluster=openshift-dj2bm machine.openshift.io/cluster-api-machine-role=master machine.openshift.io/cluster-api-machine-type=master Annotations: <none> API Version: machine.openshift.io/v1beta1 Kind: Machine Metadata: Creation Timestamp: 2020-05-12T18:08:10Z Generation: 1 Resource Version: 1695 Self Link: /apis/machine.openshift.io/v1beta1/namespaces/openshift-machine-api/machines/openshift-dj2bm-master-0 UID: f9d58c3a-003e-40d7-8f2e-1634ce9bf117 Spec: Metadata: Creation Timestamp: <nil> Provider Spec: Value: API Version: vsphereprovider.openshift.io/v1beta1 Credentials Secret: Name: vsphere-cloud-credentials Disk Gi B: 120 Kind: VSphereMachineProviderSpec Memory Mi B: 16384 Metadata: Creation Timestamp: <nil> Network: Devices: Network Name: Num CP Us: 4 Num Cores Per Socket: 1 Template: User Data Secret: Name: master-user-data Workspace: Datacenter: LAB Datastore: raid0 Folder: openshift-dj2bm Server: vcenter.lab.int Status: Events: <none> install-config.yaml apiVersion: v1 baseDomain: lab.int compute: - hyperthreading: Enabled name: worker replicas: 0 controlPlane: hyperthreading: Enabled name: master replicas: 3 metadata: name: openshift networking: clusterNetworks: - cidr: 10.254.0.0/16 hostPrefix: 24 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16 platform: vsphere: vcenter: vcenter.lab.int username: Administrator password: .... datacenter: LAB defaultDatastore: raid0 pullSecret: '{ "auths": {...} }' sshKey: 'ssh-rsa ...' Version-Release number of selected component (if applicable): 4.4.3 How reproducible: Every time. Steps to Reproduce: 1. Provision OpenShift Container Platform 4.4.3 on VMWare using UPI 2. 3. Actual results: Machines created that are not associated to the actual Master nodes which result in the error messages. Expected results: Either no Machines are created or the Machines are created and then associated to the master nodes. Additional info: