Skip to content

Conversation

neisw
Copy link
Contributor

@neisw neisw commented Aug 25, 2025

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2025
@openshift-ci-robot
Copy link

@neisw: This pull request references Jira Issue OCPBUGS-60564, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Reverts #450

Failures seen in pr /payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10 are now seen in payloads.

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.

@neisw neisw force-pushed the revert-450-add-webhook-tolerance-test branch from e8cf45e to 9068488 Compare August 25, 2025 09:47
@dgoodwin
Copy link

/lgtm

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

tmshort commented Aug 25, 2025

@neisw, I'm not seeing a failure of this test in the provided link; in fact the test is listed in the "Tests Pass" (not that those seem to matter, given 0s run time).
I'm seeing:

time="2025-08-20T18:59:21.010Z" level=info msg="  checking openshift-operator-framework-operator-controller-450-ci-4.20-e2e-gcp-ovn-techpreview-serial/1957950009433395200 for matchID match: looking for \"b82e044755bdef8727b52b940dd602a6c9233a682279d9849fd3a971\" found \"fc44c9e55c5d29c72260804b90625d2439ce3aa0fea5907e317a7815\"."

Which seems like a build problem? I'm not clear on the reasoning for that error or this revert.

@tmshort
Copy link
Contributor

tmshort commented Aug 25, 2025

Note: The prefix for this commit is UPSTREAM: <drop>, that means this commit will be dropped the next time we sync from upstream (which would be in the next day or two); I'm not sure you want that to happen (meaning the revert will be "reverted").

Copy link
Contributor

openshift-ci bot commented Aug 25, 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.

@neisw
Copy link
Contributor Author

neisw commented Aug 25, 2025

@tmshort it isn't that the test is failing but that it is causing other failures. Sippy intervals can help show that but also the PR being reverted had these failures in the payload jobs used for verification.

…tion test, mirroring the logic used in the certificate rotation test. This makes the test more robust by ensuring a new secret is created, not just that an existing one is still present.

This reverts commit 0bb1953.

UPSTREAM: <carry>: [OTE] Add webhook to validate openshift-service-ca certificate rotation

This reverts commit e9e3220.
@neisw neisw force-pushed the revert-450-add-webhook-tolerance-test branch from 9068488 to 7ff0655 Compare August 25, 2025 14:29
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2025
@tmshort
Copy link
Contributor

tmshort commented Aug 25, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2025
@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-60564, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

In response to this:

/jira refresh

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.

@tmshort
Copy link
Contributor

tmshort commented Aug 25, 2025

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 2

@tmshort
Copy link
Contributor

tmshort commented Aug 25, 2025

/lgtm

Copy link
Contributor

openshift-ci bot commented Aug 25, 2025

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

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0c0104f0-81c1-11f0-8ae5-ba8b9934ac5c-0

@tmshort
Copy link
Contributor

tmshort commented Aug 25, 2025

/approve

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

openshift-ci bot commented Aug 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, tmshort

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 25, 2025
@neisw
Copy link
Contributor Author

neisw commented Aug 25, 2025

/override ci/prow/e2e-aws-techpreview-olmv1-ext
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/openshift-e2e-aws
/override ci/prow/openshift-e2e-aws-techpreview
/skip

passed previously but had to update the commit message

Copy link
Contributor

openshift-ci bot commented Aug 25, 2025

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-techpreview-olmv1-ext, ci/prow/okd-scos-e2e-aws-ovn, ci/prow/openshift-e2e-aws, ci/prow/openshift-e2e-aws-techpreview

In response to this:

/override ci/prow/e2e-aws-techpreview-olmv1-ext
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/openshift-e2e-aws
/override ci/prow/openshift-e2e-aws-techpreview
/skip

passed previously but had to update the commit message

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-merge-bot openshift-merge-bot bot merged commit 9b50498 into openshift:main Aug 25, 2025
13 checks passed
@openshift-ci-robot
Copy link

@neisw: Jira Issue OCPBUGS-60564: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-60564 has not been moved to the MODIFIED state.

In response to this:

Reverts #450

Failures seen in pr /payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10 are now seen in payloads.

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.

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants