https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-release-openshift-origin-installer-e2e-aws-4.5-cnv/71 Seeing the error "step e2e-aws failed: step needs a lease but no lease client provided" over the past few days in canary-release-openshift-origin-installer-e2e-aws-4.5-cnv
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-release-openshift-origin-installer-e2e-aws-4.5-cnv/74
This is a user's misconfiguration of their job. Please configure your jobs appropriately. Please see other jobs for how to set flags: https://github.com/openshift/release/blob/161b3cfcb306abe34c30d8b54ed158e9a272ba63/ci-operator/jobs/openshift/aws-ebs-csi-driver-operator/openshift-aws-ebs-csi-driver-operator-master-presubmits.yaml#L24-L26 And how to mount the credentials: https://github.com/openshift/release/blob/161b3cfcb306abe34c30d8b54ed158e9a272ba63/ci-operator/jobs/openshift/aws-ebs-csi-driver-operator/openshift-aws-ebs-csi-driver-operator-master-presubmits.yaml#L52-L54 https://github.com/openshift/release/blob/161b3cfcb306abe34c30d8b54ed158e9a272ba63/ci-operator/jobs/openshift/aws-ebs-csi-driver-operator/openshift-aws-ebs-csi-driver-operator-master-presubmits.yaml#L71-L76
sorry wrong component ... will fix momentarily
putting this under the "Build" component for now, but really it's a CI job definition problem. (See https://bugzilla.redhat.com/show_bug.cgi?id=1828401#c2)
*** Bug 1829069 has been marked as a duplicate of this bug. ***
Roman, do you have an idea about this bug?
I fixed this for you here: https://github.com/openshift/release/pull/8977/files#diff-c5125c8ba8a5219585f189ff63f8cd2bR5599
can see at least a few recent passes here: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.5-informing#canary-release-openshift-origin-installer-e2e-aws-4.5-cnv
Setting version, target and priority QE were not involved in this bug, so if some of the data is incorrect, please feel free to change my settings, but priority was set to low because CNV is aimed for BM, ocp4.5 should work with cnv2.4, so adjusted the version and since it was verified, i assume it is working with 2.4
yes the issue here had nothing to do w/ CNV itself, it was a CI job configuration problem which has been fixed, so the CNV version is irrelevant.
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-2020:3194