Re: Terminating a cluster does not remove its security group (UNCLASSIFIED)

From: Dustin Machi <no email>
Date: Tue, 18 Dec 2012 11:39:28 -0500

If the terminate command fails, then there will often be things left
behind. This often happens if you manipulate the security groups
outside of start cluster and it fails to delete the security group. For
example if you start a cluster and then add it's security group to
another manually, it can't be deleted because that group is referenced
by another. This is just an example, but there are several places where
terminate could fail. These sometimes require cleanup before reusing a
name again.

Dustin


On 7 Dec 2012, at 2:15, Oppe, Thomas C ERDC-RDE-ITL-MS Contractor wrote:

> Classification: UNCLASSIFIED
> Caveats: FOUO
>
>
> Dear Sir:
>
>
>
> I have noticed that when I try to start up a cluster with the same
> name that was used before, the "startcluster start" command errors out
> with some message about there not being a "master" node to run plugins
> or something to that effect. So I choose a new name for the cluster
> and all works fine with the new name. I think the problem is that
> "starcluster terminate" doesn't completely remove all remnants of the
> cluster. I did "starcluster listclusters" and saw all these defunct
> clusters that were terminated a long time ago. The solution was to
> delete the "Security Group" associated with each terminated cluster.
> Once the security group is deleted, you can use that cluster's name
> again in future "starcluster start" commands. At least I think so.
>
>
>
> Tom Oppe
>
>
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
Received on Tue Dec 18 2012 - 11:39:38 EST