Bug 1861974
Summary: | [vsphere] Machine stuck in provisioning phase , while using default vlaues to create machineset | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Milind Yadav <miyadav> |
Component: | Cloud Compute | Assignee: | Alexander Demicev <ademicev> |
Cloud Compute sub component: | Other Providers | QA Contact: | Milind Yadav <miyadav> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | low | ||
Priority: | unspecified | CC: | agarcial |
Version: | 4.6 | ||
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-09-22 14:51:48 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: |
Description
Milind Yadav
2020-07-30 04:56:47 UTC
VALIDATED ON - Cluster version is 4.6.0-0.nightly-2020-08-18-165040 Steps: 1.use below yaml to create machineset http://pastebin.test.redhat.com/895459 2.Machineset gets created successfuly 3.Validate machine created by machineset [miyadav@miyadav rhv]$ oc get machines -o wide --config vsp NAME PHASE TYPE REGION ZONE AGE NODE PROVIDERID STATE miyadav-vs2108-52mxn-master-0 Running 74m miyadav-vs2108-52mxn-master-0 vsphere://422be7bf-9dd2-9bf0-6f44-18318394b2f2 poweredOn miyadav-vs2108-52mxn-master-1 Running 74m miyadav-vs2108-52mxn-master-1 vsphere://422b98db-0569-8d4f-7424-f023096cb763 poweredOn miyadav-vs2108-52mxn-master-2 Running 74m miyadav-vs2108-52mxn-master-2 vsphere://422b4689-a8b3-e993-4f8b-a72fc55709de poweredOn miyadav-vs2108-52mxn-worker-default-8wnbx Provisioned 27m vsphere://422b67d5-4bd2-3b6c-1465-9b6a0442eb45 poweredOn miyadav-vs2108-52mxn-worker-qbbsp Running 65m miyadav-vs2108-52mxn-worker-qbbsp vsphere://422ba0c6-7c3f-98e0-caf7-68e7efe87c55 poweredOn miyadav-vs2108-52mxn-worker-v8xq6 Running 5m24s miyadav-vs2108-52mxn-worker-v8xq6 vsphere://422b4257-0416-4b8d-1d87-2f46a4c60b86 poweredOn miyadav-vs2108-52mxn-worker-xm42s Running 65m miyadav-vs2108-52mxn-worker-xm42s vsphere://422b06c9-78b5-aefc-bfee-3b4e7e253719 poweredOn ... Expected - Machine should be in Running phase (after this much time) Additional Info : The exisiting machineset scales as expected with successful running status , its only when we use default yaml , it gets stuck shows invalid mount error on the VM console ... There is a bug in defaulting webhook for vSphere. We are thinking about cutting out defaulting webhooks from this release. *** This bug has been marked as a duplicate of bug 1876680 *** |