Bug 1071443

Summary:	3.6. Recovering Failed Node Hosts
Product:	OpenShift Container Platform	Reporter:	Aaron Weitekamp <aweiteka>
Component:	Documentation	Assignee:	Julie <juwu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.0.0	CC:	bleanhar, jokerman, libra-onpremise-devel, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 20822, Administration Guide-2-1.0 Build Date: 27-02-2014 09:56:50 Topic ID: 20758-593082 [Latest]
Last Closed:	2014-07-06 23:31:55 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:

Description Aaron Weitekamp 2014-02-28 19:51:10 UTC

Title: Recovering Failed Node Hosts
Procedure 3.4. To Recover a Failed Node Host
step 3b should use '-d' instead of '-l'
ls -d -n /var/lib/openshift/UUID

Describe the issue:
The value we want (4th value) is '6692' but this isn't clear from the output.

[root@node2 ~]# ls -l -n /var/lib/openshift/530fbdbdad4c3bcb4900001b
total 24
drwxr-xr-x.  4 6692 6692 4096 Feb 27 17:35 app-deployments
drwxr-xr-x.  4    0 6692 4096 Feb 27 17:35 app-root
drwxr-xr-x.  2    0    0 4096 Feb 27 17:36 gear-registry
drwxr-xr-x.  3    0    0 4096 Feb 27 17:35 git
drwxr-xr-x. 11 6692 6692 4096 Feb 27 17:35 haproxy
drwxr-xr-x. 14 6692 6692 4096 Feb 27 17:35 ruby


Suggestions for improvement:
[root@node2 ~]# ls -d -n /var/lib/openshift/530fbdbdad4c3bcb4900001b
drwxr-x---. 16 0 6692 4096 Feb 27 17:35 /var/lib/openshift/530fbdbdad4c3bcb4900001b

This method is also more script friendly.


Additional information:

Comment 7 Julie 2014-07-06 23:31:55 UTC

Re comment5, updated 1.x content spec to include [29446].
Won't fix commands in [29446] step1 and step3 as could not get info. Please file a new bug if you think the fixes from this bug is not sufficient.