[ 
https://issues.apache.org/jira/browse/WHIRR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom White updated WHIRR-123:
----------------------------

    Attachment: WHIRR-123.patch

The problem with the previous patch was that arguments to the runurl script 
were being treated as a part of the URL, which caused a problem when the URL 
was being checked. Here's a new patch which fixes that.

> Cassandra integration tests hang if whirr's scripts bucket is missing
> ---------------------------------------------------------------------
>
>                 Key: WHIRR-123
>                 URL: https://issues.apache.org/jira/browse/WHIRR-123
>             Project: Whirr
>          Issue Type: Bug
>          Components: core, service/cassandra
>    Affects Versions: 0.2.0
>            Reporter: Patrick Hunt
>            Assignee: Tom White
>            Priority: Critical
>             Fix For: 0.3.0
>
>         Attachments: WHIRR-123.patch, WHIRR-123.patch
>
>
> I don't know if this is specific to cassandra or just a general issue.
> I ran the integration tests as part of building the 0.2.0 release candidate. 
> The tests failed while verifying cassandra. Looking on the ec2 host I see the 
> following in the stderr (nothing in stdout). Note - I had not created the 
> 0.2.0-incubating bucket on s3, so while this test would never pass, it seems 
> unusual that the test hangs forever rather than tear down the test and report 
> an error (I had to ctrl-c to stop the test, then manually cleanup ec2).
> --------- stderr ---------------
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/sun/java/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8
> --2010-11-02 05:51:45--
> http://whirr.s3.amazonaws.com/0.2.0-incubating/apache/cassandra/install
> Resolving whirr.s3.amazonaws.com... 72.21.211.174
> Connecting to whirr.s3.amazonaws.com|72.21.211.174|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-11-02 05:51:45 ERROR 404: Not Found.
> runurl: wget failed: 8

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to