It appears it finally 'figured' it out overnight. How long is the timeout, and is there any way to change that?
Thanks! On Wednesday, May 21, 2014 1:24:23 AM UTC-7, Thomas Orozco wrote: > > Hi Justice, > > Scalr should automatically realize that this instance is dead on the > OpenStack side of things, has the instance been like this for a while? > > Cheers, > > On Tuesday, May 20, 2014 8:28:51 PM UTC+2, Justice London wrote: >> >> A developer did something he shouldn't have and attempted to rebuild an >> instance from the openstack side. Thankfully it wasn't a 'live' instance so >> it didn't overall break anything. The trouble is that Scalr got confused >> after I believe it couldn't communicate with Scalarizr. It is now stuck in >> a 'terminating' state even though the openstack instance has been >> terminated. What can I do to get it out of this state and attempt to >> rebuild the instance (If it has to be removed from the database I suppose >> that is okay as well). >> >> Thanks! >> > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
