Description of problem: Verify job doesn't check if vendor directory was updated correctly. This is a problem because upstream doesn't have a vendor directory, and usually after every rebase the go.mod file changes. This breaks our CI and we don't notice it. How reproducible: Always. Steps to Reproduce: 1. Update go.mod without running "go mod vendor" 2. Submit the changes to openshift/aws-ebs-csi-driver 2. Verify job will pass Actual results: Verify job in CI will pass. Expected results: Verify job detects there are inconsistencies in vendor dir and fail.
The following PRs were submitted: - https://github.com/openshift/aws-ebs-csi-driver/pull/166 - introduces the changes in the aws-ebs-csi-driver repo. - https://github.com/openshift/release/pull/11615 - introduces the change in the release repo.
From log: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_aws-ebs-csi-driver/172/pull-ci-openshift-aws-ebs-csi-driver-master-verify/1336872009929330688/artifacts/build-logs/src.log, we can see vendor dir sanity is checked and passed.
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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:5633