Bug 875657

Summary:	[US3036]Some format errors in the prompt message when executing "oo-admin-ctl" and "oo-accept-*"
Product:	OpenShift Container Platform	Reporter:	xjia <xjia>
Component:	Node	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED ERRATA	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.2.0	CC:	bleanhar, jkeck, lmeyer, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-31 20:32:34 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 xjia 2012-11-12 10:12:46 UTC

Description of problem:
1. The prompt message is not aligned
[root@broker broker]# oo-admin-chk 
Check failed.
 FAIL - PUBLIC_IP 127.0.0.1 should be public, not localhost
FAIL - multiple node hosts have public_hostname node1.example.com: node.example.com,node1.example.com

2. The format is "FAIL -" when execute "oo-admin-chk", but the format is "FAIL: " when execute "oo-accept-*".  It will be better if the format is the same.


Version-Release number of selected component (if applicable):
http://download.lab.bos.redhat.com/rel-eng/OpenShiftEnterprise/1.0/2012-11-10.1


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Luke Meyer 2012-12-13 19:28:04 UTC

Most of this functionality was moved to oo-accept-systems, leaving oo-admin-chk to just check gear consistency.

What remains consistently says "FAIL:" and doesn't indent that first line in the summary.

I should also note that upstream this has been modified quite a bit and now says "ERROR:" consistently. So for 1.2 that's likely what we will see...

Comment 3 xjia 2012-12-17 10:21:54 UTC

Verify:
Seem no problem

Version"
OpenShiftEnterprise/1.1.x/2012-12-14.1/

Comment 5 errata-xmlrpc 2013-01-31 20:32:34 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.

http://rhn.redhat.com/errata/RHSA-2013-0220.html