You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.
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
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.
The text was updated successfully, but these errors were encountered: