Bug 1679215 - Deletion of master machine has no automatic recovery
Summary: Deletion of master machine has no automatic recovery
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.1.0
Assignee: Luis Sanchez
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1664187
TreeView+ depends on / blocked
 
Reported: 2019-02-20 15:42 UTC by Steven Walter
Modified: 2024-01-06 04:26 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-29 13:33:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1679215 0 high CLOSED Deletion of master machine has no automatic recovery 2024-01-06 04:26:06 UTC
Red Hat Knowledge Base (Solution) 3928181 0 None None None 2019-02-20 15:51:18 UTC

Internal Links: 1679215 1679772

Description Steven Walter 2019-02-20 15:42:09 UTC 
Description of problem:
You can delete master machine. As they are not controlled by any controller, there is no defined method of recovery.

Version-Release number of selected component (if applicable):
4.0

How reproducible:
100%

Steps to Reproduce:
1.
$ oc delete machine example-master-0

Actual results:
Machine not recreated

Expected results:
Machine recreated -- or documentation on how to manually recreate it

Additional info:
openshift beta list: "What happens when you delete master machine?"
Comment 2 Eric Rich 2019-02-21 20:06:05 UTC 
A solution to this issue might be to protect the AWS resources: https://bugzilla.redhat.com/show_bug.cgi?id=1679772
Comment 5 Stephen Cuppett 2019-03-27 11:00:20 UTC 
JIRA here: https://jira.coreos.com/browse/MSTR-336
Comment 9 Red Hat Bugzilla 2024-01-06 04:26:07 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.