Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1322006 - [RFE] Support to prevent from using same pvc by multiple pods accidentally
[RFE] Support to prevent from using same pvc by multiple pods accidentally
Status: CLOSED NOTABUG
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.1.0
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Bradley Childs
Johnny Liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-29 10:35 EDT by Kenjiro Nakayama
Modified: 2017-02-15 17:55 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-02-15 17:55:32 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2214541 None None None 2016-03-31 01:19 EDT

  None (edit)
Description Kenjiro Nakayama 2016-03-29 10:35:04 EDT
1. Proposed title of this feature request

[RFE] Support to prevent from using same pvc by multiple pods accidentally

3. What is the nature and description of the request?

- There are no way to restrict to be used pvc which is "in use" by other pods in same namespace(project)

4. Why does the customer need this? (List the business requirements here)
5. How would the customer like to achieve this? (List the functional requirements here)

Steps to Reproduce:
step-1. Create pvc

  $ oc get pvc
  NAME      LABELS    STATUS    VOLUME    CAPACITY   ACCESSMODES   AGE
  claim1    <none>    Bound     pv0001    1Gi        RWO           13s

step-2. Create pod(nfs-test) and use above pvc(claim1).

  $ oc describe pod nfs-test |grep -1 claim1
      Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
      ClaimName:	claim1
      ReadOnly:	false

step-3. Create another pod(nfs-test2) and use same pvc(claim1).

  $ oc describe pod nfs-test2 |grep -1 claim1
      Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
      ClaimName:	claim1
      ReadOnly:	false

- It is possible to use the pvc "in-use" by other pods.
- We want some options to prevent from using in-use pvc by other pods.


7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

- No, as far as I searched.
Comment 2 Kenjiro Nakayama 2016-03-29 11:04:50 EDT
I think we should some way to see if pvc has already been in-use or not.
Comment 5 Steve Watt 2016-07-18 21:18:01 EDT
I think this issue is that you have specified a Shared File System as READWRITEONCE(RWO). That is really a READWRITEMANY accessmode. ReadWriteOnce devices (Block Devices - such as ISCSI, AWS EBS, or Ceph RBD) have their own locking mechanisms to prevent simultaneous access to the storage resource from more than one host.

NFS is designed to be used by more than one host. I think you can get around this issue by verifying that the AccessMode of all of your PVs are correctly specified.

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