-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.8] Bug 1975078: Gracefully shutdown taking around 6-7 mins (libvirt provider) #2636
[release-4.8] Bug 1975078: Gracefully shutdown taking around 6-7 mins (libvirt provider) #2636
Conversation
The machine-config-daemon gets stuck blocking SIGTERM on rebootless updatesbecause it only removes its SIGTERM protection when it reboots or when it encounters an error in the triggerUpdateWithmachineConfig-> update->performPostConfigChangeAction cycle. This changes the behavior such that it will remove the protection on a successful rebootless update and adds some logging messages so it's more clear when it starts and stops protecting itself.
@openshift-cherrypick-robot: Bugzilla bug 1965992 has been cloned as Bugzilla bug 1975078. Retitling PR to link against new bug. In 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 kubernetes/test-infra repository. |
@openshift-cherrypick-robot: This pull request references Bugzilla bug 1975078, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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 kubernetes/test-infra repository. |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, sinnykumari 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
11 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@sinnykumari It is quite critical for us (CRC side) to move forward, right now we are using a hack as workaround which is suggested on the original BZ ( Deleting the MCD pods just before shutdown). We really want to avoid those hack on CRC side which are issues on openshift and fixed. Also I tested 4.9 nightly which have this fix and it worked. I would like to have it as part of 4.8 release side instead of any z stream so we can also ship CRC with 4.8 without any hacky workaround. |
I understand your concern, but since we are close to 4.8 going GA, to avoid any regression only critical bugs get approved from group lead and this bug severity is marked as medium. If you still think it should be merged in 4.8 GA instead of waiting for z stream, it would require priority escalation from CRC team. |
I agree with what Sinny said. 4.8 is already past final freeze, so we cannot merge any code into 4.8.0 anymore barring extraordinary circumstances |
@sinnykumari since we need approval for this to merge, I think we can remove the hold now? WDYT |
PR is already approved, it doesn't have group-lead approval but that doesn't prevent bot to keep retesting. Hold is mainly to keep bot away 😆 |
Since, all failed tests have completed, hopefully skip will work as expected now |
/hold cancel |
Re-validating bugzilla status after prow config updates. |
@sdodson: This pull request references Bugzilla bug 1975078, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: In 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 kubernetes/test-infra repository. |
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
1 similar comment
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window. skipped
NOTE: This message was automatically generated, if you have questions please ask on #forum-release |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@openshift-cherrypick-robot: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: Bugzilla bug 1975078 has been moved to the MODIFIED state. In 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 kubernetes/test-infra repository. |
This is an automated cherry-pick of #2631
/assign praveenkumar