Bug 1683019 - [DOCS] Destroy cluster without a metadata.json file
Summary: [DOCS] Destroy cluster without a metadata.json file
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Kathryn Alexander
QA Contact: Johnny Liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-26 05:48 UTC by Johnny Liu
Modified: 2019-09-13 20:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-20 12:59:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Johnny Liu 2019-02-26 05:48:22 UTC 
Document URL: 
https://docs.openshift.com/container-platform/4.0/installing-aws/uninstalling-cluster-aws.html

Section Number and Name: 
Uninstalling a cluster on AWS

Describe the issue: 
There is a KCS to deal with "Destroy cluster without a metadata.json file" scenario, but ocp document do not have such document.

https://access.redhat.com/solutions/3826921 

Suggestions for improvement: 
Move the KCS to OCP document as a sub-section in "Uninstalling a cluster on AWS" chapter.

Additional information:
Comment 1 Kathryn Alexander 2019-02-28 21:12:03 UTC 
PR's here: https://github.com/openshift/openshift-docs/pull/13903

Jianlin Liu, will you please review?
Comment 2 Johnny Liu 2019-03-01 07:49:12 UTC 
Most part looks good to me, leave some minor comments.
Comment 3 Kathryn Alexander 2019-03-01 17:01:23 UTC 
Thank you for the comments! I've made more changes - will you please take another look?
Comment 4 Johnny Liu 2019-03-06 07:52:24 UTC 
Resolution provided by dev for BZ#1685089 still have some issues, pls follow up the bug discussion, hold on this PR merge until we have a final solution.
Comment 7 Kathryn Alexander 2019-05-20 12:59:17 UTC 
Per Vikram, I'm deferring this bug until https://bugzilla.redhat.com/show_bug.cgi?id=1685089 is resolved.
Note You need to log in before you can comment on or make changes to this bug.