Bug 2077592 - The MachineNotYetDeleted was fired: What to do?
Summary: The MachineNotYetDeleted was fired: What to do?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Michael McCune
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-21 16:51 UTC by Hongkai Liu
Modified: 2022-07-19 18:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-19 18:52:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Joel Speed 2022-07-14 15:34:21 UTC 
We don't currently have any runbooks for our alerts but are aware that they need to be created. We are going to create an epic to track creating these and we will prioritise that within our usual planning cycles, we have an example of one of the stories here https://issues.redhat.com/browse/OCPCLOUD-1313

Once we create the epic, we will create a card to cover this alert and close this out in favour of tracking in Jira.
Comment 2 Hongkai Liu 2022-07-15 15:01:56 UTC 
Thanks for the follow up, Joel.
Comment 3 Michael McCune 2022-07-19 18:52:24 UTC 
we have created a jira epic to track the work of creating runbooks for the machine api alerts, i am closing this bug in favor of tracking in jira.

https://issues.redhat.com/browse/OCPCLOUD-1627
Note You need to log in before you can comment on or make changes to this bug.