Bug 1727991 - Vsphere storage provider returns 'No Vm found' to pv-controller
Summary: Vsphere storage provider returns 'No Vm found' to pv-controller
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: aos-storage-staff@redhat.com
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-08 18:36 UTC by emahoney
Modified: 2024-03-25 15:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-09 16:13:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description emahoney 2019-07-08 18:36:02 UTC
Description of problem: When provisioning storage from a vsphere storage provider, the storage provider returns 'No VM found' to the pv-controller[1]. We also see in the node spec that tehe 'providerID' is not being set properly on the nodes. 'govc' returns the proper hosts and seem to match the vsphere.conf configuration.  

[1]
Events:
  Type     Reason              Age               From                         Message
  ----     ------              ----              ----                         -------
  Warning  ProvisioningFailed  5s (x2 over 12s)  persistentvolume-controller  Failed to provision volume with StorageClass "vsphere-standard": No VM found


Version-Release number of selected component (if applicable):
3.11 latest

How reproducible:
Able to reproduce the 'No VM found' error by creating a PVC using the vsphere sc. 

Steps to Reproduce:
1. Create a PVC specifying 'vsphere-standard' as the storage class.
2.
3.

Actual results:
PV fails to be created and the pv-controller is returned 'No VM found'.


Expected results:
PV created on vpshere side and mounted to the node. 

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 15 emahoney 2019-07-09 16:13:55 UTC
The UUIDs configured on the client[1] were not matching what was in vmware. Resolving those UUIDs fixed the issue. 

[1]
# cat /sys/class/dmi/id/product_serial
# cat /sys/class/dmi/id/product_uuid
# oc describe node <nodename> | grep  "System UUID"

Comment 16 ShashiMaraIBM 2021-05-01 20:04:05 UTC
Reference:  How did you fix it? 
Had the same issue restoring the VM after unsuccessful pathing the Linux. Resolved by 
https://access.redhat.com/solutions/4256051


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