Bug 1626373 - PVC created by oc set volume cannot be bound to static PV
Summary: PVC created by oc set volume cannot be bound to static PV
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: Kenjiro Nakayama
QA Contact: Xingxing Xia
Depends On:
TreeView+ depends on / blocked
Reported: 2018-09-07 07:47 UTC by Kenjiro Nakayama
Modified: 2021-12-10 17:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-04 10:40:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:40:43 UTC

Description Kenjiro Nakayama 2018-09-07 07:47:23 UTC
Description of problem:
- When cluster has default storageclass, PVC created by oc set volume always bind to the default storage class. In ohter words, it cannot be bound to static PV.

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

  # oc version
  oc v3.9.14
  kubernetes v1.9.1+a0ce1bc657
  features: Basic-Auth GSSAPI Kerberos SPNEGO
  Server https://knakayam-ose39-all.example.com:8443
  openshift v3.9.14
  kubernetes v1.9.1+a0ce1bc657

How reproducible: 100%

Steps to Reproduce:
1. Prepare default StorageClass (dynamic in below) and staic PV(pv0001)

  # oc get sc
  NAME                PROVISIONER         AGE
  cephfs              ceph.com/cephfs     44d
  dynamic (default)   kubernetes.io/rbd   48d

  // Also, we prepare for static PV. (We would like to let PVC bind to this static PV.)
  # oc get pv
  NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM            STORAGECLASS   REASON    AGE
  pv0001                                     1Gi        RWX            Recycle          Available   default/claim1                            23s

2. Run oc set volumes without --claim-name.

  # oc set volumes dc/docker-registry --name=registry-storage --claim-name=registry-claim --claim-mode=ReadWriteMany --claim-size=1Gi --add

3. PVC created is alywas has "storageClassName: dynamic".

  # oc get pvc
  registry-claim   Pending                                       dynamic        1m

  # oc get pvc registry-claim -o yaml |grep storageClassName
    storageClassName: dynamic

Actual results:
- Please refer to step-3 above. It always has "storageClassName: dynamic" so that it cannot bind to static PV(pv0001).

Expected results:
- Assign PVC created by oc set volume bind to static PV.

Additional info:
- If we can specify 'storageClassName: ""', then it is possible to use staic PV - ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1

Comment 1 Kenjiro Nakayama 2018-09-07 07:48:48 UTC
Proposal patch https://github.com/openshift/origin/pull/20889

Comment 8 Xingxing Xia 2018-12-03 06:41:11 UTC
Verified in v4.0.0-0.79.0. Give default sc and static pv exist, pvc is bound to the latter via --claim-class="".

Comment 11 errata-xmlrpc 2019-06-04 10:40:34 UTC
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.


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