You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Steven Phung (JIRA)" <ji...@apache.org> on 2014/04/30 09:35:20 UTC

[jira] [Commented] (MESOS-1124) Mesos EC2 scripts: Cannot find any cluster

    [ https://issues.apache.org/jira/browse/MESOS-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985245#comment-13985245 ] 

Steven Phung commented on MESOS-1124:
-------------------------------------

Plan:
1.  Try to reproduce.
2.  Debug the ec2_mesos.py script to see what is going on.

Upon initial inspection it looks like the AWS EC2 security group ID is being used to catch the instances with a filter instead of the security group name.  If this is the case I will make the simple correction, test, and submit the patch.

> Mesos EC2 scripts: Cannot find any cluster
> ------------------------------------------
>
>                 Key: MESOS-1124
>                 URL: https://issues.apache.org/jira/browse/MESOS-1124
>             Project: Mesos
>          Issue Type: Bug
>          Components: ec2
>    Affects Versions: 0.17.0
>         Environment: MacOS X Mavericks, 0.19.2
>            Reporter: Flavian Alexandru
>            Assignee: Steven Phung
>            Priority: Critical
>              Labels: patch
>             Fix For: 0.19.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Currently, the Mesos EC2 scripts are consistently failing to perform any management tasks after launching a cluster.
> The below will work as expected:
> {code}
>  ./mesos-ec2 -k "mkey" -i mykey.pem -w 550 -z "us-east-1c" -t m1.large launch mycluster
> {code}
> After the cluster is launched:
> {code}
>  ./mesos-ec2 -k "mykey" -i mykey.pem login mycluster // fails
> // ERROR: Could not find any existing cluster
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)