Red Hat Bugzilla – Bug 806375
rhc-admin-chk flags apps that are fine as "does not exist on any node"
Last modified: 2015-05-14 21:49:11 EDT
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):
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
Flags apps that are fine as "does not exist on any node".
It should only flag apps that have issues.
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.
Ok, sounds good. Ping me after the release to PROD and you and I can go through this in STG or PROD together.
Fixed with rev#ab7f57f1414516ab70795cdf44684f79b13bd988
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".
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.
I verified that this bug is fixed in STG.