Skip to content

Conversation

@neisw
Copy link
Contributor

@neisw neisw commented Oct 13, 2025

Aggregation failures like

Passed 1 times, failed 0 times, skipped 0 times: we require at least 6 attempts to have a chance at success name: '[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release

Likely came in with #29900 based on

<testcase name="[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release" time="0">
<failure message="had 1 non-graceful lease releases">
Oct 12 21:42:01.624 - 17s I namespace/openshift-operators node/ci-op-diyz2hf4-3db6f-xjsx2-worker-a-4c74z pod/servicemesh-operator3-55f49c5f94-jmckn uid/f130253c-5409-4cc6-8d08-99642da6d903 container/sail-operator constructed/lease-checker reason/Acquiring Waiting for lease.
</failure>
<system-out>sysout</system-out>
<system-err>syserr</system-err>
</testcase>
<testcase name="[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release" time="0"/>

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

@neisw: This pull request explicitly references no jira issue.

In response to this:

Aggregation failures like

Passed 1 times, failed 0 times, skipped 0 times: we require at least 6 attempts to have a chance at success name: '[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release

Likely came in with #29900 based on

<testcase name="[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release" time="0">
<failure message="had 1 non-graceful lease releases">
Oct 12 21:42:01.624 - 17s I namespace/openshift-operators node/ci-op-diyz2hf4-3db6f-xjsx2-worker-a-4c74z pod/servicemesh-operator3-55f49c5f94-jmckn uid/f130253c-5409-4cc6-8d08-99642da6d903 container/sail-operator constructed/lease-checker reason/Acquiring Waiting for lease.
</failure>
<system-out>sysout</system-out>
<system-err>syserr</system-err>
</testcase>
<testcase name="[Monitor:lease-checker][sig-arch] all leases in ns/openshift-operators must gracefully release" time="0"/>

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 requested review from deads2k and sjenning October 13, 2025 00:11
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@neisw
Copy link
Contributor Author

neisw commented Oct 13, 2025

/payload-aggregate periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade 10

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 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-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/49a858c0-a7c9-11f0-86f5-fc5544776487-0

@stbenjam
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2025
@stbenjam
Copy link
Member

/verified bypass

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 13, 2025
@openshift-ci-robot
Copy link

@stbenjam: The verified label has been added.

In response to this:

/verified bypass

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-merge-bot openshift-merge-bot bot merged commit 86d83ea into openshift:main Oct 13, 2025
19 of 20 checks passed
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants