[
https://issues.apache.org/jira/browse/MESOS-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092172#comment-15092172
]
Greg Mann commented on MESOS-4319:
----------------------------------
[~arojas], I'll be posting a patch today for MESOS-3940 which should fix this
issue. Unfortunately, the verification functions for RESERVE, UNRESERVE,
CREATE, and DESTROY operations currently enforce the principal to be {{Some}},
which shouldn't be the case if we're allowing these operations without
authentication, or in the case of a permissive set of ACLs. Perhaps we should
mark this ticket as dependent on MESOS-3940, or a duplicate?
> Dynamic reservation creation failed with http endpoint
> ------------------------------------------------------
>
> Key: MESOS-4319
> URL: https://issues.apache.org/jira/browse/MESOS-4319
> Project: Mesos
> Issue Type: Bug
> Reporter: Guangya Liu
>
> {code}
> curl -i -u p1:s1 -d slaveId="12875be6pe": "SCALAR", "scalar": { "value": 1 },
> "role": "ads", "reservation": { "principal": "p1" } }, { "name": "mem",
> "type": "SCALAR", "scalar": { "value": 1000 }, "role": "ads", "reservation":
> { "principal": "p1" } } ]' -X POST http://192.168.1.104:5050/master/reserve
> HTTP/1.1 400 Bad Request
> Date: Sun, 10 Jan 2016 04:10:50 GMT
> Content-Length: 71
> Invalid RESERVE operation: Cannot reserve resources without a principal
> {code}
> I found that in https://reviews.apache.org/r/39043/diff/32#6 , the HTTP
> authentication was updated by adding a new optional parameter {{principal}}
> for reserve, but there is no document for how to set this parameter via http
> endpoint.
> cc [~arojas] , any comments for this? Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
