Red Hat Bugzilla – Bug 823851
rhc-chk and "rhc domain status"will return failure message even if all the files are matched in win7
Last modified: 2015-05-14 21:54:34 EDT
Created attachment 585986 [details]
The massage of rhc-chk
Description of problem:
The rhc-chk will return failure message even if all the files are matched.
And I uploaded the output of rhc-chk to the attachment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create an domain in win7
Will return the message like the attachment.
The result of rhc-chk should 100% passed.
I run the rhc-chk on mac os, the output is like below.
..EF.Could not open a connection to your authentication agent.
|| Your system did not pass all of the tests ||
1) Local /var/root/.ssh/id_rsa does not match remote pub key, SSH auth will not work
Perhaps you should regenerate your public key, or run 'rhc sshkey add' to add your new key.
2) Either ssh-agent is not running or you do not have any keys loaded.
|| Something went wrong, and not all tests completed ||
NoMethodError: undefined method `load_data_public_key' for Net::SSH::KeyFactory:Class
Right now failing only on Mac, lowering severity so this doesn't block the build and because we now have rhc setup to configure what's missing.
Tested on Mac again with rhc-0.93.19, it works
dhcp-8-149:test root# rhc domain status -p 1
Loaded suite /usr/bin/rhc-chk
Finished in 4.716513 seconds.
6 tests, 18 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
1.27 tests/s, 3.82 assertions/s
still cannot pass the rhc-chk on Windows paltform by the following failures for rhc-0.93.19.
Loaded suite C:/Ruby193/bin/rhc-chk
347: perms = sprintf('%o',File.stat(file).mode)[-3..-1]
=> 349: assert_match permission, perms, error_for(:bad_permissions,file,pe
<> expected but was
310: # Test public key and remote key
311: assert_not_nil $user_info, error_for(:no_account)
=> 312: assert $remote_ssh_pubkeys.include?(@@local_ssh_pubkey), error_for
314: fp.close if fp
<> expected but was
Private key id_rsa has wrong permission on Windows (-rw-r--r--), and cannot change it by chmod.
BTW, rhc-chk will always check the ssh-agent even if user dose not start it. And only start it and load the key to it can pass the check point.
Increasing severity on this bug since we're so dependent upon this status check to work in order to have a healthy rhc environment and overall user experience. Hoping to increase severity/priority of https://bugzilla.redhat.com/show_bug.cgi?id=836483 in the process.
I ran into this today while trying to debug a user's environment (Win) as well as my own (Mac OSX-Lion). Both were on version 0.95.13 based on yesterday's upgrade. Even after running rhc setup, things weren't working and we were dependent upon this status check to detect actual problems rather than throwing errors of it's own.
Some things to catch: When GIT_SSH env variable is set, ssh may work, but git clone won't work.
Hope that helps;
Most part about domain status failure have been fixed in this bug :https://bugzilla.redhat.com/show_bug.cgi?id=836483 on rhc-0.95.14
We should release rhc-0.95.14 in this sprint but not rhc-0.95.13.
Related to fix for 841170 and working on today.
I think I got all issues related to rhc-chk in the Windows platform.
When there is no pageant running users can still see a failure in rhc domain status, but it's not blocker (user will have to input the key password, the test failure message is explanatory).
verified on rhc-0.96.8, and the unfixed issue will tracked by 841170