Red Hat Bugzilla – Bug 1014837
oo-admin-chk sees problems with jenkins ssh keys that oo-admin-repair doesn't fix
Last modified: 2015-05-14 20:21:36 EDT
Description of problem: on INT environment, oo-admin-chk --level 1 is logging errors like: Gear '52453af66cec0e3e1c0001d8' has key with name 'jenkins' in mongo but not on the node. Running oo-admin-repair --ssh-keys does not correct the problem. Of the 37 apps being flagged on INT, only 4 actually have jenkins cartridges. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. run oo-admin-chk --level 1 on INT (also appears on STG and PROD, but has had less investigation) Actual results: errors on ssh keys that oo-admin-repair is not correcting Expected results: oo-admin-repair should be able to correct any missing ssh keys, or log a message explaining why no cleanup was attempted. Further, it's possible these entries in mongo are erroneous. Additional info:
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/9f6c5bf6f5548510faf4c99b4528e6d4d086c87b Fix for bug 1014837
Verified on devenv_3874 Create jenkins app and applications with jenkins, modify the jenkins system ssh key content to make oo-admin-chk fail, the repair it with oo-admin-repair, the mismatched sshkey can be repaired.