Description of problem: In the node code - lib/openshift-origin-node/model/unix_user.rb - the write_ssh_keys method is not thread safe. Version-Release number of selected component (if applicable): all How reproducible: Often (on INT) Steps to Reproduce: 1. Create an account on integration 2. Add 2 different ssh keys to the account 3. In a loop - create and destroy scalable apps till the git clone fails. Actual results: Fails to clone the git repository because the ~/.ssh/authorized_keys is hosed. Expected results: git clone should succeed + keys should be valid. Additional info: The broker creates the gear and then issues parallel mcollective calls to add the authorized ssh keys to the gear. On a slow system, its possible to have the 2 parallel ssh key operations running simultaneously and this results in the ~/.ssh/authorized_keys file getting borked.
Workaround: Remove all the keys from the account and re-add the keys. Can FutureFeature this but keep the pri/sev higher.
This issue was worked around in BZ 876942 by disabling the parallel thread execution and a user story was created to put it back in. *** This bug has been marked as a duplicate of bug 876942 ***