Bug 1547884
Summary: | Storage class "Retain" reclaim policy does not work on nfs/ efs / cephFS-provisioner | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenqi He <wehe> |
Component: | Storage | Assignee: | Tomas Smetana <tsmetana> |
Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, aos-storage-staff, bchilds, chaoyang, hchiramm, jhou, lxia, smunilla, tsmetana, xtian |
Target Milestone: | --- | Keywords: | Rebase |
Target Release: | 3.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-external-storage-0.0.2-1.gitd3c94f0.el7 | Doc Type: | Known Issue |
Doc Text: |
Cause:
The external NFS and EFS provisioners do not respect the ReclaimPolicy of volume StorageClass.
Consequence:
The dynamically provisioned NFS and EFS volumes can only have the default "Delete" ReclaimPolicy.
Workaround (if any):
N/A
Result:
The NFS and EFS external provisioners would provision new volumes having the default (i.e. "Delete") policy ignoring the ReclaimPolicy of the volume's StorageClass.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-30 19:09:51 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
Wenqi He
2018-02-22 08:26:53 UTC
EFS has same issue. I will try to backport the upstream patchs that fixed this: https://github.com/kubernetes-incubator/external-storage/pull/419/commits/48b796d4a1d587adf1abe49ebff4119df24c7aba However it is possible the patch might require updating the dependencies which equals to rebasing the package. That's probably something we should avoid at this stage. (In reply to Tomas Smetana from comment #2) > I will try to backport the upstream patchs that fixed this: > > https://github.com/kubernetes-incubator/external-storage/pull/419/commits/ > 48b796d4a1d587adf1abe49ebff4119df24c7aba > > However it is possible the patch might require updating the dependencies > which equals to rebasing the package. That's probably something we should > avoid at this stage. Tomas, ideally its not required to backport it. If you can retrigger or create new containers of EFS and NFS containers in external storage repo, it should be supported by default. (In reply to Humble Chirammal from comment #3) > (In reply to Tomas Smetana from comment #2) > > I will try to backport the upstream patchs that fixed this: > > > > https://github.com/kubernetes-incubator/external-storage/pull/419/commits/ > > 48b796d4a1d587adf1abe49ebff4119df24c7aba > > > > However it is possible the patch might require updating the dependencies > > which equals to rebasing the package. That's probably something we should > > avoid at this stage. > > > Tomas, ideally its not required to backport it. If you can retrigger or > create new containers of EFS and NFS containers in external storage repo, it > should be supported by default. We can take help from Brad or Jan to trigger upstream containers, it should have this support. Otherwise if you can get the latest tar ball from upstream ( https://github.com/kubernetes-incubator/external-storage/releases) and if we can trigger downstream containers from it, it will also solve this problem. That's the problem: we need to ship containerized version of the code we tested. And that is definitely not the recent upstream: we either backport or just live with the fact there are known issues. And I'm afraid it's going to be the second case here. Changing target release to 3.10.0, adding "Rebase" keyword. Summary: The following external provisioners we support has this problem - NFS - EFS - CephFS Tested on below version: # oc version openshift v3.10.0-0.46.0 kubernetes v1.10.0+b81c8f8 This issue still repro on NFS and EFS provisioner. NFS provisioner works from my today's testing, I used the image v1.0.9, will continue to test EFS tomorrow. Thanks. We have tested on below version: openshift v3.10.0-0.66.0 kubernetes v1.10.0+b81c8f8 # uname -a Linux wehe-master-etcd-nfs-1 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.5 (Maipo) "Retain" reclaim policy works on NFS/EFS/CephFS provsioner. And we have separated email to track the image tag issue. Thanks Thank you. I'm myself not totally sure about the correct versioning. I will try to find somebody who could shed some light into this. 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/RHBA-2018:1816 |