Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1497042 - Unable to mount dynamically provisioned persistant volumes using vSphere
Unable to mount dynamically provisioned persistant volumes using vSphere
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage (Show other bugs)
3.6.1
Unspecified Unspecified
urgent Severity urgent
: ---
: 3.6.z
Assigned To: Pavel Pospisil
Jianwei Hou
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-09-29 01:33 EDT by Jaspreet Kaur
Modified: 2017-12-07 02:11 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: volumePath that includes datastore name is parsed incorrectly. The same applies to volumePath that includes datacluster and datastore names. Consequence: It is not possible to attach persistent volumes that have the above described volumePath values. Fix: volumePath is now parsed correctly. Result: Persistent volumes that have the above described volumePath values are attached correctly.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-07 02:11:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3389 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise security, bug fix, and enhancement update 2017-12-07 07:09:10 EST

  None (edit)
Description Jaspreet Kaur 2017-09-29 01:33:32 EDT 
Description of problem: We have set up OCP to dynamically create vmdk-files in vSphere as persistant volumes.
When creating a pod using persistant volumes, we get this error message:
Failed to attach volume "pvc-c60418fb-a1e8-11e7-978a-005056bf7cc7" on node "ocp-prod-node01.x.y " with: datastore 'D6OCPV01' not found


When we specified "datastore: OCPPROD/D6OCPV01" it where able to provision the volume, but not mount it.
## Failed to attach volume "pvc-ec2816b1-a2c4-11e7-978a-005056bf7cc7" on node "ocp-prod-node02.local.husbanken.no" with: datastore 'D6OCPV01' not found"


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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results: It is not able to locate the datastore.


Expected results: It shpuld be able to locate it

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

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

Additional info:
Comment 7 Jan Safranek 2017-10-02 06:48:58 EDT 
It's hard to guess what's wrong without reproducing the bug locally.

@Jianwei, can you or someone from your team try to reproduce the bug on our systems and give me access there?

I suspect that it's caused by https://github.com/kubernetes/kubernetes/issues/44007 and it's fixed by https://github.com/kubernetes/kubernetes/pull/44868, but that's just a wild guess.
Comment 11 Jan Safranek 2017-10-23 03:27:50 EDT 
The PR is not merged yet
Comment 18 Jianwei Hou 2017-11-06 05:00:11 EST 
Tested on v3.6.173.0.63

Volume mounted successfully when storageclass has 'datastore' parameter.
Comment 23 errata-xmlrpc 2017-12-07 02:11:23 EST 
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/RHSA-2017:3389
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.