Description of problem: The image in ocp3.10 now is openshift3/efs-provisioner The name is different with ocpv3.7 and ocpv3.9 Version-Release number of selected component (if applicable): openshift v3.10.45-2 How reproducible: Always Steps to Reproduce: 1.Install OCP310 2.Pull image openshift3/efs-provisioner:v3.10.45-2 Actual results: The image openshift3/efs-provisioner pulled successfully Expected results: The image should named openshift3/ose-efs-provisioner Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
The description speaks of OSE 3.10... So I assume the correct target is 3.10.z. Second thing I completely don't understand: why is this blocking the 3.11 bug? Where does the dependency come from?
Bug #630127 is cloned from this #1629579, maybe it is "block" come from.
In 3.9 there is an efs-provisioner dockerfile: https://github.com/openshift/external-storage/tree/release-3.9/images/efs-provisioner This is not present in 3.10. THere is no 3.11 branch and the images/efs-provisioner directory does not exist on master.
Dockerfile for the 3.10 branch (taken from 3.9): https://github.com/openshift/external-storage/pull/4
Will re-test. Is it also in master, and so 3.11/4.0?
The master branch is not diverging from upstream (intentionally). So we need to create the additional branches (release-3.11 and release-4.0). I'll check with the team lead just to be sure.
Checked that ose-efs-provisioner:v3.10 and v3.10.x exist on reg-aws and stage registry. Move bug to verified.
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-2018:2709