[jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319818#comment-16319818 ] Yan Xu commented on MESOS-8125: --- We used to not need to handle recovering executors after a reboot because

[jira] [Commented] (MESOS-8413) Zookeeper configuration passwords are shown in clear text

[ https://issues.apache.org/jira/browse/MESOS-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319625#comment-16319625 ] James Peach commented on MESOS-8413: There's a similar issue with URLs for the {{CommandInfo.URI}}

[jira] [Updated] (MESOS-8422) Master's UpdateSlave handler not correctly updating terminated operations

[ https://issues.apache.org/jira/browse/MESOS-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gastón Kleiman updated MESOS-8422: -- Summary: Master's UpdateSlave handler not correctly updating terminated operations (was:

[jira] [Updated] (MESOS-8422) Master's UpdateSlave handler not correctly updating operations

[ https://issues.apache.org/jira/browse/MESOS-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gastón Kleiman updated MESOS-8422: -- Description: I created a test that verifies that operation status updates are resent to the

[jira] [Updated] (MESOS-8422) Master's UpdateSlave handler not correctly updating terminated operations

[ https://issues.apache.org/jira/browse/MESOS-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gastón Kleiman updated MESOS-8422: -- Description: I created a test that verifies that operation status updates are resent to the

[jira] [Created] (MESOS-8422) Master's UpdateSlave handler not correctly updating operations

Gastón Kleiman created MESOS-8422: - Summary: Master's UpdateSlave handler not correctly updating operations Key: MESOS-8422 URL: https://issues.apache.org/jira/browse/MESOS-8422 Project: Mesos

[jira] [Created] (MESOS-8421) Duration operators drop precision, even when used with integers

Andrew Schwartzmeyer created MESOS-8421: --- Summary: Duration operators drop precision, even when used with integers Key: MESOS-8421 URL: https://issues.apache.org/jira/browse/MESOS-8421 Project:

[jira] [Commented] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319427#comment-16319427 ] Greg Mann commented on MESOS-8078: -- There are some similarly missing fields in the agent operator API.

[jira] [Commented] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319425#comment-16319425 ] Greg Mann commented on MESOS-8078: -- Review here: https://reviews.apache.org/r/65056/ > Some fields went

[jira] [Updated] (MESOS-8413) Zookeeper configuration passwords are shown in clear text

[ https://issues.apache.org/jira/browse/MESOS-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-8413: - Shepherd: Greg Mann > Zookeeper configuration passwords are shown in clear text >

[jira] [Updated] (MESOS-8420) Test that operation status updates are retried after being dropped en-route to the master.

[ https://issues.apache.org/jira/browse/MESOS-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gastón Kleiman updated MESOS-8420: -- Summary: Test that operation status updates are retried after being dropped en-route to the

[jira] [Created] (MESOS-8420) Verify end-to-end operation status update

Gastón Kleiman created MESOS-8420: - Summary: Verify end-to-end operation status update Key: MESOS-8420 URL: https://issues.apache.org/jira/browse/MESOS-8420 Project: Mesos Issue Type: Task

[jira] [Updated] (MESOS-7803) fs::list drops path components on Windows

[ https://issues.apache.org/jira/browse/MESOS-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schwartzmeyer updated MESOS-7803: Priority: Major (was: Minor) > fs::list drops path components on Windows >

[jira] [Updated] (MESOS-8224) mesos.interface 1.4.0 cannot be installed with pip

[ https://issues.apache.org/jira/browse/MESOS-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kapil Arya updated MESOS-8224: -- Story Points: 1 Sprint: Mesosphere Sprint 72 Packages available at:

[jira] [Commented] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319344#comment-16319344 ] Greg Mann commented on MESOS-8078: -- [~drozhkov], thanks for the ping. I'm working on this issue today,

[jira] [Updated] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-8078: - Shepherd: Vinod Kone (was: Greg Mann) > Some fields went missing with no replacement in api/v1 >

[jira] [Assigned] (MESOS-8419) RP manager incorrectly setting framework ID leads to CHECK failure

[ https://issues.apache.org/jira/browse/MESOS-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-8419: Assignee: Greg Mann > RP manager incorrectly setting framework ID leads to CHECK failure >

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Fix Version/s: 1.3.2 > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Target Version/s: 1.3.2, 1.4.2, 1.5.1 (was: 1.4.2, 1.5.1) > Persistent volume ownership is set to root despite

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Fix Version/s: 1.4.2 > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Commented] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319113#comment-16319113 ] Jie Yu commented on MESOS-8356: --- commit c8e6487d251d938c3c221f606f7e924514877655 (origin/master,

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Fix Version/s: 1.5.0 > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Updated] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-8078: - Sprint: Mesosphere Sprint 66, Mesosphere Sprint 67, Mesosphere Sprint 68, Mesosphere Sprint 72 (was:

[jira] [Assigned] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-8078: Assignee: Greg Mann (was: Vinod Kone) > Some fields went missing with no replacement in api/v1 >

[jira] [Commented] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318943#comment-16318943 ] Jie Yu commented on MESOS-8356: --- I verified that it's not an issue with Mesos containerizer (aka, universal

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Affects Version/s: 1.1.3 1.2.3 1.3.1 Target Version/s: 1.4.2,

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Priority: Critical (was: Major) > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Comment Edited] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318907#comment-16318907 ] Jie Yu edited comment on MESOS-8356 at 1/9/18 6:45 PM: --- [~kkalin] Thanks for

[jira] [Commented] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318907#comment-16318907 ] Jie Yu commented on MESOS-8356: --- [~kkalin] Thanks for reporting! [~xujyan] This looks like a bug to me

[jira] [Assigned] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused

[ https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Megha Sharma reassigned MESOS-8125: --- Assignee: Megha Sharma > Agent should properly handle recovering an executor when its pid is

[jira] [Commented] (MESOS-8348) Enable function sections in the build.

[ https://issues.apache.org/jira/browse/MESOS-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318864#comment-16318864 ] James Peach commented on MESOS-8348: No apparent performance difference with a quick and arbitrary

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Target Version/s: (was: 1.4.2, 1.5.1) > Persistent volume ownership is set to root despite of sandbox owner

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Target Version/s: 1.4.2, 1.5.1 > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Updated] (MESOS-8356) Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

[ https://issues.apache.org/jira/browse/MESOS-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-8356: -- Affects Version/s: 1.4.1 > Persistent volume ownership is set to root despite of sandbox owner >

[jira] [Commented] (MESOS-6595) As a Mesos user I want to launch processes that will run on every node in the cluster

[ https://issues.apache.org/jira/browse/MESOS-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318802#comment-16318802 ] Sampsa Tuokko commented on MESOS-6595: -- Any progress at all on this? DaemonSets in Kubernetes world

[jira] [Updated] (MESOS-7854) Authorize resource calls to provider manager api

[ https://issues.apache.org/jira/browse/MESOS-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-7854: Description: The resource provider manager provides a function {code} process::Future api(

[jira] [Updated] (MESOS-7558) Add resource provider validation

[ https://issues.apache.org/jira/browse/MESOS-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-7558: Story Points: 2 > Add resource provider validation > > >

[jira] [Updated] (MESOS-7558) Add resource provider validation

[ https://issues.apache.org/jira/browse/MESOS-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-7558: Story Points: 3 (was: 2) > Add resource provider validation >

[jira] [Updated] (MESOS-7329) Authorize offer operations for converting disk resources

[ https://issues.apache.org/jira/browse/MESOS-7329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-7329: Story Points: 3 > Authorize offer operations for converting disk resources >

[jira] [Commented] (MESOS-7742) ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession is flaky

[ https://issues.apache.org/jira/browse/MESOS-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318666#comment-16318666 ] Andrei Budnik commented on MESOS-7742: -- As we have launched

[jira] [Commented] (MESOS-7742) ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession is flaky

[ https://issues.apache.org/jira/browse/MESOS-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318567#comment-16318567 ] Andrei Budnik commented on MESOS-7742: -- How to reproduce Flavour 3: Put a {{::sleep(1);}} before

[jira] [Updated] (MESOS-8388) Show LRP resources in master endpoints.

[ https://issues.apache.org/jira/browse/MESOS-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-8388: Story Points: 2 Component/s: master > Show LRP resources in master endpoints. >

[jira] [Commented] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318459#comment-16318459 ] Dmitrii Rozhkov commented on MESOS-8078: Hey [~vinodkone], would you please give an update on the

[jira] [Updated] (MESOS-8078) Some fields went missing with no replacement in api/v1

[ https://issues.apache.org/jira/browse/MESOS-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitrii Rozhkov updated MESOS-8078: --- Priority: Critical (was: Major) > Some fields went missing with no replacement in api/v1 >

[jira] [Updated] (MESOS-8382) Master should bookkeep local resource providers.

[ https://issues.apache.org/jira/browse/MESOS-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bannier updated MESOS-8382: Story Points: 5 > Master should bookkeep local resource providers. >

[jira] [Updated] (MESOS-7506) Multiple tests leave orphan containers.

[ https://issues.apache.org/jira/browse/MESOS-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Budnik updated MESOS-7506: - Attachment: ROOT_IsolatorFlags-badrun2.txt > Multiple tests leave orphan containers. >

[jira] [Commented] (MESOS-8419) RP manager incorrectly setting framework ID leads to CHECK failure

[ https://issues.apache.org/jira/browse/MESOS-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318132#comment-16318132 ] Greg Mann commented on MESOS-8419: -- Review here: https://reviews.apache.org/r/65034/ > RP manager

[jira] [Updated] (MESOS-8419) RP manager incorrectly setting framework ID leads to CHECK failure

[ https://issues.apache.org/jira/browse/MESOS-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-8419: - Sprint: Mesosphere Sprint 72 Story Points: 1 Labels: mesosphere (was: )

[jira] [Created] (MESOS-8419) RP manager incorrectly setting framework ID leads to CHECK failure

Greg Mann created MESOS-8419: Summary: RP manager incorrectly setting framework ID leads to CHECK failure Key: MESOS-8419 URL: https://issues.apache.org/jira/browse/MESOS-8419 Project: Mesos

[jira] [Created] (MESOS-8418) mesos-agent high cpu usage because of numerous /proc/mounts reads

Stéphane Cottin created MESOS-8418: -- Summary: mesos-agent high cpu usage because of numerous /proc/mounts reads Key: MESOS-8418 URL: https://issues.apache.org/jira/browse/MESOS-8418 Project: Mesos

[jira] [Commented] (MESOS-8373) Test reconciliation after operation is dropped en route to agent

[ https://issues.apache.org/jira/browse/MESOS-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318110#comment-16318110 ] Greg Mann commented on MESOS-8373: -- Review here: https://reviews.apache.org/r/65039/ > Test