Bug 1045343

Description of problem:
By oo-admin-repair --ssh-key to repair the ssh key issue, after that, oo-admin-chk -l1 will show 'FAILED', but in fact, it did not find some error.

Version-Release number of selected component (if applicable):
devenv_4161

How reproducible:
always

Steps to Reproduce:
1. Create an app 
2. Create ssh key
 ssh-keygen -t rsa -N '' -f testkey
3. Add new sshkey
  rhc sshkey add testkey testkey.pub
4. Remove the testkey in /var/lib/openshift/UUID/.ssh/authorized_keys 
5. Run 'oo-admin-chk -l 1'
6. Run 'oo-admin-repair --sshkey
7. Run 'oo-admin-chk -l 1' again

Actual results:

step 5:
oo-admin-chk -l1
Started at: 2013-12-20 06:59:19 UTC

Total gears found in mongo: 2
Total gears found on the nodes: 2
Total nodes that responded: 1

Finished at: 2013-12-20 07:00:01 UTC
Total time: 42.004s
Gear '52b3e86a92e613db8d000036' has key with hash '7a611e51642d8c0ba56a1e217532a5d9' and updated name '52b3e6c292e613db8d000001-testkey' in mongo but not on the node.

FAILED
Please refer to the oo-admin-repair tool to resolve some of these inconsistencies.

*****************************************************************
step 6:

oo-admin-repair --ssh-keys
Started at: 2013-12-20 02:07:21 -0500
Time to fetch mongo data: 0.021s
Total gears found in mongo: 2
Time to get all sshkeys for all gears from nodes: 20.732s
Total gears found on the nodes: 2
Total nodes that responded : 1
Check failed.
Gear '52b3e86a92e613db8d000036' has key with hash '7a611e51642d8c0ba56a1e217532a5d9' and updated name '52b3e6c292e613db8d000001-testkey' in mongo but not on the node.


Fixing ssh key inconsistencies for all affected applications:

Fixed ssh key mismatches for 1 applications.

Total time: 21.512s
Finished at: 2013-12-20 02:07:43 -0500

***********************************************************
step 7, oo-admin-chk -l 1 still show 'FAILED' but did not find any errors.

oo-admin-chk -l1 -v
Started at: 2013-12-20 07:15:16 UTC

Total gears found in mongo: 2
Total gears found on the nodes: 2
Total nodes that responded: 1
Checking application gears on corresponding nodes
Checking node gears in application database
Checking for user consumed gears and actual gears
Checking application gears and ssh keys on corresponding nodes
Checking for unreserved UIDs in the district
Checking for unused UIDs in the district
Checking for gears with the same UID
Checking gears available in applications collection but not in usage_records and viceversa: OK
Checking gears with additional storage in applications collection but not in usage_records and viceversa: OK
Checking gears with premium cartridge in applications collection but not in usage_records and viceversa: OK
Checking un-ended records in usage_records collection but not in usage collection and viceversa: OK
Checking usage_account_id validity for all billing users: OK
Checking plan_id validity for all billing users: OK
Checking plan_state validity for all billing users: OK

Finished at: 2013-12-20 07:15:58 UTC
Total time: 41.943s

FAILED
Please refer to the oo-admin-repair tool to resolve some of these inconsistencies.
 
Expected results:
Should show 'PASS'

Additional info:
Use 'oo-admin-repair --consumed-gears/ssh-keys/district-uids -r' to check, all of them show 'Success'