Release Notes - Mesos - Version 1.3.2 - HTML format

Configure Release Notes

Bug

[MESOS-6743] - Docker executor hangs forever if `docker stop` fails.
[MESOS-6950] - Launching two tasks with the same Docker image simultaneously may cause a staging dir never cleaned up
[MESOS-7627] - Mesos slave stucks
[MESOS-7652] - Docker image with universal containerizer does not work if WORKDIR is missing in the rootfs.
[MESOS-7674] - Update the generic Protobuf to JSON facility to not output deprecated fields.
[MESOS-7744] - Mesos Agent Sends TASK_KILL status update to Master, and still launches task
[MESOS-7783] - Framework might not receive status update when a just launched task is killed immediately
[MESOS-7858] - Launching a nested container with namespace/pid isolation, with glibc < 2.25, may deadlock the LinuxLauncher and MesosContainerizer
[MESOS-7863] - Agent may drop pending kill task status updates.
[MESOS-7865] - Agent may process a kill task and still launch the task.
[MESOS-7872] - Scheduler hang when registration fails.
[MESOS-7909] - Ordering dependency between 'linux/capabilities' and 'docker/runtime' isolator.
[MESOS-7912] - Master WebUI not working in Chrome.
[MESOS-7926] - Abnormal termination of default executor can cause MesosContainerizer::destroy to fail.
[MESOS-7934] - OOM due to LibeventSSLSocket send incorrectly returning 0 after shutdown.
[MESOS-7968] - Handle `/proc/self/ns/pid_for_children` when parsing available namespace.
[MESOS-7969] - Handle cgroups v2 hierarchy when parsing /proc/self/cgroups.
[MESOS-7975] - The command/default/docker executor can incorrectly send a TASK_FINISHED update even when the task is killed
[MESOS-7980] - Stout fails to compile with libc >= 2.26.
[MESOS-8051] - Killing TASK_GROUP fail to kill some tasks
[MESOS-8080] - The default executor does not propagate missing task exit status correctly.
[MESOS-8135] - Masters can lose track of tasks' executor IDs.
[MESOS-8237] - Strip (Offer|Resource).allocation_info for non-MULTI_ROLE schedulers.
[MESOS-8356] - Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - Mesos - Version 1.3.2
                
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-6743'>MESOS-6743</a>] -         Docker executor hangs forever if `docker stop` fails.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-6950'>MESOS-6950</a>] -         Launching two tasks with the same Docker image simultaneously may cause a staging dir never cleaned up
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7627'>MESOS-7627</a>] -         Mesos slave stucks
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7652'>MESOS-7652</a>] -         Docker image with universal containerizer does not work if WORKDIR is missing in the rootfs.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7674'>MESOS-7674</a>] -         Update the generic Protobuf to JSON facility to not output deprecated fields.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7744'>MESOS-7744</a>] -         Mesos Agent Sends TASK_KILL status update to Master, and still launches task
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7783'>MESOS-7783</a>] -         Framework might not receive status update when a just launched task is killed immediately
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7858'>MESOS-7858</a>] -         Launching a nested container with namespace/pid isolation, with glibc &lt; 2.25, may deadlock the LinuxLauncher and MesosContainerizer
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7863'>MESOS-7863</a>] -         Agent may drop pending kill task status updates.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7865'>MESOS-7865</a>] -         Agent may process a kill task and still launch the task.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7872'>MESOS-7872</a>] -         Scheduler hang when registration fails.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7909'>MESOS-7909</a>] -         Ordering dependency between &#39;linux/capabilities&#39; and &#39;docker/runtime&#39; isolator.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7912'>MESOS-7912</a>] -         Master WebUI not working in Chrome.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7926'>MESOS-7926</a>] -         Abnormal termination of default executor can cause MesosContainerizer::destroy to fail. 
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7934'>MESOS-7934</a>] -         OOM due to LibeventSSLSocket send incorrectly returning 0 after shutdown.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7968'>MESOS-7968</a>] -         Handle `/proc/self/ns/pid_for_children` when parsing available namespace.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7969'>MESOS-7969</a>] -         Handle cgroups v2 hierarchy when parsing /proc/self/cgroups.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7975'>MESOS-7975</a>] -         The command/default/docker executor can incorrectly send a TASK_FINISHED update even when the task is killed
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-7980'>MESOS-7980</a>] -         Stout fails to compile with libc &gt;= 2.26.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-8051'>MESOS-8051</a>] -         Killing TASK_GROUP fail to kill some tasks
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-8080'>MESOS-8080</a>] -         The default executor does not propagate missing task exit status correctly.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-8135'>MESOS-8135</a>] -         Masters can lose track of tasks&#39; executor IDs.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-8237'>MESOS-8237</a>] -         Strip (Offer|Resource).allocation_info for non-MULTI_ROLE schedulers.
</li>
<li>[<a href='https://issues.apache.org/jira/browse/MESOS-8356'>MESOS-8356</a>] -         Persistent volume ownership is set to root despite of sandbox owner (frameworkInfo.user) when docker executor is used
</li>
</ul>