[JIRA] (JENKINS-60802) JCasC EC2 Plugin private key not working

5 views
Skip to first unread message

ard-jan.barnas@signalpath.com (JIRA)

unread,
Jan 16, 2020, 1:33:03 PM1/16/20
to jenkinsc...@googlegroups.com
Ard-Jan Barnas created an issue
 
Jenkins / Bug JENKINS-60802
JCasC EC2 Plugin private key not working
Issue Type: Bug Bug
Assignee: Ewelina Wilkosz
Components: configuration-as-code-plugin, ec2-plugin
Created: 2020-01-16 18:32
Priority: Critical Critical
Reporter: Ard-Jan Barnas

The private key in configuration-as-code placed under referenceContent of EC2 cloud is successfully imported, however jobs fail to connect to EC2 slaves. Once the (SAME) private key is configured MANUALLY through the UI, it works fine.

Steps to reproduce:

  1. Install Jenkins using Helm chart (codecentric) and configure private key in values.yaml for this chart.
  2. Run helm install
  3. Run a job that uses EC2 slave
  4. Job fails
  5. Manually import private key in Jenkins system config
  6. Run job again... success

 

No
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

richard.pula@gmail.com (JIRA)

unread,
Mar 20, 2020, 5:47:02 PM3/20/20
to jenkinsc...@googlegroups.com
Richard Pula commented on Bug JENKINS-60802
 
Re: JCasC EC2 Plugin private key not working

I faced the same problem and it was because the remoteFS attribute was missing in my jenkins.yaml.

Here an example:

  - amazonEC2:      
      cloudName: "Slaves EC2"      
      privateKey: "${KEY}"      
      region: "eu-central-1"      
      templates:      
        - ami: "ami-0269d640534cbf7ea"        
          amiType:          
            unixData:            
              sshPort: "22"
          remoteFS: ""

 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages