Bug 985679 - Documentation does not mention force-delete action for oo-admin-ctl-domain
Summary: Documentation does not mention force-delete action for oo-admin-ctl-domain
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 1.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Bilhar
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-18 04:40 UTC by Miciah Dashiel Butler Masters
Modified: 2017-03-08 17:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-27 04:01:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Miciah Dashiel Butler Masters 2013-07-18 04:40:22 UTC
Description of problem:
In Section 3.3. "Removing User Data" of the Administration Guide, the force-delete action for oo-admin-ctl-domain should be mentioned for those hard-to-kill applications.


Version-Release number of selected component (if applicable):
OpenShift Enterprise Administration Guide Edition 1.2


How reproducible:
Completely.


Steps to Reproduce:
1. Read Section 3.3, Procedure 3.4, Step 3.


Actual results:
I see the following command:

    # oo-admin-ctl-app -l username -a app1 -c destroy


Expected results:
In addition to the destroy command that is already there, I should also see the following command in the same step or in a new, subsequent step:

    # oo-admin-ctl-app -l username -a app1 -c force-destroy

The guide should explain that the force-destroy action may be needed for particularly pesky applications that can't be destroyed without force.


Additional info:
I am referencing the Administration Guide using the following URL:

https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/1/html-single/Administration_Guide/index.html#sect-OpenShift_Enterprise-Administration_Guide-Removing_User_Data


Note You need to log in before you can comment on or make changes to this bug.