Description of problem: Cherry-picked a few lines of code to oo-admin-chk which gives an error when someone has changed the hostname (server identity) on the node so that it no longer matches what's recorded with the apps. I would like to push this out in 1.2 so that people have a method of detecting this problem of changing hostnames before it bites them during the upgrade to 2.0 (as we found with one customer when testing 1.1 => 1.2; it was a nasty problem to diagnose). Origin commit: commit ce2881c65a9bda2a841cabc12204e4d7cdcde896 Author: Luke Meyer <lmeyer> Date: Tue Oct 15 18:03:41 2013 -0400
check it on puddle [2.0-2013-10-31.2] # oo-admin-chk -l 1 Started at: 2013-11-03 23:51:45 -0700 Time to fetch mongo data: 0.079s Total gears found in mongo: 72 Time to get all gears from nodes: 20.446s Total gears found on the nodes: 72 Total nodes that responded : 2 Time to get all sshkeys for all gears from nodes: 20.143s Total gears found on the nodes: 73 Total nodes that responded : 2 Check failed. District 'dist2' has (5989) available UIDs but (5985) available capacity WARNING: Only checked the first 4000 errors for false positives. Please refer to the oo-admin-repair tool to resolve some of these inconsistencies. Total time: 43.766s Finished at: 2013-11-03 23:52:29 -0700 [root@broker ~]# oo-admin-chk -l 1 Started at: 2013-11-03 23:55:04 -0700 Time to fetch mongo data: 0.081s Total gears found in mongo: 72 Time to get all gears from nodes: 20.44s Total gears found on the nodes: 72 Total nodes that responded : 2 Time to get all sshkeys for all gears from nodes: 20.16s Total gears found on the nodes: 73 Total nodes that responded : 2 Check failed. District 'dist2' has (5989) available UIDs but (5985) available capacity Gear 5271f5a17d59db442c00015d exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 5271f5a17d59db442c00015e exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 5271f6b07d59dbf5900000ff exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 5271f6b07d59dbf590000100 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 5272002b7d59db2ee4000143 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 527202867d59dbda310000d8 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 527221a67d59db12b7000266 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 527223587d59db12b70002ee exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 527223c57d59dbe3d5000164 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn' Gear 527202cc7d59dbea19000089 exists but node 'node3.ose-1028.com.cn' does not match DB server_identity 'node2.ose-1029.com.cn'
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/RHBA-2014-0019.html