[JIRA] [ec2] (JENKINS-23788) EC2 plugin regression: fails to launch nodes with "syntax error near unexpected token `newline'"

Wed, 16 Jul 2014 08:44:27 -0700

This is not an EC2 plugin bug. It's an unrelated misconfiguration.

The EC2 access key for the host had recently been revoked and re-generated. While the plugin key was updated, the signed URLs for setup scripts, like:

#!/bin/bash
curl -L -s "http://2q-jenkins-resources.s3.amazonaws.com/amazonlinux201209_jenkins_instancesetup.sh?AWSAccessKeyId=AKIAJZPC6FQAU4REUX2A&Expires=1670373735&Signature=nnnwC%2Fjmc8F69ZR5GGMnyf%2BVZ64%3D" | sudo bash


were not. The output of this, when curl fails, is:





<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>52BD679ED9E0DB18</RequestId><HostId>cdKQeciGcl+HLd1TLSdxY48LGPk8znlYKGIV15momRZ1rPFgcInjnB2tBMx+EIW5</HostId></Error>





thus the error. 





set -o pipefail





would've helped produce a clearer error, when combined with





curl -L -s --fail





to produce a command like:





set -o pipefail
if ! curl -L -s --fail 'http://2q-jenkins-resources.s3.amazonaws.com/amazonlinux201209_jenkins_instancesetup.sh?AWSAccessKeyId=AKIAJZPC6FQAU4REUX2A&amp;Expires=1670373735&amp;Signature=nnnwC%2Fjmc8F69ZR5GGMnyf%2BVZ64%3D' | bash; then 
  echo "Setup script failed"
fi





So - PEBKAC, no problem here.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to