[
https://issues.apache.org/jira/browse/MESOS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joris Van Remoortere updated MESOS-2025:
----------------------------------------
Description:
Reparenting does not always assign pid 1 (/sbin/init). If there is a user init
such as init --user with some other pid, this will be the new parent.
Modify os_tests to check that the subtree has been reparented to a process
different from its original parent (a.k.a. child) and that it is not a zombie.
was:
Reparenting does not always assign pid 1 (/sbin/init). If there is a user init
such as init --user with some other pid, this will be the new parent.
Modify os_tests to check up the parent tree, and succeed if there is a path to
pid 1 without zombies along the way.
This is not the cleanest fix, but I'm having trouble finding a way to find the
appropriate init to check for.
> OsTest.killtreeNoRoot: Process reparent assumes new parent is init pid 1
> ------------------------------------------------------------------------
>
> Key: MESOS-2025
> URL: https://issues.apache.org/jira/browse/MESOS-2025
> Project: Mesos
> Issue Type: Bug
> Components: stout
> Environment: Ubuntu 14.04 with graphical interface
> Reporter: Joris Van Remoortere
> Assignee: Joris Van Remoortere
> Priority: Minor
>
> Reparenting does not always assign pid 1 (/sbin/init). If there is a user
> init such as init --user with some other pid, this will be the new parent.
> Modify os_tests to check that the subtree has been reparented to a process
> different from its original parent (a.k.a. child) and that it is not a zombie.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
