Bug 806375

Summary:	rhc-admin-chk flags apps that are fine as "does not exist on any node"
Product:	OKD	Reporter:	Thomas Wiest <twiest>
Component:	Pod	Assignee:	Rajat Chopra <rchopra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	high
Version:	2.x	CC:	dmcphers, jialiu, mpatel
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:	2012-04-27 20:47:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thomas Wiest 2012-03-23 15:10:22 UTC

Description of problem:
rhc-admin-chk flags apps that are fine as "does not exist on any node."

For instance, in STG, it says this about one of my apps:
Gear 10f90d2d524342c39ea598afd775ab85 in drupal does not exist on any node

But when I look, it's clearly still on ex-std-node1.stg.rhcloud.com.


It does this in PROD too. Here is one of my apps:
Gear 0dc36a4daa35429b9ad4a308695ef5d4 in jmigrate does not exist on any node

But when I look, it's still on ex-std-node11.prod.rhcloud.com


In STG it flags roughly 50% of apps. In PROD it flags roughly 90% of apps.


Version-Release number of selected component (if applicable):
rhc-broker-0.88.10-1.el6_2.noarch


How reproducible:
Very


Steps to Reproduce:
1. Run rhc-admin-chk
2. Take one of the results from the output and look for that app on a node
3. Notice that that app is still on a node
  

Actual results:
Flags apps that are fine as "does not exist on any node".


Expected results:
It should only flag apps that have issues.

Comment 1 Rajat Chopra 2012-03-30 02:56:27 UTC

Cant reproduce this bug on devenv. 
Possible theoretical reasons are : timeout on mcollective calls, truncation of data because of size.

Need help with getting on the stg env to debug.

Not fixing this in Sprint #8.

Comment 2 Thomas Wiest 2012-03-30 03:13:18 UTC

Ok, sounds good. Ping me after the release to PROD and you and I can go through this in STG or PROD together.

Thanks :)

Comment 3 Rajat Chopra 2012-04-02 23:00:15 UTC

Fixed with rev#ab7f57f1414516ab70795cdf44684f79b13bd988

Comment 4 Johnny Liu 2012-04-06 09:06:23 UTC

Hi Thomas,

For QE, it is difficult to reproduce this issue, and verify it.
Can you help to verify it? If it passed, please help move this bug to "Verified".


Thanks

Comment 5 Thomas Wiest 2012-04-09 14:53:37 UTC

Sure. It hasn't been pushed in to STG yet (that will happen later this week), and once it is, then I'll verify it.

Comment 6 Thomas Wiest 2012-04-13 19:08:52 UTC

I verified that this bug is fixed in STG.