Skip to content

registry_pod: Avoid grace period delay#5818

Closed
avisiedo wants to merge 1 commit into
operator-framework:masterfrom
avisiedo:avoid-grace-period-for-deleting-registry-pod
Closed

registry_pod: Avoid grace period delay#5818
avisiedo wants to merge 1 commit into
operator-framework:masterfrom
avisiedo:avoid-grace-period-for-deleting-registry-pod

Conversation

@avisiedo

@avisiedo avisiedo commented May 31, 2022

Copy link
Copy Markdown

Description of the change:

Substitute shell by the last command that serve the registry pod.

Motivation for the change:

The shell script does not propagate the SIGTERM signal that is sent to
the pod when it is terminated; to avoid this, we run the last command to
substitute the shell process, so that the pod stop immediately instead of
waiting the 30 default seconds of the grace period when an user uninstall
the operator by using 'operator-sdk cleanup ...' command.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

issue: #5866

@openshift-ci openshift-ci Bot requested review from asmacdo and jmrodri May 31, 2022 07:03
@avisiedo avisiedo force-pushed the avoid-grace-period-for-deleting-registry-pod branch from f7342e3 to bed75e3 Compare May 31, 2022 07:06
The shell script does not propagate the SIGTERM signal that is sent to
the pod when it is terminated; to avoid this, we run the last command to
substitute the shell process, so that the pod stop immediately instead of
waiting the 30 default seconds of the grace period when an user uninstall
the operator by using 'operator-sdk cleanup ...' command.

Signed-off-by: Alejandro Visiedo <avisiedo@redhat.com>
@avisiedo avisiedo force-pushed the avoid-grace-period-for-deleting-registry-pod branch from bed75e3 to 4748ba5 Compare June 1, 2022 07:27
@jmrodri

jmrodri commented Jun 3, 2022

Copy link
Copy Markdown
Member

@avisiedo is there a github issue that explains the problem you were having?

@avisiedo

avisiedo commented Jun 5, 2022

Copy link
Copy Markdown
Author

@jmrodri No, there is not. What am I missing to propose a change into the repository?

  • I don't see the change as a user-facing change, as the operations and interactions are the same, just improve the time the registry_pod to terminate. Should documentation about this to be provided for the changeling anyway?
  • The same for 'website/content/en/docs', as I don't see changes into the user interaction with this change.

Please correct me on the above if I were wrong in something, and if an issue is required, let me know and I will create it, and I will update this PR to reference the issue.

Thanks

@avisiedo

avisiedo commented Jun 6, 2022

Copy link
Copy Markdown
Author

/retest

@openshift-ci

openshift-ci Bot commented Jun 6, 2022

Copy link
Copy Markdown

@avisiedo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

@avisiedo

Copy link
Copy Markdown
Author

@jmrodri In the pipeline I get here and issue related with an external link.

I have checked the link manually and it worked, probably network transitory situations; I can not relaunch the test to check it. 😅

If further changes are necessary, or an issue ticket is necessary for the change, please let me know and I will do it

Cheers! 🙂

@avisiedo

Copy link
Copy Markdown
Author

I have added an issue at: #5866

@openshift-bot

Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 12, 2022
@openshift-bot

Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 13, 2022
@openshift-bot

Copy link
Copy Markdown

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

1 similar comment
@openshift-bot

Copy link
Copy Markdown

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Nov 12, 2022
@openshift-ci

openshift-ci Bot commented Nov 12, 2022

Copy link
Copy Markdown

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants