NO-JIRA: Extend project deletion timeout #30393
Conversation
Analysis of audit logs / namespace controller shows succesful deletion 6 minutes after DELETE API. The namespace controller is extremely active with other activity during this period.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jupierce, smg247 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 |
openshift-ci
bot
added
the
approved
|
/retitle NO-JIRA: Extend project deletion timeout |
|
/verified bypass |
openshift-ci
bot
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@jupierce: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
verified
|
@stbenjam: The 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jupierce: The following test 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-sigs/prow repository. I understand the commands that are listed here. |
openshift-merge-bot
bot
merged commit 4faf768
into
openshift:main
4 participants
Analysis of audit logs / namespace controller shows succesful deletion 6 minutes after DELETE API. The namespace controller is extremely active with other activity during this period.