[
https://issues.apache.org/jira/browse/MESOS-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542751#comment-15542751
]
Dan Osborne commented on MESOS-6282:
------------------------------------
Agreed, but I think it'd be a good idea to print a low-level log message
(INFO?) even when exit status is 0 as well.
> CNI isolator should print plugin's stderr
> -----------------------------------------
>
> Key: MESOS-6282
> URL: https://issues.apache.org/jira/browse/MESOS-6282
> Project: Mesos
> Issue Type: Improvement
> Components: containerization, isolation, network
> Reporter: Dan Osborne
> Assignee: Avinash Sridharan
>
> It's quite difficult for both Operators and CNI plugin developers to diagnose
> CNI plugin errors in production or in test when the only error information
> available is the stdout error string returned by the plugin (assuming it
> managed to even print its correctly formatted text to stdout).
> Many CNI plugins print logging information to stderr, [as per the CNI
> spec|https://github.com/containernetworking/cni/blob/master/SPEC.md#result]:
> bq. In addition, stderr can be used for unstructured output such as logs.
> Therefore, I propose the Mesos CNI Isolator capture the CNI plugin's stderr
> output and log it to the Agent Logs, for easier diagnosis.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
