Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Add a provider account. 2. If i understand correctly , Key field is for Private key (pk-....pem) and cert key field is for (cert-...pem) 3. If the keys are exchanged i.e cert key is browsed for Key field and Private key for Cert , No error is thrown . Test Connection also shows success. Not able to test if this gives problem while ssh'ing to the instance as template building fails in this build. Actual results: Expected results: Additional info:
Your understanding is correct in regards to key (pk-*.pem) and certificate (cert-*.pem) I wasn't able to reproduce this issue. I switched the key and certificate as you said and got this error as expected: "Login Credenials are Invalid for this Provider"
agreed this is working in [root@hp-dl360g5-02 ~]# rpm -qa | grep aeolus aeolus-all-0.3.0-0.el6.20110601221125git0f429f7.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110601221125git0f429f7.noarch aeolus-conductor-0.3.0-0.el6.20110601221125git0f429f7.noarch aeolus-conductor-doc-0.3.0-0.el6.20110601221125git0f429f7.noarch aeolus-configure-2.0.1-0.el6.20110602110128git5cb9257.noarch
removing from tracker
perm close