Skip to content

Conversation

@tchap
Copy link
Contributor

@tchap tchap commented Sep 19, 2025

This is in preparation of proper signal handling.

Split from #2062

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 19, 2025
@openshift-ci-robot
Copy link

@tchap: This pull request references Jira Issue OCPBUGS-59311, which is valid.

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

Requesting review from QA contact:
/cc @zhouying7780

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

In response to this:

This is in preparation of proper signal handling.

Split from #2062

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.

@tchap
Copy link
Contributor Author

tchap commented Sep 21, 2025

/retest

The former queue implementation is deprecated.
When the temporary must-gather role binding fails to be created, no
namespace cleanup function is returned and the namespace is left behind.
This is now fixed by returning the namespace cleanup function on error.
Currently defer queue.Done(pod) is called in a worker thread loop,
which means that the pod is marked as done when the whole worker thread
exits and not in that pod processing loop iteration.

This is now fixed and the pod is marked as processed as soon as it is
actually processed.
@tchap tchap force-pushed the must-gather-use-context branch from eb52134 to 47bf325 Compare September 22, 2025 11:43
This is in preparation of proper signal handling.
@tchap tchap force-pushed the must-gather-use-context branch from 47bf325 to 6a2ebc9 Compare September 22, 2025 11:44
@tchap
Copy link
Contributor Author

tchap commented Sep 22, 2025

@ardaguclu Split into multiple commits as requested.

@ardaguclu
Copy link
Member

That is nice! Thank you
/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 22, 2025
@ardaguclu
Copy link
Member

/retest

@ardaguclu
Copy link
Member

The CI results are not in a good shape (maybe unrelated?). But we need to be sure that.
/lgtm cancel
until we confirm that there is no issue

@openshift-ci openshift-ci bot removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 23, 2025
@tchap
Copy link
Contributor Author

tchap commented Sep 23, 2025

Yeah, I don't think it's us, because before I did the commit split, everything was green AFAIK.

@ardaguclu
Copy link
Member

/lgtm

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

openshift-ci bot commented Sep 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, tchap

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 Sep 23, 2025
@tchap
Copy link
Contributor Author

tchap commented Sep 23, 2025

/retest

1 similar comment
@ardaguclu
Copy link
Member

/retest

@ardaguclu
Copy link
Member

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

@tchap: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-certrotation 6a2ebc9 link false /test e2e-aws-certrotation

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.

@tchap
Copy link
Contributor Author

tchap commented Sep 25, 2025

/verified by @tchap

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 25, 2025
@openshift-ci-robot
Copy link

@tchap: This PR has been marked as verified by @tchap.

In response to this:

/verified by @tchap

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 abe2393 into openshift:main Sep 25, 2025
17 of 18 checks passed
@openshift-ci-robot
Copy link

@tchap: Jira Issue OCPBUGS-59311: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

All associated pull requests must be merged or 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-59311 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

In response to this:

This is in preparation of proper signal handling.

Split from #2062

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.

@tchap tchap deleted the must-gather-use-context branch September 25, 2025 09:32
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-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. 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