After some debugging, I found out the cause of the said problem. Below is
the output from "git diff":
================================================
diff --git a/starcluster/cluster.py b/starcluster/cluster.py
index 0e820a7..436ae44 100644
--- a/starcluster/cluster.py
+++ b/starcluster/cluster.py
_at__at_ -544,7 +544,7 @@ class Cluster(object):
description field.
"""
try:
- compressed_data =
base64.b64decode(self.cluster_group.description)
+ compressed_data =
base64.b64encode(self.cluster_group.description)
pkl_data = zlib.decompress(compressed_data)
cluster_settings = cPickle.loads(str(pkl_data)).__dict__
for key in cluster_settings:
================================================
As you can see, "base64.b64decode" should have been "base64.b64encode" in
line 547.
Regards,
Joseph
On Thu, Jan 13, 2011 at 3:02 PM, Kyeong Soo (Joseph) Kim <
kyeongsoo.kim_at_gmail.com> wrote:
> Hello Justin and All,
>
> Another bug report for the development version from github.
>
> Here below is the error message from "listclusters" command:
> =============================================
> ~$ starcluster listclusters
> StarCluster - (http://web.mit.edu/starcluster) (v. 0.9999)
> Software Tools for Academics and Researchers (STAR)
> Please submit bug reports to starcluster_at_mit.edu
>
> cli.py:156 - ERROR - failed to load cluster receipt: Incorrect padding
> =============================================
>
> With the development version, I could go through all the examples in the
> documentation -- which means there is no problem with the account
> credentials -- but the listcluster command.
>
> By the way, the development version seems quite stable and provides much
> more information in the configuration template than the stable one (e.g.,
> the updated information on the use of AMIs in different zones/regions).
>
> Regards,
> Joseph
>
Received on Fri Jan 14 2011 - 13:55:59 EST