Bug 1767954
| Summary: | openshift/api verify job not catching missing regens | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> |
| Component: | kube-apiserver | Assignee: | Mike Dame <mdame> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, maszulik, mfojtik |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 11:10:26 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: | |||
|
Description
Ben Parees
2019-11-01 17:51:33 UTC
Oh, looks like I forgot to add any sort of regen checking to the verify script (https://github.com/openshift/api/blob/master/hack/verify-crds.sh)... will fix Hi, not sure what issue this bug caused and not clear how to verify, could you share some hint? Thx This was an issue with a CI job on the openshift/api repository in which the verify job didn't properly confirm that the PR included regenerated code. I don't think QE needs to verify it, i'd rely on the developer who fixed the job to verify it manually (such as by submitting a PR that does not include regenerated code and confirming the verify job reports a failure). I opened a test PR here: https://github.com/openshift/api/pull/514 Which successfully failed (hah) as expected: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_api/514/pull-ci-openshift-api-master-verify/1487 With that, I'm going to verify this manually as you said. Thanks! 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:0062 |