OCPBUGS-98586: Don't wait on oc delete in konnectivity_cleanup#10682
OCPBUGS-98586: Don't wait on oc delete in konnectivity_cleanup#10682bfournie wants to merge 1 commit into
Conversation
Remove the wait on the 'oc delete namespace' command in konnectivity_cleanup. The namespace deletion request will be submitted but oc delete won't block waiting for finalization to complete. bootkube.sh proceeds immediately to touch /opt/openshift/.bootkube.done, unblocking report-progress.sh and the rest of the bootstrap chain. The namespace will eventually be cleaned up by the namespace controller once the conversion webhook becomes available (or the CRDs are removed). There's no functional reason to wait for it synchronously — the bootstrap konnectivity resources just need to be requested for deletion, not fully finalized, before bootkube can move on.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@bfournie: This pull request references Jira Issue OCPBUGS-98586, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/hold |
📝 WalkthroughWalkthroughThe Konnectivity cleanup script now deletes the bootstrap namespace without waiting for completion, while retaining ChangesKonnectivity cleanup
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/test ? |
|
@bfournie: This pull request references Jira Issue OCPBUGS-98586, which is valid. 3 validation(s) were run on this 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test e2e-agent-compact-ipv4-iso-no-registry |
|
/test e2e-aws-ovn-techpreview |
|
@bfournie: The following tests 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-sigs/prow repository. I understand the commands that are listed here. |
Remove the wait on the
oc delete namespace command in konnectivity_cleanup. The namespace deletion request will be submitted but oc delete won't block waiting for finalization to complete. bootkube.sh proceeds immediately to touch/opt/openshift/.bootkube.done, unblockingreport-progress.shand the rest of the bootstrap chain.The namespace will eventually be cleaned up by the namespace controller once the conversion webhook becomes available (or the CRDs are removed). There's no functional reason to wait for it synchronously — the bootstrap konnectivity resources just need to be requested for deletion, not fully finalized, before bootkube can move on.
Summary by CodeRabbit