Bug 1798759
Summary: | Provide a way to use iSCSI persistent volumes for the Image Registry | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jose Kaz C R <jcasimir> | |
Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> | |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.3.0 | CC: | adam.kaplan, aos-bugs, mfuruta, rh-container, susuresh, tschaibl | |
Target Milestone: | --- | |||
Target Release: | 4.4.0 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: the image-registry was using RollingUpdate strategy that is not compatible with RWO volumes
Consequence: RWO volumes couldn't be used
Fix: allow to pick the deployment strategy
Result: the image-registry can be deployed with RWO volumes in non-high-available configurations (i.e. with only 1 replica)
|
Story Points: | --- | |
Clone Of: | ||||
: | 1799447 (view as bug list) | Environment: | ||
Last Closed: | 2020-05-04 11:34:08 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1799447 |
Description
Jose Kaz C R
2020-02-05 22:17:14 UTC
We have an existing RFE for this use case [1] and are adding a feature in OCP 4.4 that will enable it [2]. Using RWO is possible by bringing your own PVC and backing volume [3] - however the current rollout strategy for the registry's deployment prevents the volume from being mounted during upgrade. The new feature will allow admins to set the rollout strategy to "Recreate", which allows the RWO PV to be mounted into the new registry pod on upgrade. [1] https://issues.redhat.com/browse/RFE-489 [2] https://issues.redhat.com/browse/DEVEXP-523 [3] https://docs.openshift.com/container-platform/4.3/registry/configuring-registry-storage/configuring-registry-storage-baremetal.html#registry-configuring-storage-baremetal_configuring-registry-storage-baremetal This was fixed and verified by https://issues.redhat.com/browse/DEVEXP-523. Do you want to have it backported to 4.3? (In reply to Oleg Bulatov from comment #3) > This was fixed and verified by https://issues.redhat.com/browse/DEVEXP-523. > > Do you want to have it backported to 4.3? Yes, please. Since that's the version that is actually out. Thank you, very much in advance. Verified on 4.4.0-0.nightly-2020-02-06-230833: $ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE registrypvc Bound pvc-b933321c-244f-41af-bad1-876544d1e9ad 1Gi RWO iscsi-targetd-vg-targetd 15m $ oc get pods NAME READY STATUS RESTARTS AGE cluster-image-registry-operator-df4ccc5c9-jzhnj 2/2 Running 0 121m image-registry-5b75d4844d-pqdpk 1/1 Running 0 12m node-ca-8dhdb 1/1 Running 0 118m node-ca-9bh7d 1/1 Running 0 118m node-ca-kllc4 1/1 Running 0 118m node-ca-knzln 1/1 Running 0 121m node-ca-nnxqs 1/1 Running 0 121m node-ca-p5494 1/1 Running 0 121m 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-2020:0581 |