5 Replies Latest reply on Jul 14, 2016 12:16 AM by Sayan Roy

    Install Agents on Agentless AWS Linux target instances failed

    Sayan Roy

      Hi,

      I am looking for installing agents on agentless aws linux target instances using unified agent installer. I created the agent software bundles in the depot folder from the BBSA87-RSCDAgents.zip. Imported the agentless Linux instance into BSA(testing with one instance as of now, need to do for multiple instance post deployment). In the unified agent installer wizard, created an object to install agents. In the Add Remote Authentication window I defined the authentication information. Provided the username as 'ec2-user' and imported the .ppk file in the Private Key Path. I had added the property condition the TARGET.IP_ADDRESS equals  the IP of the instance. Ran the agent installer job against the target agentless server. The job fails showing an error "Remote host authentication failed to validate against the server due to invalid private key".

      Check the automation principle created. The AWS Linux instance is very much accessible via putty with the ppk file I used in the unified agent installer object.

      Please help. I am clueless why the error threw as invalid private key.

        • 1. Re: Install Agents on Agentless AWS Linux target instances failed
          Bill Robinson

          what kind of key are you using ?  i believe bsa only works w/ rsa.

          • 2. Re: Install Agents on Agentless AWS Linux target instances failed
            Sayan Roy

            I am using the .ppk file which I generated from puttygen from the .pem file(private key generated during ec2 instance provisioning). This is 2048 SSH-2-RSA key. BSA doesn't work with this key?

            • 3. Re: Install Agents on Agentless AWS Linux target instances failed
              Sayan Roy

              Below is the agent installer job logs:

               

              Job Name,LinRSCD - Run at 07/13/2016 13:07:31

              Start Time,07/13/2016 13:07:31

              End Time,07/13/2016 13:07:51

              Status,Completed with Errors

               

               

              Participant,Type,Date,Message

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:31,"JobRun Log Settings: JobRun Limit = 1000000, Per Target Log Limit = 1000, Per Target Log Level = AllInfo"

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:31,Started running the job 'LinRSCD' with priority 'NORMAL' on application server 'job_deployment_2_blrsfbsasv'(5)

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:33,Executing 'LinRSCD' with agent bundle 'LinRSCD'.

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:35,Executing work item Agent Installer Job:LinRSCD; Server:10.3.1.22;  on application server: job_deployment_1_blrsfbsasv

              10.3.1.22,Info,07/13/2016 13:07:39,Failed to detect a running agent on server '10.3.1.22'. Assuming agent is not installed.

              10.3.1.22,Info,07/13/2016 13:07:39,Initiating agent installation.

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:42,Executing work item Agent Installer Job(Pre-Execute):LinRSCD; Server:10.3.1.22;  on application server: job_deployment_1_blrsfbsasv

              10.3.1.22,Info,07/13/2016 13:07:42,Initializing the FQDN and IP Address for '10.3.1.22'

              10.3.1.22,Info,07/13/2016 13:07:42,No property update is needed for '10.3.1.22' as FQDN and IP Address are already set.

              10.3.1.22,Info,07/13/2016 13:07:42,Found 1 remote host authentication associated with server '10.3.1.22'.  Checking it to make sure it is valid.

              Run at 07/13/2016 13:07:31,Info,07/13/2016 13:07:49,Executing work item Agent Installer Job(OsDiscovery):LinRSCD; Server:10.3.1.22;  on application server: job_deployment_1_blrsfbsasv

              10.3.1.22,Info,07/13/2016 13:07:49,Validating remote host authentication 1 of 1 'LinRSCD_1' against server '10.3.1.22'.

              10.3.1.22,Warning,07/13/2016 13:07:49,Remote host authentication 1 of 1 'LinRSCD_1' failed to validate against server '10.3.1.22' due to: invalid privatekey: E:/BMC Software/BladeLogic/8.1/NSH/tmp/job_deployment_1_blrsfbsasv/8854c150-a7a0-429a-814b-a476a25e084c\AnanthaRao.ppk

              10.3.1.22,Error,07/13/2016 13:07:49,Installing the agent on '10.3.1.22' failed because all of the remote host authentications failed to validate.

              Run at 07/13/2016 13:07:31,Error,07/13/2016 13:07:51,The job 'LinRSCD' has failed.

              • 4. Re: Install Agents on Agentless AWS Linux target instances failed
                Bill Robinson

                is the ppk in plain text ?  it's not some binary format or a keystore format ?  it should be identical to what you get from a 'ssh-keygen' - the id_rsa.pub

                1 of 1 people found this helpful
                • 5. Re: Install Agents on Agentless AWS Linux target instances failed
                  Sayan Roy

                  Thank you so much. I used the original .pem file of the aws linux instance to authenticate the agent installer job, it worked. It could validate.

                  I did your option too. Exported the private key to OpenSSH compatible format. ssh-keygen("ssh" package) produces different keys from puttygen ("putty" package).