It sounds like from this thread, rackspace incorrectly reports accessible
servers as pending state.

The only solutions I can think of are:
* remove the server status check and instead only rely on TCP port
accessibility
* doublecheck status on PENDING

Any other thoughts?
-A
On Oct 24, 2012 6:57 PM, "Tom Barber" <tombarbe...@googlemail.com> wrote:

We should talk about it, as right now, rackspace is the only one with this
bug.

Even if the socket test is tuned to something we consider just long enough
to be valid, it will cause an unnecessary delay on pending or terminated
nodes.  If someone has hundreds of nodes, this could add up quite a bit.

What I'd suggest is that we:
* raise this bug to rackspace, hopefully in a way they can see for
themselves the glitch
* make the health check pluggable and default to current logic
* make a temporary change to rackspace (or module in rackspace) to
double-check pending or skip state check

I suppose we could alternatively introduce a check strategy flag..

Wdyt?
-A
On Oct 30, 2012 2:12 AM, "Chris Strand" <clastr...@gmail.com> wrote:

I haven't run into this bug yet but I agree it needs to be raised if it's an issue.

Tom Barber came across it originally. Tom, is it possible for you to isolate the issue in a small app and share it with us in a gist?

If not, we can work to isolate it ourselves.

Thanks,
Everett

From: Adrian Cole <adrian.f.c...@gmail.com<mailto:adrian.f.c...@gmail.com>>
Reply-To: "jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>" <jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>>
Date: Tuesday, October 30, 2012 9:33 AM
To: "jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>" <jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>>, "jclouds-dev@googlegroups.com<mailto:jclouds-dev@googlegroups.com>" <jclouds-dev@googlegroups.com<mailto:jclouds-dev@googlegroups.com>>
Subject: Re: needs to be running before executing a script on it. current state: PENDING

We should talk about it, as right now, rackspace is the only one with this bug.

Even if the socket test is tuned to something we consider just long enough to be valid, it will cause an unnecessary delay on pending or terminated nodes.  If someone has hundreds of nodes, this could add up quite a bit.

What I'd suggest is that we:
* raise this bug to rackspace, hopefully in a way they can see for themselves the glitch
* make the health check pluggable and default to current logic
* make a temporary change to rackspace (or module in rackspace) to double-check pending or skip state check

I suppose we could alternatively introduce a check strategy flag..

Wdyt?
-A

On Oct 30, 2012 2:12 AM, "Chris Strand" <clastr...@gmail.com<mailto:clastr...@gmail.com>> wrote:
Relying on TCP port accessibility seems to make sense to me in this case since I can't think of any cases where this wouldn't be accurate.

Would it make sense to do this just for Rackspace or for other providers too?

Chris

On 26 October 2012 14:39, Adrian Cole <adrian.f.c...@gmail.com<mailto:adrian.f.c...@gmail.com>> wrote:

It sounds like from this thread, rackspace incorrectly reports accessible servers as pending state.

The only solutions I can think of are:
* remove the server status check and instead only rely on TCP port accessibility
* doublecheck status on PENDING

Any other thoughts?
-A

On Oct 24, 2012 6:57 PM, "Tom Barber" <tombarbe...@googlemail.com<mailto:tombarbe...@googlemail.com>> wrote:
HI Guys,

I'm testing on the Rackspace nextgen stuff, and my code that runs fine on EC2 gives me:
Caused by: java.lang.IllegalStateException: node DFW/073e9685-cd25-407d-a7b7-d477d8a40148 needs to be running before
                      executing a script on it. current state: PENDING

I know the server was up, I was ssh'd into it on a console as well.

I'm using the client.submitScriptOnNode() method.

Anyone seen similar?

Thanks

Tom

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To post to this group, send email to jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>.
To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com<mailto:jclouds%2Bunsubscribe@googlegro ups.com>.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To post to this group, send email to jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>.
To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com<mailto:jclouds%2Bunsubscribe@googlegro ups.com>.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To post to this group, send email to jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>.
To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com<mailto:jclouds%2Bunsubscribe@googlegro ups.com>.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To post to this group, send email to jclouds@googlegroups.com<mailto:jclouds@googlegroups.com>.
To unsubscribe from this group, send email to jclouds+unsubscribe@googlegroups.com<mailto:jclouds+unsubscribe@googlegroup s.com>.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.