Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

Destroy node on joyentcloud does not destroy an already running node #1263

Closed
rstradling opened this issue Jan 29, 2013 · 2 comments
Closed
Milestone

Comments

@rstradling
Copy link
Contributor

When running a converge 0 step in pallet the node is not destroyed because it is in the running state.. After discussing this with jclouds e-mail list I was asked to submit a bug to make delete force a shutdown if the node is already running to match other behaviors. The relevant thread is this one https://groups.google.com/forum/?fromgroups=#!topic/jclouds-dev/2TZW-02rqRA

WARN jclouds.compute - << illegal state destroying node(us-east-1/4632fb03-4e31-4610-b387-814aec9e5048)
16:52:16.973 [clojure-agent-send-off-pool-9] DEBUG jclouds.compute - << destroyed node(us-east-1/4632fb03-4e31-4610-b387-814aec9e5048) success(false)

which I imagine comes from BaseComputeService.java line 266 in 1.5.5 jclouds which is called by pallet to destroy the node.

According to the thread it should shutdown and then destroy the node.

@codefromthecrypt
Copy link
Contributor

can you verify using 1.5.x ?

@rstradling
Copy link
Contributor Author

This is most definitely fixed. Thank you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants