Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
Description
UEC, one AMI defined.
UEC URL is https://10.55.56.10:8443/
AMI is emi-AD2C1446 (an internal AMI, but shouldn't matter).
'test connection' is working. but 'check AMI' isn't - gives the error 'endpoint is not a valid URL'.
Attachments
Activity
lifeless
created issue -
Masaki Muranaka
added a comment - I inspected the behavior in my browser. (Safari 5.0.3 (6533.19.4) on OSX10.6)
validateButton() is called with 'paramList == "secretKey,accessId,ec2EndpointUrl,ami"'. This may be correct.
But (at least on my environment), the return value of findPreviousFormItem(button, "ec2EndPointUrl") become null.
In this case, Jenkins can't find the location. right?
Masaki Muranaka
added a comment - I inspected the behavior in my browser. (Safari 5.0.3 (6533.19.4) on OSX10.6)
validateButton() is called with 'paramList == "secretKey,accessId,ec2EndpointUrl,ami"'. This may be correct.
But (at least on my environment), the return value of findPreviousFormItem(button, "ec2EndPointUrl") become null.
In this case, Jenkins can't find the location. right? 
william selwood
added a comment - Getting the same error when I push the button with Amazon EC2 using region eu-west-1 in both Fire Fox 4b12 and Chrome under Windows 7 with plugin version 1.10
Masaki Muranaka's hint above leads me to believe that the problem lies in the ec2EndpointUrl being invalid when it is passed into validateAmi cant find where this ec2EndpointUrl comes from though. Worth noting the test connection button uses the region rather than this ec2EndpointUrl, this may be one solution to the problem. If I have time I may do more digging tomorrow.
william selwood
added a comment - Getting the same error when I push the button with Amazon EC2 using region eu-west-1 in both Fire Fox 4b12 and Chrome under Windows 7 with plugin version 1.10
Masaki Muranaka's hint above leads me to believe that the problem lies in the ec2EndpointUrl being invalid when it is passed into validateAmi cant find where this ec2EndpointUrl comes from though. Worth noting the test connection button uses the region rather than this ec2EndpointUrl, this may be one solution to the problem. If I have time I may do more digging tomorrow. | Field | Original Value | New Value |
|---|---|---|
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 136156 ] | JNJira + In-Review [ 187127 ] |
I've been got similar issue with EC2.
The Version of plugin is "Hudson Amazon EC2 plugin : 1.10".