Skip to content

Conversation

@neisw
Copy link
Contributor

@neisw neisw commented Jul 2, 2025

Reverts #2138

Opening to run payload tests while investigating OCPBUGS-58231

Narrowing down timeline for regressions to 4.20.0-0.nightly-2025-06-27-202106 and the diff show this as one of the changes.

Verified via multiple aggregate runs of

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

That the regression failure we have seen in payloads / ci / other suspected reverts is not present in these runs

: [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel] expand_less
Run #0: Failed expand_less 	5s
{  fail [github.com/openshift/origin/test/extended/authorization/scc.go:76]: 1 pods failed before test on SCC errors
Error creating: pods "event-exporter-867d8cd5d4-" is forbidden: unable to validate against any security context constraint: provider "restricted-v2": Forbidden: not usable by user or serviceaccount for ReplicaSet.apps/v1/event-exporter-867d8cd5d4 -n openshift-e2e-loki happened 11 times

Ginkgo exit error 1: exit with code 1}

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 2, 2025

@neisw: This pull request references CNTRLPLANE-72 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Reverts #2138

Opening to run payload tests while investigating OCPBUGS-58231

Narrowing down timeline for regressions to 4.20.0-0.nightly-2025-06-27-202106 and the diff show this as one of the changes.

Investigation only at the moment.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

Hello @neisw! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 2, 2025
@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/15883540-56db-11f0-8760-7a3f7eaa46e7-0

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b97dce60-572d-11f0-854d-c268ae5a4323-0

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b5370be0-574c-11f0-92ef-1b8ea8d36031-0

@neisw neisw marked this pull request as ready for review July 2, 2025 14:47
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 2, 2025
@openshift-ci openshift-ci bot requested review from deads2k and everettraven July 2, 2025 14:48
@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

Initial payload testing didn't show the scc failure. Running the aggregate job again. There is also o/k#2354 library bump revert being evaluated

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 2, 2025

@neisw: This pull request references CNTRLPLANE-72 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Reverts #2138

Opening to run payload tests while investigating OCPBUGS-58231

Narrowing down timeline for regressions to 4.20.0-0.nightly-2025-06-27-202106 and the diff show this as one of the changes.

Verified via multiple aggregate runs of

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

That the regression failure we have seen in payloads / ci / other suspected reverts is not present in these runs

: [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel] expand_less
Run #0: Failed expand_less 	5s
{  fail [github.com/openshift/origin/test/extended/authorization/scc.go:76]: 1 pods failed before test on SCC errors
Error creating: pods "event-exporter-867d8cd5d4-" is forbidden: unable to validate against any security context constraint: provider "restricted-v2": Forbidden: not usable by user or serviceaccount for ReplicaSet.apps/v1/event-exporter-867d8cd5d4 -n openshift-e2e-loki happened 11 times

Ginkgo exit error 1: exit with code 1}

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 openshift-eng/jira-lifecycle-plugin repository.

@everettraven
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: everettraven, neisw
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/label approved

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 2, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9bbe393 and 2 for PR HEAD 712062c in total

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/override ci/prow/e2e-aws-serial-2of2

job completed without failures but timed out at the very end.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-serial-2of2

In response to this:

/override ci/prow/e2e-aws-serial-2of2

job completed without failures but timed out at the very end.

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-sigs/prow repository.

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/skip

@neisw
Copy link
Contributor Author

neisw commented Jul 2, 2025

/override ci/prow/e2e-aws-serial-techpreview-2of2
/skip

see the same prometheus failure in other prs

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-serial-techpreview-2of2

In response to this:

/override ci/prow/e2e-aws-serial-techpreview-2of2
/skip

see the same prometheus failure in other prs

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-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@neisw: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit b76bb2c into openshift:master Jul 2, 2025
26 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-config-api
This PR has been included in build ose-cluster-config-api-container-v4.20.0-202507022324.p0.gb76bb2c.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants