[release-4.9] Bug 2101429: test: switch to testing CapBnd over CapInh#27279
Conversation
|
@openshift-cherrypick-robot: Bugzilla bug 2076265 has been cloned as Bugzilla bug 2101429. Retitling PR to link against new bug. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2101429, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest-required |
|
@ashcrow PTAL, this will unbreak 4.9 CI/promotion |
|
/approve |
|
/lgtm |
|
/label backport-risk-assessed |
|
@rphillips: Can not set label backport-risk-assessed: Must be member in one of these teams: [] DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Is the "ci/prow/okd-e2e-gcp — Job failed." a valid concern? |
|
/retest |
|
the test seems not to have provisioned, so I don't think it's related to this PR |
|
/retest |
|
Hmm, maybe I didn't wait long enough, because we failed the same way. Checking the ingress operator: $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/27279/pull-ci-openshift-origin-release-4.9-okd-e2e-gcp/1544792718503317504/artifacts/release/artifacts/release-payload-latest/image-references | jq -r '.spec.tags[] | select(.name == "cluster-ingress-operator").annotations["io.openshift.build.commit.id"]'
b59abfcd5bdebcad518ed7bb1ec3581a551c086eAnd yeah, we're hoping for openshift/cluster-ingress-operator@9dbf3af5cb7fcc9. Try again: /retest |
as CRI-O will soon drop CapInh, see GHSA-4hj2-r2pm-3hc6 and CVE-2022-27652 Signed-off-by: Peter Hunt <pehunt@redhat.com>
00aaa7c to
6d05174
Compare
|
Updated the commit hash to retrigger the CI jobs with hopefully the latest cluster-ingress-operator. |
Did we get a confirmation from TP that this is necessary? I guess this situation is somewhat rare, but it's a bit surprising that a retest wouldn't pick up new images from other parts of the payload, when newer images exist. (At a minimum at some point i'd expect the old NS to be deleted and thus the retest, even if it reuses the NS name/hash, would re-import the images and get new versions, but i'm not sure how long the NSes live for) |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, mrunalp, openshift-cherrypick-robot, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Update run failed on the unrelated /test e2e-gcp-upgrade |
|
@openshift-cherrypick-robot: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: Bugzilla bug 2101429 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherry-pick release-4.8 |
|
@haircommander: new pull request created: #27306 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is an automated cherry-pick of #27021
/assign haircommander