Bug 1792498

Summary: No delete node action in console [openshift-4.4]
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: Management ConsoleAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, calfonso, jokerman, xiaocwan
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:25:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Warning info when deleting node none

Description Clayton Coleman 2020-01-17 18:16:06 UTC 
From node details page you cannot delete a node.

Deleting a node comes with some consequences that we need to communicate to users, so deleting nodes should have a form like deleting projects where you are warned about the implications, then required to do something abnormal.

The text should read:

This action cannot be undone. Deleting a node will instruct Kubernetes that the node is down or unrecoverable and delete all pods scheduled to that node. If the node is still running but unresponsive and the node is deleted, stateful workloads and persistent volumes may suffer corruption or data loss. Only delete a node that you have confirmed is completely stopped and cannot be restored.
Comment 2 XiaochuanWang 2020-02-07 10:08:47 UTC 
Created attachment 1661646 [details]
Warning info when deleting node
Comment 3 XiaochuanWang 2020-02-07 10:10:30 UTC 
Warning message shows up when user trying to delete node on nodes list page or node detail kebab.
Attached the message screenshot.
Verified on 4.4.0-0.nightly-2020-02-05-220946
Comment 5 errata-xmlrpc 2020-05-04 11:25:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581