Description of problem: Image snapshot-controller is using old api. While image snapshot-provisioner does not have such issue. And package snapshot-controller, snapshot-provisioner does not have such issue. Version-Release number of selected component (if applicable): "Id": "sha256:e8dfcff0a6567f8a647c6742c83360629c0674410280927af81ee65a031f8be7" # docker exec -it snapshot-controller bash -c 'rpm -qa | grep snapshot' openshift-external-storage-snapshot-controller-0.0.1-3.git78d6339.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Check the latest image of snapshot-controller. Actual results: # oc create -f snapshot1.yaml (with apiVersion: volumesnapshot.external-storage.k8s.io/v1) error: unable to recognize "snapshot.yaml": no matches for volumesnapshot.external-storage.k8s.io/, Kind=VolumeSnapshot # oc create -f snapshot2.yaml (with apiVersion: volume-snapshot-data.external-storage.k8s.io/v1) volumesnapshot "snapshot-1" created Expected results: We should use newer api as "volumesnapshot.external-storage.k8s.io/v1" Additional info: # cat snapshot.yaml apiVersion: volumesnapshot.external-storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: snapshot-1 namespace: 43iv1 spec: persistentVolumeClaimName: pvc
Rebuilt the image with the new openshift-external-storage-snapshot-controller.x86_64 0:0.0.1-5.git78d6339.el7 package: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14558950
Verified that the new images works fine. # docker exec -it 7fbf4a788c1e bash -c 'rpm -qa | grep snapshot' openshift-external-storage-snapshot-controller-0.0.1-5.git78d6339.el7.x86_64 # oc create -f ss.yaml volumesnapshot "snapshot-1" created # cat ss.yaml apiVersion: volumesnapshot.external-storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: snapshot-1 spec: persistentVolumeClaimName: pvc
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-2017:3188