You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "vinod Kone (Created) (JIRA)" <ji...@apache.org> on 2011/10/25 07:14:32 UTC
[jira] [Created] (MESOS-44) Master Detector uses the wrong ACL when
auth is not required
Master Detector uses the wrong ACL when auth is not required
------------------------------------------------------------
Key: MESOS-44
URL: https://issues.apache.org/jira/browse/MESOS-44
Project: Mesos
Issue Type: Bug
Components: master
Reporter: vinod Kone
Master detector uses the following ACL regardless of auth credentials:
static ACL _EVERYONE_READ_CREATOR_ALL_ACL[] = {
{ZOO_PERM_READ, ZOO_ANYONE_ID_UNSAFE},
{ZOO_PERM_ALL, ZOO_AUTH_IDS}
};
But this ACL doesn't work with the (default) ZK server when there are no auth credentials provided.
2 ways to fix this:
1) Short term: Start the java ZK server with the flag "-Dzookeeper.skipACL=yes"
2) Long term: Fix the detector code, to use a different ACL (ZOO_OPEN_ACL_UNSAFE) when no auth is provided. This is what the new replicated log does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MESOS-44) Master Detector uses the wrong ACL when
auth is not required
Posted by "Vinod Kone (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-44:
----------------------------
Attachment: 0002-Detector-ACL-fix.patch
> Master Detector uses the wrong ACL when auth is not required
> ------------------------------------------------------------
>
> Key: MESOS-44
> URL: https://issues.apache.org/jira/browse/MESOS-44
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Vinod Kone
> Attachments: 0002-Detector-ACL-fix.patch
>
>
> Master detector uses the following ACL regardless of auth credentials:
> static ACL _EVERYONE_READ_CREATOR_ALL_ACL[] = {
> {ZOO_PERM_READ, ZOO_ANYONE_ID_UNSAFE},
> {ZOO_PERM_ALL, ZOO_AUTH_IDS}
> };
> But this ACL doesn't work with the (default) ZK server when there are no auth credentials provided.
> 2 ways to fix this:
> 1) Short term: Start the java ZK server with the flag "-Dzookeeper.skipACL=yes"
> 2) Long term: Fix the detector code, to use a different ACL (ZOO_OPEN_ACL_UNSAFE) when no auth is provided. This is what the new replicated log does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-44) Master Detector uses the wrong ACL
when auth is not required
Posted by "Vinod Kone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone resolved MESOS-44.
-----------------------------
Resolution: Fixed
> Master Detector uses the wrong ACL when auth is not required
> ------------------------------------------------------------
>
> Key: MESOS-44
> URL: https://issues.apache.org/jira/browse/MESOS-44
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Attachments: 0002-Detector-ACL-fix.patch
>
>
> Master detector uses the following ACL regardless of auth credentials:
> static ACL _EVERYONE_READ_CREATOR_ALL_ACL[] = {
> {ZOO_PERM_READ, ZOO_ANYONE_ID_UNSAFE},
> {ZOO_PERM_ALL, ZOO_AUTH_IDS}
> };
> But this ACL doesn't work with the (default) ZK server when there are no auth credentials provided.
> 2 ways to fix this:
> 1) Short term: Start the java ZK server with the flag "-Dzookeeper.skipACL=yes"
> 2) Long term: Fix the detector code, to use a different ACL (ZOO_OPEN_ACL_UNSAFE) when no auth is provided. This is what the new replicated log does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MESOS-44) Master Detector uses the wrong ACL
when auth is not required
Posted by "Chris Lambert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambert reassigned MESOS-44:
----------------------------------
Assignee: Vinod Kone
> Master Detector uses the wrong ACL when auth is not required
> ------------------------------------------------------------
>
> Key: MESOS-44
> URL: https://issues.apache.org/jira/browse/MESOS-44
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Attachments: 0002-Detector-ACL-fix.patch
>
>
> Master detector uses the following ACL regardless of auth credentials:
> static ACL _EVERYONE_READ_CREATOR_ALL_ACL[] = {
> {ZOO_PERM_READ, ZOO_ANYONE_ID_UNSAFE},
> {ZOO_PERM_ALL, ZOO_AUTH_IDS}
> };
> But this ACL doesn't work with the (default) ZK server when there are no auth credentials provided.
> 2 ways to fix this:
> 1) Short term: Start the java ZK server with the flag "-Dzookeeper.skipACL=yes"
> 2) Long term: Fix the detector code, to use a different ACL (ZOO_OPEN_ACL_UNSAFE) when no auth is provided. This is what the new replicated log does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-44) Master Detector uses the wrong ACL
when auth is not required
Posted by "Vinod Kone (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137780#comment-13137780 ]
Vinod Kone commented on MESOS-44:
---------------------------------
fixed and tested on a default zk server (with skipACL=no) and successfully connected mesos master to zk.
> Master Detector uses the wrong ACL when auth is not required
> ------------------------------------------------------------
>
> Key: MESOS-44
> URL: https://issues.apache.org/jira/browse/MESOS-44
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Vinod Kone
> Attachments: 0002-Detector-ACL-fix.patch
>
>
> Master detector uses the following ACL regardless of auth credentials:
> static ACL _EVERYONE_READ_CREATOR_ALL_ACL[] = {
> {ZOO_PERM_READ, ZOO_ANYONE_ID_UNSAFE},
> {ZOO_PERM_ALL, ZOO_AUTH_IDS}
> };
> But this ACL doesn't work with the (default) ZK server when there are no auth credentials provided.
> 2 ways to fix this:
> 1) Short term: Start the java ZK server with the flag "-Dzookeeper.skipACL=yes"
> 2) Long term: Fix the detector code, to use a different ACL (ZOO_OPEN_ACL_UNSAFE) when no auth is provided. This is what the new replicated log does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira