-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey Greg,
The latest code on github will store the cluster's metadata in the
master node's tags and user data instead of the description field of
the cluster's security group.
Before this change the cluster's group description contained the
version plus the cluster's base64-encoded metadata e.g.:
0.93.3-$base64_encoded_data
If you see 0.9999 as the version this means you used a previous
development version of StarCluster. In this case you'll need to
roll-back to a previous commit (ie before the metadata change) in
order to use StarCluster to manage the cluster:
$ git checkout d7443c16573cc99aa6fd020e507f6e2757222371
In this case I would recommend temporarily running the above (perhaps
in a separate copy of the git repo) just to do whatever's necessary to
shutdown the cluster. Once your old clusters have been terminated it
you should be able to switch back to the latest git code.
Sorry this is so cumbersome but sometimes when you live on the
bleeding edge you bleed :D With that said I plan to provide more
informative error messages before release to alleviate some of this
pain...
HTH,
~Justin
On 10/23/2012 10:45 AM, Greg Caporaso wrote:
> Hi, I'm running into an issue related to the one described here:
>
> https://github.com/jtriley/StarCluster/issues/151
>
> (I asked this question there as well, but then realized that this
> was the more appropriate place to ask.)
>
> Is there a way to determine what version of StarCluster was used
> to create a cluster?
>
> Greg _______________________________________________ StarCluster
> mailing list StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://www.enigmail.net/
iEYEARECAAYFAlCKv5gACgkQ4llAkMfDcrkaIgCbB17//3HQ7EGxKGrYIH+C+SCy
cfEAoI5GB9JCChPh++mphgQfbCRIBo0e
=yunT
-----END PGP SIGNATURE-----
Received on Fri Oct 26 2012 - 12:51:38 EDT