You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2010/08/09 06:30:18 UTC

[jira] Updated: (WHIRR-23) Upgrade to jclouds 1.0-beta-6

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

Tom White updated WHIRR-23:
---------------------------

    Attachment: jclouds-compute.log

Thanks for the patch Adrian. I've been trying to run it, but have hit a problem when the scripts are run on the newly-provisioned nodes - see the attached log file. I actually get a similar problem without this patch, which I wasn't seeing before, so I wonder if it's something that changed on the EC2 side. Can you run any of the integration tests (e.g. zookeeper) successfully?

> Upgrade to jclouds 1.0-beta-6 
> ------------------------------
>
>                 Key: WHIRR-23
>                 URL: https://issues.apache.org/jira/browse/WHIRR-23
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.1.0
>            Reporter: Tom White
>            Priority: Blocker
>             Fix For: 0.1.0
>
>         Attachments: jclouds-compute.log, WHIRR-23.patch
>
>
> There are some API changes which need code changes: http://anyweight.blogspot.com/2010/05/new-jclouds-hardens-cloud-provisioning.html

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


Re: [jira] Updated: (WHIRR-23) Upgrade to jclouds 1.0-beta-6

Posted by Adrian Cole <ad...@opscode.com>.
Hi, Tom.

I'll look at the log, but I noticed only zookeeper worked.  Since I didn't
baseline, I'm not sure if they did before I updated to beta-6.

-Adrian

On Sun, Aug 8, 2010 at 9:30 PM, Tom White (JIRA) <ji...@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/WHIRR-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Tom White updated WHIRR-23:
> ---------------------------
>
>    Attachment: jclouds-compute.log
>
> Thanks for the patch Adrian. I've been trying to run it, but have hit a
> problem when the scripts are run on the newly-provisioned nodes - see the
> attached log file. I actually get a similar problem without this patch,
> which I wasn't seeing before, so I wonder if it's something that changed on
> the EC2 side. Can you run any of the integration tests (e.g. zookeeper)
> successfully?
>
> > Upgrade to jclouds 1.0-beta-6
> > ------------------------------
> >
> >                 Key: WHIRR-23
> >                 URL: https://issues.apache.org/jira/browse/WHIRR-23
> >             Project: Whirr
> >          Issue Type: Improvement
> >          Components: core
> >    Affects Versions: 0.1.0
> >            Reporter: Tom White
> >            Priority: Blocker
> >             Fix For: 0.1.0
> >
> >         Attachments: jclouds-compute.log, WHIRR-23.patch
> >
> >
> > There are some API changes which need code changes:
> http://anyweight.blogspot.com/2010/05/new-jclouds-hardens-cloud-provisioning.html
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Re: [jira] Updated: (WHIRR-23) Upgrade to jclouds 1.0-beta-6

Posted by Adrian Cole <ad...@opscode.com>.
Hi, Tom.

Do you happen to have the jclouds-wire.log?  It seems that the ec2 instance
didn't have a state attribute, which is very unexpected, but not terribly
surprising.  I wonder if it is possible that the describeInstances command
from ec2 can return an instance without a state?  If so, we may have to
build in a retry until the state is visible.

-Adrian

On Sun, Aug 8, 2010 at 9:30 PM, Tom White (JIRA) <ji...@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/WHIRR-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Tom White updated WHIRR-23:
> ---------------------------
>
>    Attachment: jclouds-compute.log
>
> Thanks for the patch Adrian. I've been trying to run it, but have hit a
> problem when the scripts are run on the newly-provisioned nodes - see the
> attached log file. I actually get a similar problem without this patch,
> which I wasn't seeing before, so I wonder if it's something that changed on
> the EC2 side. Can you run any of the integration tests (e.g. zookeeper)
> successfully?
>
> > Upgrade to jclouds 1.0-beta-6
> > ------------------------------
> >
> >                 Key: WHIRR-23
> >                 URL: https://issues.apache.org/jira/browse/WHIRR-23
> >             Project: Whirr
> >          Issue Type: Improvement
> >          Components: core
> >    Affects Versions: 0.1.0
> >            Reporter: Tom White
> >            Priority: Blocker
> >             Fix For: 0.1.0
> >
> >         Attachments: jclouds-compute.log, WHIRR-23.patch
> >
> >
> > There are some API changes which need code changes:
> http://anyweight.blogspot.com/2010/05/new-jclouds-hardens-cloud-provisioning.html
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>