[jira] [Commented] (MESOS-9575) Mesos Web UI can't display relative timestamps in the future
[
https://issues.apache.org/jira/browse/MESOS-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769093#comment-16769093
]
Armand Grillet commented on MESOS-9575:
---
relative-date has not been updated since 2011:
https://github.com/azer/relative-date
We could use https://github.com/moment/moment/ which can [parse UNIX
timestamps|https://momentjs.com/docs/#/parsing/unix-timestamp/] and return
relative dates in the past and the future:
{noformat}
moment("20111031", "MMDD").fromNow(); // 7 years ago
moment().startOf('day').fromNow();// 10 hours ago
moment().endOf('day').fromNow(); // in 14 hours
{noformat}
> Mesos Web UI can't display relative timestamps in the future
>
>
> Key: MESOS-9575
> URL: https://issues.apache.org/jira/browse/MESOS-9575
> Project: Mesos
> Issue Type: Bug
>Reporter: Benno Evers
>Priority: Major
>
> The `relativeDate()` function used by the Mesos WebUI
> (https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=src/webui/assets/libs/relative-date.js;hb=HEAD)
> is only able to handle dates in the past. All dates in the future are
> rendered as "just now".
> This can be especially confusing when posting maintenance windows, where
> usually both dates are in the future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9514) Reviewboard bot fails on verify-reviews.py.
[
https://issues.apache.org/jira/browse/MESOS-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738010#comment-16738010
]
Armand Grillet commented on MESOS-9514:
---
https://reviews.apache.org/r/69697/
https://reviews.apache.org/r/69698/
> Reviewboard bot fails on verify-reviews.py.
> ---
>
> Key: MESOS-9514
> URL: https://issues.apache.org/jira/browse/MESOS-9514
> Project: Mesos
> Issue Type: Bug
> Components: build
>Reporter: Till Toenshoff
>Assignee: Armand Grillet
>Priority: Critical
>
> Seeing this on our Azure based Mesos CI for review requests.
> {noformat}
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on dummy-slave-01 (dummy-slave) in workspace
> /home/jenkins/workspace/mesos-reviewbot
> > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
> > git config remote.origin.url https://github.com/apache/mesos # timeout=10
> Pruning obsolete local branches
> Cleaning workspace
> > git rev-parse --verify HEAD # timeout=10
> Resetting working tree
> > git reset --hard # timeout=10
> > git clean -fdx # timeout=10
> Fetching upstream changes from https://github.com/apache/mesos
> > git --version # timeout=10
> > git fetch --tags --progress https://github.com/apache/mesos
> +refs/heads/*:refs/remotes/origin/* --prune
> > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> Checking out Revision 3478e344fb77d931f6122980c6e94cd3913c441d
> (refs/remotes/origin/master)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 3478e344fb77d931f6122980c6e94cd3913c441d
> Commit message: "Sent SIGKILL to I/O switchboard server as a safeguard."
> > git rev-list --no-walk 3478e344fb77d931f6122980c6e94cd3913c441d #
> timeout=10
> [mesos-reviewbot] $ /usr/bin/env bash /tmp/jenkins5023908134863801311.sh
> git rev-parse HEAD
> Traceback (most recent call last):
> File
> "/home/jenkins/workspace/mesos-reviewbot/mesos/support/verify-reviews.py",
> line 101, in
> HEAD = shell("git rev-parse HEAD")
> File
> "/home/jenkins/workspace/mesos-reviewbot/mesos/support/verify-reviews.py",
> line 97, in shell
> out = subprocess.check_output(command, stderr=subprocess.STDOUT,
> shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'git rev-parse HEAD' returned non-zero
> exit status 128
> Build step 'Execute shell' marked build as failure
> Finished: FAILURE
> {noformat}
> This is happening pretty much exactly since we landed
> https://github.com/apache/mesos/commit/3badf7179992e61f30f5a79da9d481dd451c7c2f#diff-0bcbb572aad3fe39e0e5c3c8a8c3e515
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-7278) Implement configuration reader/writer for the new CLI
[ https://issues.apache.org/jira/browse/MESOS-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16703585#comment-16703585 ] Armand Grillet commented on MESOS-7278: --- https://reviews.apache.org/r/68785/ > Implement configuration reader/writer for the new CLI > - > > Key: MESOS-7278 > URL: https://issues.apache.org/jira/browse/MESOS-7278 > Project: Mesos > Issue Type: Task > Components: cli >Reporter: Eric Chung >Assignee: Eric Chung >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8495) Use tree structure in Roles tab
[
https://issues.apache.org/jira/browse/MESOS-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700446#comment-16700446
]
Armand Grillet commented on MESOS-8495:
---
I have checked some libraries that we could use to resolve this ticket, I have
not found one that is based on Angular and has all the features we want:
https://docs.google.com/spreadsheets/d/1DVpulpfZkzc_oLNCrmFmnCzV9j58Fc6WHl33BI-bMiA/edit#gid=0
> Use tree structure in Roles tab
> ---
>
> Key: MESOS-8495
> URL: https://issues.apache.org/jira/browse/MESOS-8495
> Project: Mesos
> Issue Type: Task
> Components: webui
>Reporter: Armand Grillet
>Assignee: Armand Grillet
>Priority: Major
> Labels: multi-tenancy
> Attachments: Screen Shot 2018-01-26 à 13.21.06.png
>
>
> Current table structure:
> !Screen Shot 2018-01-26 à 13.21.06.png!
> Instead, we should display by default:
> * slave_public
> * dcos-edgelb_pools_edgelb-persistent-pool-role
> * kubernetes-role
> Even better, we should have a way to collapse all the {{slave_public/}} roles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9398) post-reviews.py fails to update an existing chain.
[
https://issues.apache.org/jira/browse/MESOS-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697820#comment-16697820
]
Armand Grillet commented on MESOS-9398:
---
Marking this ticket as "Reviewable" while we check if
e6b507b6469553725c98b953f9578ab3f1a40b93 improves the situation.
> post-reviews.py fails to update an existing chain.
> --
>
> Key: MESOS-9398
> URL: https://issues.apache.org/jira/browse/MESOS-9398
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.8.0
>Reporter: Till Toenshoff
>Assignee: Armand Grillet
>Priority: Major
> Labels: reviewboard
>
> My current branch, all commits beyond master's tipp are:
> {noformat}
> commit fbf64ee88c41d7ce1a964197a5fd8900a3157fad (HEAD ->
> ci/till/master-authz-fix-3, origin/ci/till/master-authz-fix-3, backup)
> Author: Till Toenshoff
> Date: Sun Nov 18 16:56:21 2018 +0100
> Added test for ACCESS_MESOS_LOG authorization.
> commit 7b02bac16d74a80fc72cd02514fb115a9084cf87
> Author: Till Toenshoff
> Date: Sun Nov 18 18:02:54 2018 +0100
> Refactored createSubject and authorizeLogAccess to common/authorization.
> Moves 'createSubject' out of common/http into common/authorization.
> Removes duplicate 'authorizeLogAccess' out of master.cpp and slave.cpp.
> Introduces 'authorizeLogAccess' within common/authorization.
> commit e4ef89597d8ba99b060ede5d64388041edc6e3d0
> Author: Till Toenshoff
> Date: Sun Nov 18 18:00:47 2018 +0100
> Introduced common/authorization and refactored collectAuthorizations.
> Adds a new collection of authorization specific helper/s to reduce code
> duplication and increase efficient test coverage.
> Moves the newly introduced 'collectAuthorizations' helper into this new
> authorization source unit.
> commit 4180d433893ec2940c74556b959e9444cef9ad02
> Author: Till Toenshoff
> Date: Sat Nov 17 23:39:35 2018 +0100
> Added collectAuthorizations helper to master.hpp.
> Adds the helper function 'collectAuthorizations' to master.hpp. This
> function allows for a simple way to collect authorization futures and
> only if all supplied futures result in an approved authorization will
> the returned future return true.
> All identified areas that were formally triggering MESOS-9317 are
> being updated to make use of this new helper.
> A helper function has been chosen and preferred over copying this
> pattern into the areas that needed a fix to allow for an efficient and
> complete test coverage.
> Additionally we are adding a test validating that new helper.
> Review: https://reviews.apache.org/r/69369/
> commit 7c3e73231ec8eb663299dc868f75aea51f2daae7
> Author: Till Toenshoff
> Date: Sat Nov 17 23:39:23 2018 +0100
> Added test reproducing crash on authorization failure.
> This test reproduces the scenario as described in MESOS-9317. The test
> attempts to create a persistent volume by a web request to the
> authorized V1 operator endpoint. The test assures that the underlying
> authorization request fails as it can in production due to failures in
> the authorization backend.
> Without fixing MESOS-9317, this test crashes the master process as the
> code-path involved will attempt to access the contents of the awaited
> future even though the future had failed.
> Review: https://reviews.apache.org/r/69368/
> {noformat}
> When trying to use post-reviews.py, things appear rather quirky...
> step 1:
> {noformat}
> $ ./support/post-reviews.py
> Running 'rbt post' across all of ...
> fbf64ee88c41d7ce1a964197a5fd8900a3157fad - (HEAD ->
> ci/till/master-authz-fix-3, origin/ci/till/master-authz-fix-3, backup) Added
> test for ACCESS_MESOS_LOG authorization. (31 minutes ago)
> 7b02bac16d74a80fc72cd02514fb115a9084cf87 - Refactored createSubject and
> authorizeLogAccess to common/authorization. (31 minutes ago)
> e4ef89597d8ba99b060ede5d64388041edc6e3d0 - Introduced common/authorization
> and refactored collectAuthorizations. (31 minutes ago)
> 4180d433893ec2940c74556b959e9444cef9ad02 - Added collectAuthorizations helper
> to master.hpp. (31 minutes ago)
> 7c3e73231ec8eb663299dc868f75aea51f2daae7 - Added test reproducing crash on
> authorization failure. (31 minutes ago)
> Updating diff of:
> 7c3e73231ec8eb663299dc868f75aea51f2daae7 - Added test reproducing crash on
> authorization failure. (31 minutes ago)
> Press enter to continue or 'Ctrl-C' to skip.
> {noformat}
> Pressing 'enter', awaiting step 2:
> {noformat}
> Review request #69368 posted.
> https://reviews.apache.org/r/69368/
> https://reviews.apache.org/r/69368/diff/
> Updating diff of:
> 4180d433893ec2940c74556b959e9444cef9ad02 - Added collectAuthorizations helper
> to master.hpp. (32 minutes ago)
> ... with parent diff
[jira] [Commented] (MESOS-9398) post-reviews.py fails to update an existing chain.
[
https://issues.apache.org/jira/browse/MESOS-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696101#comment-16696101
]
Armand Grillet commented on MESOS-9398:
---
I have faced the same issue and was not able to fix the situation by
cherry-picking.
{noformat}
➜ apache-mesos (MESOS-9399) ✔ support/post-reviews.py
Running 'rbt post' across all of ...
14f2ddf1283016b6f4aedbd26bf2ad98b2eb4ed5 - (HEAD -> MESOS-9399) Added '--all'
flag to 'mesos task list'. (8 seconds ago)
92f74aa144e20c4fa3568aacc66b656ca82c4379 - Replaced CLI test helper function
'running_tasks' by 'wait_for_task'. (8 seconds ago)
8d814a992faac40de7d7869901f872788fcde7f4 - Fixed name of task created when
running mesos-cli-tests. (8 seconds ago)
b9b2080cac081f1f0a4a232f9e88435844107edf - Updated 'mesos task list' to only
display running tasks. (20 seconds ago)
Updating diff of:
b9b2080cac081f1f0a4a232f9e88435844107edf - Updated 'mesos task list' to only
display running tasks. (20 seconds ago)
Press enter to continue or 'Ctrl-C' to skip.
Failed to execute: 'rbt post --markdown --tracking-branch=master
--review-request-id=69394 fcb8e2abeef52042a7f40312c461cab716c0bf3c
1a418847eb152875f1c579e45f6f35733532e3bb':
ERROR: Error validating diff
fatal: git cat-file: could not get object info
(HTTP 400, API Error 224)
➜ apache-mesos (MESOS-9399) ✔ git checkout master
➜ apache-mesos (master) ✔ git checkout -b MESOS-9399-2
➜ apache-mesos (MESOS-9399-2) ✔ git cherry-pick
b9b2080cac081f1f0a4a232f9e88435844107edf
[MESOS-9399-2 015168383] Updated 'mesos task list' to only display running
tasks.
Date: Mon Nov 19 14:05:17 2018 +0100
2 files changed, 10 insertions(+), 7 deletions(-)
➜ apache-mesos (MESOS-9399-2) ✔ support/post-reviews.py
Running 'rbt post' across all of ...
0151683836474223c0d76d779c9e451ba6fdbd88 - (HEAD -> MESOS-9399-2) Updated
'mesos task list' to only display running tasks. (6 seconds ago)
Updating diff of:
0151683836474223c0d76d779c9e451ba6fdbd88 - (HEAD -> MESOS-9399-2) Updated
'mesos task list' to only display running tasks. (6 seconds ago)
Press enter to continue or 'Ctrl-C' to skip.
Failed to execute: 'rbt post --markdown --tracking-branch=master
--review-request-id=69394 fcb8e2abeef52042a7f40312c461cab716c0bf3c
954f9b3cf58aed47f1ea58e57e33491ea9d46a2b':
ERROR: Error validating diff
fatal: git cat-file: could not get object info
(HTTP 400, API Error 224)
➜ apache-mesos (master) ✔ rbt post --markdown --tracking-branch=master
--review-request-id=69394 fcb8e2abeef52042a7f40312c461cab716c0bf3c
0151683836474223c0d76d779c9e451ba6fdbd88
ERROR: Error validating diff
fatal: git cat-file: could not get object info
(HTTP 400, API Error 224)
{noformat}
We can sometimes see the same issue with ReviewBot, like in
https://reviews.apache.org/r/69426/
> post-reviews.py fails to update an existing chain.
> --
>
> Key: MESOS-9398
> URL: https://issues.apache.org/jira/browse/MESOS-9398
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.8.0
>Reporter: Till Toenshoff
>Assignee: Armand Grillet
>Priority: Major
> Labels: reviewboard
>
> My current branch, all commits beyond master's tipp are:
> {noformat}
> commit fbf64ee88c41d7ce1a964197a5fd8900a3157fad (HEAD ->
> ci/till/master-authz-fix-3, origin/ci/till/master-authz-fix-3, backup)
> Author: Till Toenshoff
> Date: Sun Nov 18 16:56:21 2018 +0100
> Added test for ACCESS_MESOS_LOG authorization.
> commit 7b02bac16d74a80fc72cd02514fb115a9084cf87
> Author: Till Toenshoff
> Date: Sun Nov 18 18:02:54 2018 +0100
> Refactored createSubject and authorizeLogAccess to common/authorization.
> Moves 'createSubject' out of common/http into common/authorization.
> Removes duplicate 'authorizeLogAccess' out of master.cpp and slave.cpp.
> Introduces 'authorizeLogAccess' within common/authorization.
> commit e4ef89597d8ba99b060ede5d64388041edc6e3d0
> Author: Till Toenshoff
> Date: Sun Nov 18 18:00:47 2018 +0100
> Introduced common/authorization and refactored collectAuthorizations.
> Adds a new collection of authorization specific helper/s to reduce code
> duplication and increase efficient test coverage.
> Moves the newly introduced 'collectAuthorizations' helper into this new
> authorization source unit.
> commit 4180d433893ec2940c74556b959e9444cef9ad02
> Author: Till Toenshoff
> Date: Sat Nov 17 23:39:35 2018 +0100
> Added collectAuthorizations helper to master.hpp.
> Adds the helper function 'collectAuthorizations' to master.hpp. This
> function allows for a simple way to collect authorization futures and
> only if all supplied futures result in an approved authorization will
> the returned future return true.
> All identified areas that were formally triggering MESOS-9317
[jira] [Created] (MESOS-9399) Update 'mesos task list' to only list running tasks
Armand Grillet created MESOS-9399:
-
Summary: Update 'mesos task list' to only list running tasks
Key: MESOS-9399
URL: https://issues.apache.org/jira/browse/MESOS-9399
Project: Mesos
Issue Type: Task
Components: cli
Reporter: Armand Grillet
Assignee: Armand Grillet
Doing a {{mesos task list}} currently returns all tasks that have ever been run
(not just running tasks). The default behavior should be to return only the
running tasks and offer an option to return all of them. To tell them apart,
there should be a state field in the table returned by this command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-9398) post-reviews.py fails to update an existing chain.
[
https://issues.apache.org/jira/browse/MESOS-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-9398:
-
Assignee: Armand Grillet
> post-reviews.py fails to update an existing chain.
> --
>
> Key: MESOS-9398
> URL: https://issues.apache.org/jira/browse/MESOS-9398
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.8.0
>Reporter: Till Toenshoff
>Assignee: Armand Grillet
>Priority: Major
> Labels: reviewboard
>
> My current branch, all commits beyond master's tipp are:
> {noformat}
> commit fbf64ee88c41d7ce1a964197a5fd8900a3157fad (HEAD ->
> ci/till/master-authz-fix-3, origin/ci/till/master-authz-fix-3, backup)
> Author: Till Toenshoff
> Date: Sun Nov 18 16:56:21 2018 +0100
> Added test for ACCESS_MESOS_LOG authorization.
> commit 7b02bac16d74a80fc72cd02514fb115a9084cf87
> Author: Till Toenshoff
> Date: Sun Nov 18 18:02:54 2018 +0100
> Refactored createSubject and authorizeLogAccess to common/authorization.
> Moves 'createSubject' out of common/http into common/authorization.
> Removes duplicate 'authorizeLogAccess' out of master.cpp and slave.cpp.
> Introduces 'authorizeLogAccess' within common/authorization.
> commit e4ef89597d8ba99b060ede5d64388041edc6e3d0
> Author: Till Toenshoff
> Date: Sun Nov 18 18:00:47 2018 +0100
> Introduced common/authorization and refactored collectAuthorizations.
> Adds a new collection of authorization specific helper/s to reduce code
> duplication and increase efficient test coverage.
> Moves the newly introduced 'collectAuthorizations' helper into this new
> authorization source unit.
> commit 4180d433893ec2940c74556b959e9444cef9ad02
> Author: Till Toenshoff
> Date: Sat Nov 17 23:39:35 2018 +0100
> Added collectAuthorizations helper to master.hpp.
> Adds the helper function 'collectAuthorizations' to master.hpp. This
> function allows for a simple way to collect authorization futures and
> only if all supplied futures result in an approved authorization will
> the returned future return true.
> All identified areas that were formally triggering MESOS-9317 are
> being updated to make use of this new helper.
> A helper function has been chosen and preferred over copying this
> pattern into the areas that needed a fix to allow for an efficient and
> complete test coverage.
> Additionally we are adding a test validating that new helper.
> Review: https://reviews.apache.org/r/69369/
> commit 7c3e73231ec8eb663299dc868f75aea51f2daae7
> Author: Till Toenshoff
> Date: Sat Nov 17 23:39:23 2018 +0100
> Added test reproducing crash on authorization failure.
> This test reproduces the scenario as described in MESOS-9317. The test
> attempts to create a persistent volume by a web request to the
> authorized V1 operator endpoint. The test assures that the underlying
> authorization request fails as it can in production due to failures in
> the authorization backend.
> Without fixing MESOS-9317, this test crashes the master process as the
> code-path involved will attempt to access the contents of the awaited
> future even though the future had failed.
> Review: https://reviews.apache.org/r/69368/
> {noformat}
> When trying to use post-reviews.py, things appear rather quirky...
> step 1:
> {noformat}
> $ ./support/post-reviews.py
> Running 'rbt post' across all of ...
> fbf64ee88c41d7ce1a964197a5fd8900a3157fad - (HEAD ->
> ci/till/master-authz-fix-3, origin/ci/till/master-authz-fix-3, backup) Added
> test for ACCESS_MESOS_LOG authorization. (31 minutes ago)
> 7b02bac16d74a80fc72cd02514fb115a9084cf87 - Refactored createSubject and
> authorizeLogAccess to common/authorization. (31 minutes ago)
> e4ef89597d8ba99b060ede5d64388041edc6e3d0 - Introduced common/authorization
> and refactored collectAuthorizations. (31 minutes ago)
> 4180d433893ec2940c74556b959e9444cef9ad02 - Added collectAuthorizations helper
> to master.hpp. (31 minutes ago)
> 7c3e73231ec8eb663299dc868f75aea51f2daae7 - Added test reproducing crash on
> authorization failure. (31 minutes ago)
> Updating diff of:
> 7c3e73231ec8eb663299dc868f75aea51f2daae7 - Added test reproducing crash on
> authorization failure. (31 minutes ago)
> Press enter to continue or 'Ctrl-C' to skip.
> {noformat}
> Pressing 'enter', awaiting step 2:
> {noformat}
> Review request #69368 posted.
> https://reviews.apache.org/r/69368/
> https://reviews.apache.org/r/69368/diff/
> Updating diff of:
> 4180d433893ec2940c74556b959e9444cef9ad02 - Added collectAuthorizations helper
> to master.hpp. (32 minutes ago)
> ... with parent diff created from:
> 7c3e73231ec8eb663299dc868f75aea51f2daae7 - Added test reproducing crash on
> authorization failure. (33
[jira] [Assigned] (MESOS-9211) Add new commands to make the CLI useful in production
[ https://issues.apache.org/jira/browse/MESOS-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-9211: - Assignee: Armand Grillet > Add new commands to make the CLI useful in production > - > > Key: MESOS-9211 > URL: https://issues.apache.org/jira/browse/MESOS-9211 > Project: Mesos > Issue Type: Epic >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-5278) Add command to enter container namespaces and execute arbitrary commands
[ https://issues.apache.org/jira/browse/MESOS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-5278: - Assignee: Armand Grillet (was: Guangya Liu) > Add command to enter container namespaces and execute arbitrary commands > > > Key: MESOS-5278 > URL: https://issues.apache.org/jira/browse/MESOS-5278 > Project: Mesos > Issue Type: Improvement >Reporter: Jie Yu >Assignee: Armand Grillet >Priority: Major > > Containers created by the unified containerizer (Mesos containerizer) uses > various namespaces (e.g., mount, network, etc.). > To improve debugability, we should create a CLI that allows an operator or a > user to enter the namespaces associated with the container, and execute an > arbitrary command in that container (similar to `docker exec`). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9396) Use the built CLI binary when running new CLI integration tests in CI
Armand Grillet created MESOS-9396: - Summary: Use the built CLI binary when running new CLI integration tests in CI Key: MESOS-9396 URL: https://issues.apache.org/jira/browse/MESOS-9396 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet We currently use the CLI in the virtual environment which is just a Python file being interpreted, we should instead use the binary built by PyInstaller as it is what is gonna be used in production. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9370) Unable to build new Mesos CLI with PyInstaller due to lack of Python 3.7 support
Armand Grillet created MESOS-9370:
-
Summary: Unable to build new Mesos CLI with PyInstaller due to
lack of Python 3.7 support
Key: MESOS-9370
URL: https://issues.apache.org/jira/browse/MESOS-9370
Project: Mesos
Issue Type: Bug
Reporter: Armand Grillet
Assignee: Armand Grillet
Building the new Mesos CLI with Python 3.7 and PyInstaller 3.3.1 (our current
dependencu) on your machine currently creates a binary that is not working:
{noformat}
➜ build (master) ✔ ./src/mesos
Fatal Python error: initfsencoding: unable to load the file system codec
zipimport.ZipImportError: can't find module 'encodings'
Current thread 0x000110e145c0 (most recent call first):
[1]83095 abort ./src/mesos
{noformat}
As seen in https://github.com/pyinstaller/pyinstaller/issues/3219, this is due
to PyInstaller.
We need to update the PyInstaller dependency to have a version that supports
Python 3.7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9363) Improve task exec to return correct exit status
Armand Grillet created MESOS-9363:
-
Summary: Improve task exec to return correct exit status
Key: MESOS-9363
URL: https://issues.apache.org/jira/browse/MESOS-9363
Project: Mesos
Issue Type: Task
Components: cli
Reporter: Armand Grillet
Assignee: Armand Grillet
Whatever the exit, {{mesos task exec}} always returns 0. We need to fix that to
return the correct status code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9350) CLI build step is broken with CMake due to missing file.
Armand Grillet created MESOS-9350:
-
Summary: CLI build step is broken with CMake due to missing file.
Key: MESOS-9350
URL: https://issues.apache.org/jira/browse/MESOS-9350
Project: Mesos
Issue Type: Bug
Reporter: Armand Grillet
Assignee: Armand Grillet
Fix For: 1.8.0
The file {{mesos.py}} was not added to {{CLI_FILES}} and this is now an issue
when building the CLI using CMake.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-9343) Add test(s) for `mesos task attach` on task launched with a TTY
[ https://issues.apache.org/jira/browse/MESOS-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-9343: - Assignee: Armand Grillet > Add test(s) for `mesos task attach` on task launched with a TTY > > > Key: MESOS-9343 > URL: https://issues.apache.org/jira/browse/MESOS-9343 > Project: Mesos > Issue Type: Task > Components: cli >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > As a source, we could use the tests in > https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-9342) Add interactive test(s) for `mesos task exec`
[ https://issues.apache.org/jira/browse/MESOS-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-9342: - Assignee: Armand Grillet > Add interactive test(s) for `mesos task exec` > - > > Key: MESOS-9342 > URL: https://issues.apache.org/jira/browse/MESOS-9342 > Project: Mesos > Issue Type: Task > Components: cli >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > As a source, we could use the tests in > https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py > This will require new helper functions to get the input/output of the command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-9341) Add non-interactive test(s) for `mesos task exec`
[ https://issues.apache.org/jira/browse/MESOS-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-9341: - Assignee: Armand Grillet > Add non-interactive test(s) for `mesos task exec` > - > > Key: MESOS-9341 > URL: https://issues.apache.org/jira/browse/MESOS-9341 > Project: Mesos > Issue Type: Task > Components: cli >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > As a source, we could use the tests in > https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9344) Add test for `mesos task exec` on task launched without a TTY
Armand Grillet created MESOS-9344: - Summary: Add test for `mesos task exec` on task launched without a TTY Key: MESOS-9344 URL: https://issues.apache.org/jira/browse/MESOS-9344 Project: Mesos Issue Type: Task Components: cli Reporter: Armand Grillet As a source, we could use the tests in https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9343) Add test(s) for `mesos task exec` on task launched with a TTY
Armand Grillet created MESOS-9343: - Summary: Add test(s) for `mesos task exec` on task launched with a TTY Key: MESOS-9343 URL: https://issues.apache.org/jira/browse/MESOS-9343 Project: Mesos Issue Type: Task Components: cli Reporter: Armand Grillet As a source, we could use the tests in https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9342) Add interactive test(s) for `mesos task exec`
Armand Grillet created MESOS-9342: - Summary: Add interactive test(s) for `mesos task exec` Key: MESOS-9342 URL: https://issues.apache.org/jira/browse/MESOS-9342 Project: Mesos Issue Type: Task Components: cli Reporter: Armand Grillet As a source, we could use the tests in https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py This will require new helper functions to get the input/output of the command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9341) Add non-interactive test(s) for `mesos task exec`
Armand Grillet created MESOS-9341: - Summary: Add non-interactive test(s) for `mesos task exec` Key: MESOS-9341 URL: https://issues.apache.org/jira/browse/MESOS-9341 Project: Mesos Issue Type: Task Reporter: Armand Grillet As a source, we could use the tests in https://github.com/dcos/dcos-core-cli/blob/b930d2004dceb47090004ab658f35cb608bc70e4/python/lib/dcoscli/tests/integrations/test_task.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9333) Document usage and build of new Mesos CLI
Armand Grillet created MESOS-9333: - Summary: Document usage and build of new Mesos CLI Key: MESOS-9333 URL: https://issues.apache.org/jira/browse/MESOS-9333 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet Stating how to compile and use the Mesos CLI + its limitations (only Mesos containerizer, exec DEBUG follows task-user). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8495) Use tree structure in Roles tab
[
https://issues.apache.org/jira/browse/MESOS-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646149#comment-16646149
]
Armand Grillet commented on MESOS-8495:
---
Having a tree view that we can collapse, filter, and update in real time is a
challenge. Many tree views made for Angular exist such as
https://leovo2708.github.io/ngx-treeview/#/components but they don't respect
our three constraints, have real-time updates being the most difficult one.
From the libraries I have seen right now, we would need to create a custom
component having its own "table like" UI with a way to do real-time updates.
> Use tree structure in Roles tab
> ---
>
> Key: MESOS-8495
> URL: https://issues.apache.org/jira/browse/MESOS-8495
> Project: Mesos
> Issue Type: Task
> Components: webui
>Reporter: Armand Grillet
>Assignee: Armand Grillet
>Priority: Major
> Labels: multi-tenancy
> Attachments: Screen Shot 2018-01-26 à 13.21.06.png
>
>
> Current table structure:
> !Screen Shot 2018-01-26 à 13.21.06.png!
> Instead, we should display by default:
> * slave_public
> * dcos-edgelb_pools_edgelb-persistent-pool-role
> * kubernetes-role
> Even better, we should have a way to collapse all the {{slave_public/}} roles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16644471#comment-16644471
]
Armand Grillet commented on MESOS-9253:
---
Review request submitted: https://reviews.apache.org/r/68970/
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1665#comment-1665
]
Armand Grillet commented on MESOS-9253:
---
We can see in the last comment of https://reviews.apache.org/r/68965/ that a
Python 3.5 interpreter is now used to run the script and returns a type error.
Working on a fix.
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642867#comment-16642867
]
Armand Grillet commented on MESOS-9253:
---
[~vinodkone] The last four runs seem successful, the Jenkins UI is not great
and I am thus unable to check if this is an improvement due to the code that
landed. Can you please check and update this ticket status accordingly?
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642248#comment-16642248
]
Armand Grillet commented on MESOS-9253:
---
Review request submitted: https://reviews.apache.org/r/68951/
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642225#comment-16642225
]
Armand Grillet commented on MESOS-9253:
---
>From the Jenkins logs, ReviewBot uses Ubuntu 16.04 [which has been updated to
>have Python
>3.6|https://github.com/apache/mesos/commit/cbdb6a5e1c0bb2e61dd0887cfae424ac2422b94d].
>
The issue is here:
https://github.com/apache/mesos/blob/e135b7f2175c01fd67b71b22cdc325ac37853a9d/support/verify-reviews.py#L97
Instead of using the current interpreter (which is Python 3), we specify
{{python}} which is generally still Python 2 following the guidelines given in
https://lists.apache.org/thread.html/c54687ca13873f9b4d06b0e40944c6c8494b8d6a88313336e3a886c6@%3Cdev.mesos.apache.org%3E
I'm going to send a review request changing the line in {{verify-reviews.py}}
to use the current interpreter instead of a hardcoded {{python}}, this should
solve the issue.
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-9253:
-
Assignee: Armand Grillet
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Armand Grillet
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642070#comment-16642070
]
Armand Grillet commented on MESOS-9253:
---
I see the fail in
[https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23458/console,]
gonna investigate in the coming hours.
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9253) Reviewbot is failing when posting a review
[
https://issues.apache.org/jira/browse/MESOS-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641963#comment-16641963
]
Armand Grillet commented on MESOS-9253:
---
[~vinodkone] I've seen this error if {{python}} is Python 2. {{python3
support/apply-reviews.py -n -r 68640}} should work.
> Reviewbot is failing when posting a review
> --
>
> Key: MESOS-9253
> URL: https://issues.apache.org/jira/browse/MESOS-9253
> Project: Mesos
> Issue Type: Bug
>Reporter: Vinod Kone
>Priority: Critical
>
> Observed this in CI.
> [https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Reviewbot/23425/console]
>
> {code}
> 09-23-18_02:12:05 - Running
> /home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py
> Checking if review 68640 needs verification
> Skipping blocking review 68640
> Checking if review 68641 needs verification
> Patch never verified, needs verification
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Verifying review 68641
> Dependent review: [https://reviews.apache.org/api/review-requests/68640/]
> Applying review 68640
> python support/apply-reviews.py -n -r 68640
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 156, in verify_review
> apply_reviews(review_request, reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 120, in apply_reviews
> reviews, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 124, in apply_reviews
> apply_review(review_request["id"])
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 97, in apply_review
> shell("python support/apply-reviews.py -n -r %s" % review_id)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 91, in shell
> command, stderr=subprocess.STDOUT, shell=True)
> File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> **kwargs).stdout
> File "/usr/lib/python3.5/subprocess.py", line 708, in run
> output=stdout, stderr=stderr)
> subprocess.CalledProcessError: Command 'python support/apply-reviews.py -n -r
> 68640' returned non-zero exit status 1
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 292, in
> main()
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 286, in main
> verify_review(review_request, handler)
> File
> "/home/jenkins/jenkins-slave/workspace/Mesos-Reviewbot/support/verify-reviews.py",
> line 217, in verify_review
> output += "\nFull log: "
> TypeError: can't concat bytes to str
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: bui...@mesos.apache.org
> Finished: FAILURE
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9211) We need to add new commands to make the CLI useful for devops
Armand Grillet created MESOS-9211: - Summary: We need to add new commands to make the CLI useful for devops Key: MESOS-9211 URL: https://issues.apache.org/jira/browse/MESOS-9211 Project: Mesos Issue Type: Epic Reporter: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-9186) Failed to build Mesos with Python 3.7 and new CLI enabled
[
https://issues.apache.org/jira/browse/MESOS-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-9186:
-
Assignee: Armand Grillet
> Failed to build Mesos with Python 3.7 and new CLI enabled
> -
>
> Key: MESOS-9186
> URL: https://issues.apache.org/jira/browse/MESOS-9186
> Project: Mesos
> Issue Type: Bug
> Components: cli
>Reporter: Robin Gögge
>Assignee: Armand Grillet
>Priority: Minor
>
> I've tried to build Mesos with the flag 'enable-new-cli' and Python 3.7 and
> it failed with this error message:
> {code:java}
> Traceback (most recent call last):
> File "/Users/mesosphere/code/mesos/src/python/cli_new/bin/../tests/main.py",
> line 26, in
> from cli.tests import CLITestCase
> File "/Users/mesosphere/code/mesos/src/python/cli_new/lib/cli/__init__.py",
> line 24, in
> from . import util
> File "/Users/mesosphere/code/mesos/src/python/cli_new/lib/cli/util.py", line
> 29, in
> from kazoo.client import KazooClient
> File
> "/Users/mesosphere/code/mesos/build/src/.virtualenv/lib/python3.7/site-packages/kazoo/client.py",
> line 67, in
> from kazoo.recipe.partitioner import SetPartitioner
> File
> "/Users/mesosphere/code/mesos/build/src/.virtualenv/lib/python3.7/site-packages/kazoo/recipe/partitioner.py",
> line 194
> self._child_watching(self._allocate_transition, async=True)
> ^
> SyntaxError: invalid syntax
> make[3]: *** [check-local] Error 1
> make[2]: *** [check-am] Error 2
> make[1]: *** [check] Error 2
> make: *** [check-recursive] Error 1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9179) ./support/python3/mesos-gtest-runner.py --help crashes
Armand Grillet created MESOS-9179:
-
Summary: ./support/python3/mesos-gtest-runner.py --help crashes
Key: MESOS-9179
URL: https://issues.apache.org/jira/browse/MESOS-9179
Project: Mesos
Issue Type: Bug
Reporter: Armand Grillet
Assignee: Armand Grillet
{noformat}
$ ./support/python3/mesos-gtest-runner.py --help
Traceback (most recent call last):
File "./support/python3/mesos-gtest-runner.py", line 196, in
EXECUTABLE, OPTIONS = parse_arguments()
File "./support/python3/mesos-gtest-runner.py", line 108, in parse_arguments
.format(default_=DEFAULT_NUM_JOBS))
File "/usr/lib64/python3.5/argparse.py", line 1335, in add_argument
raise ValueError('%r is not callable' % (type_func,))
ValueError: 'int' is not callable
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9112) mesos-style reports violations on a clean checkout
[
https://issues.apache.org/jira/browse/MESOS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564101#comment-16564101
]
Armand Grillet commented on MESOS-9112:
---
Thanks for the pylint info!
Your linter gives two errors that I don't have:
{code:java}
* Module mesos.http
E: 25, 0: Unable to import 'urlparse' (import-error)
E: 87,30: Undefined variable 'xrange' (undefined-variable)
Using config file /home/bbannier/src/mesos/support/pylint.config
{code}
And mine gives one error that you don't have:
{code:java}
* Module cli.plugins.task.main
W: 62,12: Unused variable 'master' (unused-variable)
{code}
> mesos-style reports violations on a clean checkout
> --
>
> Key: MESOS-9112
> URL: https://issues.apache.org/jira/browse/MESOS-9112
> Project: Mesos
> Issue Type: Bug
> Components: build, cli, python api
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Major
> Labels: lint, python, style
>
> When running {{support/mesos-style.py}} on a clean checkout of e.g.,
> {{e879e920c35}} Python style violations are reported,
> {noformat}
> Checking 46 Python files
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module cli.plugins.base
> E:119, 0: Bad option value 'R0204' (bad-option-value)
> * Module settings
> E: 32, 4: No name 'VERSION' in module 'version' (no-name-in-module)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module mesos.http
> E: 25, 0: Unable to import 'urlparse' (import-error)
> E: 87,30: Undefined variable 'xrange' (undefined-variable)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module apply-reviews
> R: 99, 0: Either all return statements in a function should return an
> expression, or none of them should. (inconsistent-return-statements)
> C:124, 9: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> R:302, 4: Unnecessary "else" after "return" (no-else-return)
> * Module generate-endpoint-help
> R:215, 4: Unnecessary "else" after "return" (no-else-return)
> * Module verify-reviews
> C:261, 7: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> Total errors found: 9
> {noformat}
> I would expect a clean checkout to not report any violations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-9112) mesos-style reports violations on a clean checkout
[
https://issues.apache.org/jira/browse/MESOS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564080#comment-16564080
]
Armand Grillet commented on MESOS-9112:
---
I have used the script with an environment and got 8 errors instead of 9 (using
the branch master as well):
{code}
$ apache-mesos (master) $ ./support/mesos-style.py
...
Checking 46 Python files
Using config file /Users/Armand/Code/apache-mesos/support/pylint.config
* Module cli.plugins.base
E:119, 0: Bad option value 'R0204' (bad-option-value)
* Module cli.plugins.task.main
W: 62,12: Unused variable 'master' (unused-variable)
* Module settings
E: 32, 4: No name 'VERSION' in module 'version' (no-name-in-module)
Using config file /Users/Armand/Code/apache-mesos/support/pylint.config
* Module apply-reviews
R: 99, 0: Either all return statements in a function should return an
expression, or none of them should. (inconsistent-return-statements)
C:124, 9: Do not use `len(SEQUENCE)` to determine if a sequence is empty
(len-as-condition)
R:302, 4: Unnecessary "else" after "return" (no-else-return)
* Module generate-endpoint-help
R:215, 4: Unnecessary "else" after "return" (no-else-return)
* Module verify-reviews
C:261, 7: Do not use `len(SEQUENCE)` to determine if a sequence is empty
(len-as-condition)
Total errors found: 8
{code}
My environment:
{code}
(linters) ~ $ pylint --version
No config file found, using default configuration
pylint 1.9.2,
astroid 1.6.5
Python 2.7.15 (default, Jun 17 2018, 12:46:58)
[GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.2)]
{code}
Can you please give me what returns {code}pylint --version{code} after doing
{code}source path/to/apache-mesos/support/.virtualenv/bin/activate{code}?
This does not change the issue you reported, I just want to make sure there is
not another one before fixing the errors reported by the linter.
> mesos-style reports violations on a clean checkout
> --
>
> Key: MESOS-9112
> URL: https://issues.apache.org/jira/browse/MESOS-9112
> Project: Mesos
> Issue Type: Bug
> Components: build, cli, python api
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Major
> Labels: lint, python, style
>
> When running {{support/mesos-style.py}} on a clean checkout of e.g.,
> {{e879e920c35}} Python style violations are reported,
> {noformat}
> Checking 46 Python files
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module cli.plugins.base
> E:119, 0: Bad option value 'R0204' (bad-option-value)
> * Module settings
> E: 32, 4: No name 'VERSION' in module 'version' (no-name-in-module)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module mesos.http
> E: 25, 0: Unable to import 'urlparse' (import-error)
> E: 87,30: Undefined variable 'xrange' (undefined-variable)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module apply-reviews
> R: 99, 0: Either all return statements in a function should return an
> expression, or none of them should. (inconsistent-return-statements)
> C:124, 9: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> R:302, 4: Unnecessary "else" after "return" (no-else-return)
> * Module generate-endpoint-help
> R:215, 4: Unnecessary "else" after "return" (no-else-return)
> * Module verify-reviews
> C:261, 7: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> Total errors found: 9
> {noformat}
> I would expect a clean checkout to not report any violations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-9112) mesos-style reports violations on a clean checkout
[
https://issues.apache.org/jira/browse/MESOS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-9112:
-
Assignee: Armand Grillet
> mesos-style reports violations on a clean checkout
> --
>
> Key: MESOS-9112
> URL: https://issues.apache.org/jira/browse/MESOS-9112
> Project: Mesos
> Issue Type: Bug
> Components: build, cli, python api
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Major
> Labels: lint, python, style
>
> When running {{support/mesos-style.py}} on a clean checkout of e.g.,
> {{e879e920c35}} Python style violations are reported,
> {noformat}
> Checking 46 Python files
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module cli.plugins.base
> E:119, 0: Bad option value 'R0204' (bad-option-value)
> * Module settings
> E: 32, 4: No name 'VERSION' in module 'version' (no-name-in-module)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module mesos.http
> E: 25, 0: Unable to import 'urlparse' (import-error)
> E: 87,30: Undefined variable 'xrange' (undefined-variable)
> Using config file /home/bbannier/src/mesos/support/pylint.config
> * Module apply-reviews
> R: 99, 0: Either all return statements in a function should return an
> expression, or none of them should. (inconsistent-return-statements)
> C:124, 9: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> R:302, 4: Unnecessary "else" after "return" (no-else-return)
> * Module generate-endpoint-help
> R:215, 4: Unnecessary "else" after "return" (no-else-return)
> * Module verify-reviews
> C:261, 7: Do not use `len(SEQUENCE)` to determine if a sequence is empty
> (len-as-condition)
> Total errors found: 9
> {noformat}
> I would expect a clean checkout to not report any violations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9075) Virtualenv management in support directory is buggy.
Armand Grillet created MESOS-9075: - Summary: Virtualenv management in support directory is buggy. Key: MESOS-9075 URL: https://issues.apache.org/jira/browse/MESOS-9075 Project: Mesos Issue Type: Bug Affects Versions: 1.7.0 Reporter: Armand Grillet Assignee: Armand Grillet When switching back and forth from Python 2 to 3, the virtualenv does not get correctly reinstalled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9074) Pylint is too noisy when using mesos-style.py
Armand Grillet created MESOS-9074:
-
Summary: Pylint is too noisy when using mesos-style.py
Key: MESOS-9074
URL: https://issues.apache.org/jira/browse/MESOS-9074
Project: Mesos
Issue Type: Bug
Reporter: Armand Grillet
Assignee: Armand Grillet
{code}
apache-mesos (MESOS-9073) $ git commit -m "Test."
No C++ files to lint
No JavaScript files to lint
Checking 1 Python file
Using config file /Users/Armand/Code/apache-mesos/support/pylint.config
---
Your code has been rated at 10.00/10 (previous run: 9.22/10, +0.78)
Total errors found: 0
[MESOS-9073 a3509d402] Test.
1 file changed, 1 insertion(+), 1 deletion(-)
{code}
The score needs to be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9073) Tox doesn't run in the support virtualenv when using Python 3 mesos-style.py
Armand Grillet created MESOS-9073: - Summary: Tox doesn't run in the support virtualenv when using Python 3 mesos-style.py Key: MESOS-9073 URL: https://issues.apache.org/jira/browse/MESOS-9073 Project: Mesos Issue Type: Bug Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9058) ModuleNotFoundError: No module named 'nodeenv' when setting up support virtualenv.
Armand Grillet created MESOS-9058:
-
Summary: ModuleNotFoundError: No module named 'nodeenv' when
setting up support virtualenv.
Key: MESOS-9058
URL: https://issues.apache.org/jira/browse/MESOS-9058
Project: Mesos
Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Armand Grillet
Assignee: Armand Grillet
{code}
apache-mesos (MESOS-8955) $ git rebase -i HEAD
No C++ files to lint
No JavaScript files to lint
Checking 1 Python file
Total errors found: 0
The "pip-requirements.txt" file has changed.
Rebuilding virtualenv...
Traceback (most recent call last):
File "/Users/Armand/Code/apache-mesos/support/.virtualenv/bin/nodeenv", line
7, in
from nodeenv import main
ModuleNotFoundError: No module named 'nodeenv'
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8979) python3/push-commits.py fails due to TypeError
Armand Grillet created MESOS-8979:
-
Summary: python3/push-commits.py fails due to TypeError
Key: MESOS-8979
URL: https://issues.apache.org/jira/browse/MESOS-8979
Project: Mesos
Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Armand Grillet
Assignee: Armand Grillet
{code}
> ./support/python3/push-commits.py
Traceback (most recent call last):
File "./support/python3/push-commits.py", line 158, in
main()
File "./support/python3/push-commits.py", line 111, in main
current_branch = current_branch_ref.replace('refs/heads/', '', 1)
TypeError: a bytes-like object is required, not 'str'
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8965) Use V1 API in Web UI
Armand Grillet created MESOS-8965: - Summary: Use V1 API in Web UI Key: MESOS-8965 URL: https://issues.apache.org/jira/browse/MESOS-8965 Project: Mesos Issue Type: Task Components: webui Reporter: Armand Grillet Assignee: Armand Grillet Using libraries such as [https://github.com/dcos-labs/mesos-client] and a new build system using npm and webpack, we can simplify the structure of the Web UI while using a more modern UI and really stream the state of the cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8957) Install Python 3 on Mesos CI instances
Armand Grillet created MESOS-8957: - Summary: Install Python 3 on Mesos CI instances Key: MESOS-8957 URL: https://issues.apache.org/jira/browse/MESOS-8957 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8955) If Python 3 is used as default python, Python bindings should not be buildable
Armand Grillet created MESOS-8955: - Summary: If Python 3 is used as default python, Python bindings should not be buildable Key: MESOS-8955 URL: https://issues.apache.org/jira/browse/MESOS-8955 Project: Mesos Issue Type: Bug Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8954) python3/post-reviews.py errors due to TypeError
Armand Grillet created MESOS-8954:
-
Summary: python3/post-reviews.py errors due to TypeError
Key: MESOS-8954
URL: https://issues.apache.org/jira/browse/MESOS-8954
Project: Mesos
Issue Type: Bug
Reporter: Armand Grillet
Assignee: Armand Grillet
{code:java}
$ ./support/python3/post-reviews.py
Running 'rbt post' across all of ...
7a662ee75d706d637f9cc2bcbdd0567c32ccef56 - (HEAD -> alexr/subscribers-health,
private/ci/alexr/default) Sent task (health) check updates over the operator
streaming API. (2 minutes ago)
Creating diff of:
7a662ee75d706d637f9cc2bcbdd0567c32ccef56 - (HEAD -> alexr/subscribers-health,
private/ci/alexr/default) Sent task (health) check updates over the operator
streaming API.
Press enter to continue or 'Ctrl-C' to skip.
Traceback (most recent call last):
File "./support/python3/post-reviews.py", line 432, in
main()
File "./support/python3/post-reviews.py", line 365, in main
sys.stdout.buffer.write(output)
TypeError: a bytes-like object is required, not 'str'{code}
The review still get posted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-8934) Update python.m4 to support Python 3
[ https://issues.apache.org/jira/browse/MESOS-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490561#comment-16490561 ] Armand Grillet commented on MESOS-8934: --- https://reviews.apache.org/r/67318/ > Update python.m4 to support Python 3 > > > Key: MESOS-8934 > URL: https://issues.apache.org/jira/browse/MESOS-8934 > Project: Mesos > Issue Type: Task >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > [https://github.com/apache/mesos/commit/9fca9176d2e8a69b2e37aae6c1481ea887cb5b25] > [https://lists.nongnu.org/archive/html/bug-automake/2018-03/msg2.html] > https://github.com/autoconf-archive/autoconf-archive/blob/master/m4/ax_python.m4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-8883) Send email to dev list concerning the Python 3 update
[
https://issues.apache.org/jira/browse/MESOS-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-8883:
-
Assignee: Armand Grillet (was: Andrew Schwartzmeyer)
> Send email to dev list concerning the Python 3 update
> -
>
> Key: MESOS-8883
> URL: https://issues.apache.org/jira/browse/MESOS-8883
> Project: Mesos
> Issue Type: Task
>Affects Versions: 1.6.0
>Reporter: Armand Grillet
>Assignee: Armand Grillet
>Priority: Major
>
> Let's prepare an email for the dev community to express our wish and reasons
> to add a {{python3}} dependency to the Mesos codebase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-8883) Send email to dev list concerning the Python 3 update
[
https://issues.apache.org/jira/browse/MESOS-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489794#comment-16489794
]
Armand Grillet commented on MESOS-8883:
---
I have prepared something:
{code}
Hi all,
Python 2.7 will retire on January 1, 2020 and we currently use it for
our support scripts, our Python bindings, and our new CLI.
Starting July 1, 2018 you will need to have Python 3.6 on your computer
in order to use the support scripts. It is available on all the
operating systems we support and even preinstalled on most recent Linux
distributions. This change is due to issues with our support scripts on
Windows and upcoming work on the CLI.
If you already have Python 3.6 installed on your machine, great.
Otherwise, you will see a deprecation message when you use the support
scripts and the related git hooks. Don't worry, these messages and the
switch to Python 3 do not change how the scripts work.
We now have a chain ready offering Python 3 support scripts alongside
the existing ones. Having a duplicated codebase is not sustainable and
we thus plan on deprecating the Python 2 support scripts by July 1st.
We want to have a few weeks to test these new scripts thoroughly and let
you install Python 3.6, this is why we have decided to have both
codebases during a few weeks.
If you want to use the new scripts, set in your environment the variable
`MESOSSUPPORTPYTHON` to `3` and run again the bash support script
`build-virtualenv`. You will then use the Python 3 scripts by default.
If you have any questions, please answer to this thread or join the
Mesos Slack channel #python3.
PS: This Python 3 switch does not apply to the rest of our codebase yet.
As we have seen in a previous thread, some developers still rely on the
Python 2 bindings and we do not want to disturb that.
{code}
> Send email to dev list concerning the Python 3 update
> -
>
> Key: MESOS-8883
> URL: https://issues.apache.org/jira/browse/MESOS-8883
> Project: Mesos
> Issue Type: Task
>Affects Versions: 1.6.0
>Reporter: Armand Grillet
>Assignee: Andrew Schwartzmeyer
>Priority: Major
>
> Let's prepare an email for the dev community to express our wish and reasons
> to add a {{python3}} dependency to the Mesos codebase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-7163) python: Produce python3 compatible python bindings
[
https://issues.apache.org/jira/browse/MESOS-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480727#comment-16480727
]
Armand Grillet commented on MESOS-7163:
---
interface:
{code}
RefactoringTool: Refactored ./src/mesos/interface/__init__.py
--- ./src/mesos/interface/__init__.py (original)
+++ ./src/mesos/interface/__init__.py (refactored)
@@ -20,7 +20,7 @@
"""Python bindings for Mesos."""
-from __future__ import print_function
+
import sys
{code}
lib:
{code}
RefactoringTool: Refactored ./mesos/exceptions.py
--- ./mesos/exceptions.py (original)
+++ ./mesos/exceptions.py (refactored)
@@ -18,7 +18,7 @@
Exceptions Classes
"""
-from __future__ import absolute_import
+
class MesosException(Exception):
RefactoringTool: Refactored ./mesos/http.py
--- ./mesos/http.py (original)
+++ ./mesos/http.py (refactored)
@@ -20,9 +20,9 @@
Classes and functions for interacting with the Mesos HTTP RESTful API
"""
-from __future__ import absolute_import
-
-from urlparse import urlparse
+
+
+from urllib.parse import urlparse
from copy import deepcopy
import requests
@@ -84,7 +84,7 @@
default timeout for connections, default headers to be included in each
request, and auth.
"""
-SUCCESS_CODES = frozenset(xrange(200, 300))
+SUCCESS_CODES = frozenset(range(200, 300))
ERROR_CODE_MAP = {c.STATUS_CODE: c for c in (
MesosBadRequestException,
MesosAuthenticationException,
RefactoringTool: No changes to ./tests/__init__.py
RefactoringTool: Refactored ./tests/conftest.py
--- ./tests/conftest.py (original)
+++ ./tests/conftest.py (refactored)
@@ -18,7 +18,7 @@
PyTest configuration
"""
-from __future__ import absolute_import
+
import mock
import pytest
RefactoringTool: No changes to ./tests/test_exceptions.py
RefactoringTool: Refactored ./tests/test_http.py
--- ./tests/test_http.py(original)
+++ ./tests/test_http.py(refactored)
@@ -16,7 +16,7 @@
# pylint:
disable=missing-docstring,protected-access,too-many-locals,too-many-arguments
-from __future__ import absolute_import
+
from collections import namedtuple
RefactoringTool: Refactored ./tests/test_mesos.py
--- ./tests/test_mesos.py (original)
+++ ./tests/test_mesos.py (refactored)
@@ -18,7 +18,7 @@
Tests for the mesos package
"""
-from __future__ import absolute_import
+
import mesos
{code}
That seems to be it.
> python: Produce python3 compatible python bindings
> --
>
> Key: MESOS-7163
> URL: https://issues.apache.org/jira/browse/MESOS-7163
> Project: Mesos
> Issue Type: Bug
> Components: python api
>Reporter: Anthony Sottile
>Priority: Minor
>
> We're looking to migrate a codebase using mesos to use python3. Some of the
> mesos python apis already seem to work though the cpython bindings will need
> some tweaking.
> This is probably blocked on producing source distributions, I'll link that
> ticket.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-4054) Evaluate python-compatibility of python bindings and utilities
[
https://issues.apache.org/jira/browse/MESOS-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480726#comment-16480726
]
Armand Grillet commented on MESOS-4054:
---
For the Python bindings:
interface:
{code}
RefactoringTool: Refactored ./src/mesos/interface/__init__.py
--- ./src/mesos/interface/__init__.py (original)
+++ ./src/mesos/interface/__init__.py (refactored)
@@ -20,7 +20,7 @@
"""Python bindings for Mesos."""
-from __future__ import print_function
+
import sys
{code}
lib:
{code}
RefactoringTool: Refactored ./mesos/exceptions.py
--- ./mesos/exceptions.py (original)
+++ ./mesos/exceptions.py (refactored)
@@ -18,7 +18,7 @@
Exceptions Classes
"""
-from __future__ import absolute_import
+
class MesosException(Exception):
RefactoringTool: Refactored ./mesos/http.py
--- ./mesos/http.py (original)
+++ ./mesos/http.py (refactored)
@@ -20,9 +20,9 @@
Classes and functions for interacting with the Mesos HTTP RESTful API
"""
-from __future__ import absolute_import
-
-from urlparse import urlparse
+
+
+from urllib.parse import urlparse
from copy import deepcopy
import requests
@@ -84,7 +84,7 @@
default timeout for connections, default headers to be included in each
request, and auth.
"""
-SUCCESS_CODES = frozenset(xrange(200, 300))
+SUCCESS_CODES = frozenset(range(200, 300))
ERROR_CODE_MAP = {c.STATUS_CODE: c for c in (
MesosBadRequestException,
MesosAuthenticationException,
RefactoringTool: No changes to ./tests/__init__.py
RefactoringTool: Refactored ./tests/conftest.py
--- ./tests/conftest.py (original)
+++ ./tests/conftest.py (refactored)
@@ -18,7 +18,7 @@
PyTest configuration
"""
-from __future__ import absolute_import
+
import mock
import pytest
RefactoringTool: No changes to ./tests/test_exceptions.py
RefactoringTool: Refactored ./tests/test_http.py
--- ./tests/test_http.py(original)
+++ ./tests/test_http.py(refactored)
@@ -16,7 +16,7 @@
# pylint:
disable=missing-docstring,protected-access,too-many-locals,too-many-arguments
-from __future__ import absolute_import
+
from collections import namedtuple
RefactoringTool: Refactored ./tests/test_mesos.py
--- ./tests/test_mesos.py (original)
+++ ./tests/test_mesos.py (refactored)
@@ -18,7 +18,7 @@
Tests for the mesos package
"""
-from __future__ import absolute_import
+
import mesos
{code}
That seems to be it.
> Evaluate python-compatibility of python bindings and utilities
> --
>
> Key: MESOS-4054
> URL: https://issues.apache.org/jira/browse/MESOS-4054
> Project: Mesos
> Issue Type: Task
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Minor
>
> In many places our python tools do not enforce a particular python version
> but call the first {{python}} from {{env}} (likely python2).
> We likely rely on some python2 constructs which can be easily migrated to a
> python3 equivalent (e.g., {{print}} vs. {{print_function}}). Let's evaluate
> what else we use and how much effort it would be to support both python2 and
> python3. If we can collect information on what minimal python version is
> required right we should also collect that to see what is available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-4054) Evaluate python-compatibility of python bindings and utilities
[
https://issues.apache.org/jira/browse/MESOS-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-4054:
-
Assignee: Armand Grillet
> Evaluate python-compatibility of python bindings and utilities
> --
>
> Key: MESOS-4054
> URL: https://issues.apache.org/jira/browse/MESOS-4054
> Project: Mesos
> Issue Type: Task
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Minor
>
> In many places our python tools do not enforce a particular python version
> but call the first {{python}} from {{env}} (likely python2).
> We likely rely on some python2 constructs which can be easily migrated to a
> python3 equivalent (e.g., {{print}} vs. {{print_function}}). Let's evaluate
> what else we use and how much effort it would be to support both python2 and
> python3. If we can collect information on what minimal python version is
> required right we should also collect that to see what is available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8934) Update python.m4 to support Python 3
Armand Grillet created MESOS-8934: - Summary: Update python.m4 to support Python 3 Key: MESOS-8934 URL: https://issues.apache.org/jira/browse/MESOS-8934 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet https://github.com/apache/mesos/commit/9fca9176d2e8a69b2e37aae6c1481ea887cb5b25 https://lists.nongnu.org/archive/html/bug-automake/2018-03/msg2.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8910) Update cpplint to a version supporting Python 3
[ https://issues.apache.org/jira/browse/MESOS-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478862#comment-16478862 ] Armand Grillet commented on MESOS-8910: --- https://reviews.apache.org/r/67055/ > Update cpplint to a version supporting Python 3 > --- > > Key: MESOS-8910 > URL: https://issues.apache.org/jira/browse/MESOS-8910 > Project: Mesos > Issue Type: Task >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-7658) apply-reviews.py fails with Unicode characters
[
https://issues.apache.org/jira/browse/MESOS-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-7658:
-
Assignee: Armand Grillet (was: Andrew Schwartzmeyer)
> apply-reviews.py fails with Unicode characters
> --
>
> Key: MESOS-7658
> URL: https://issues.apache.org/jira/browse/MESOS-7658
> Project: Mesos
> Issue Type: Bug
>Reporter: Andrew Schwartzmeyer
>Assignee: Armand Grillet
>Priority: Major
> Labels: reviewboard
>
> This prevents commits from being applied if the name or message contains
> non-ASCII characters, and so can break the Windows ReviewBot.
> {code}
> > git checkout b2801f0012535e29609f603b4324a9ca693f70cb~
> > python .\support\apply-reviews.py -r 59874
> Traceback (most recent call last):
> File ".\support\apply-reviews.py", line 381, in
> reviewboard()
> File ".\support\apply-reviews.py", line 360, in reviewboard
> apply_review()
> File ".\support\apply-reviews.py", line 126, in apply_review
> commit_patch()
> File ".\support\apply-reviews.py", line 225, in commit_patch
> shell(cmd, options['dry_run'])
> File ".\support\apply-reviews.py", line 111, in shell
> error_code = subprocess.call(command, stderr=subprocess.STDOUT,
> shell=True)
> File "C:\Python27\lib\subprocess.py", line 168, in call
> return Popen(*popenargs, **kwargs).wait()
> File "C:\Python27\lib\subprocess.py", line 390, in __init__
> errread, errwrite)
> File "C:\Python27\lib\subprocess.py", line 610, in _execute_child
> args = '{} /c "{}"'.format (comspec, args)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in position
> 25: ordinal not in range(128)
> ~\src\mesos-copy2 |-/
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-8918) Mesos UI should show count of frameworks
[ https://issues.apache.org/jira/browse/MESOS-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-8918: - Assignee: Armand Grillet > Mesos UI should show count of frameworks > > > Key: MESOS-8918 > URL: https://issues.apache.org/jira/browse/MESOS-8918 > Project: Mesos > Issue Type: Improvement > Components: webui >Reporter: Vinod Kone >Assignee: Armand Grillet >Priority: Major > > Right now, it's really hard to know the number of frameworks registered with > a master from the WebUI. Neither the home tab nor the frameworks tab has this > information. > > Some options: > In the side bar in the home page, add a section for frameworks (active, > inactive, completed) just like existing sections for agents, tasks and > resources. > In the frameworks tab, show the counts in the titles of Active, Inactive and > Complete tables. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8910) Update cpplint to a version supporting Python 3
Armand Grillet created MESOS-8910: - Summary: Update cpplint to a version supporting Python 3 Key: MESOS-8910 URL: https://issues.apache.org/jira/browse/MESOS-8910 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-8770) Use Python3 for Mesos support scripts
[
https://issues.apache.org/jira/browse/MESOS-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-8770:
-
Assignee: Armand Grillet
> Use Python3 for Mesos support scripts
> -
>
> Key: MESOS-8770
> URL: https://issues.apache.org/jira/browse/MESOS-8770
> Project: Mesos
> Issue Type: Task
>Reporter: Benjamin Bannier
>Assignee: Armand Grillet
>Priority: Major
>
> Our Python scripts under {{support/}} currently implicitly assume that
> developers have a python2 environment as their primary Python installation.
> We should consider updating these scripts so that they can be used with a
> python3 installation as well. There exist [some
> resources|http://python-future.org/overview.html#automatic-conversion-to-py2-3-compatible-code]
> on the web documenting best practices and tools for automatic rewrites which
> should get us a long way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8903) Update the Python CLI to use Python 3
Armand Grillet created MESOS-8903: - Summary: Update the Python CLI to use Python 3 Key: MESOS-8903 URL: https://issues.apache.org/jira/browse/MESOS-8903 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8894) Write documentation page regarding Python support in Mesos
Armand Grillet created MESOS-8894: - Summary: Write documentation page regarding Python support in Mesos Key: MESOS-8894 URL: https://issues.apache.org/jira/browse/MESOS-8894 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-7163) python: Produce python3 compatible python bindings
[ https://issues.apache.org/jira/browse/MESOS-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467370#comment-16467370 ] Armand Grillet commented on MESOS-7163: --- [~asottileyelp] Would this ticket still be doable by you? > python: Produce python3 compatible python bindings > -- > > Key: MESOS-7163 > URL: https://issues.apache.org/jira/browse/MESOS-7163 > Project: Mesos > Issue Type: Bug > Components: python api >Reporter: Anthony Sottile >Priority: Minor > > We're looking to migrate a codebase using mesos to use python3. Some of the > mesos python apis already seem to work though the cpython bindings will need > some tweaking. > This is probably blocked on producing source distributions, I'll link that > ticket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8882) Add Python 3 as a dependency and use it for our Python codebase
[
https://issues.apache.org/jira/browse/MESOS-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464396#comment-16464396
]
Armand Grillet commented on MESOS-8882:
---
[~andschwa] Thank you for your feedback and first patch! I have edited the
ticket following your first comment.
Yes, pyenv is still the standard way to go for versioning.
Will take a look at #66964 during the next days, I have read the description
and testing done and I am now looking at how to handle {{pylint}} with the
situation we will have.
> Add Python 3 as a dependency and use it for our Python codebase
> ---
>
> Key: MESOS-8882
> URL: https://issues.apache.org/jira/browse/MESOS-8882
> Project: Mesos
> Issue Type: Epic
> Components: cli, python api
>Reporter: Armand Grillet
>Priority: Major
>
> As mentioned by [~andschwa] [2 weeks
> ago|https://mesos.slack.com/archives/C1LPTK50T/p1524165786000521], nothing
> new should use Python 2. [~cinchurge] and [~ArmandGrillet] are currently
> working on the CLI while being shepherded by [~klueska] and, as we plan to do
> more work on it soon, mentioned again today that it would be a good time to
> start using Python 3 in our codebase.
> We use Python 2 in four areas of the Mesos codebase:
> * In the support scripts.
> * In the new CLI.
> * In the new Mesos Python package.
> * In the Python bindings.
> The support scripts and CLI can be updated independently of the switch if we
> assume that most of our devs have Python 2 and 3 installed on their machines.
> The Python can be updated last as they should not be used anymore, in favor
> of our V1 API.
> This new dependency will require changes in our documentation regarding how
> to build Python. As it will be a change for Mesos devs, we have to express
> the reasons behind this change and check if it could cause any issue on their
> side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8883) Send email to dev list concerning the Python 3 update
Armand Grillet created MESOS-8883:
-
Summary: Send email to dev list concerning the Python 3 update
Key: MESOS-8883
URL: https://issues.apache.org/jira/browse/MESOS-8883
Project: Mesos
Issue Type: Task
Affects Versions: 1.6.0
Reporter: Armand Grillet
Assignee: Andrew Schwartzmeyer
Let's prepare an email for the dev community to express our wish and reasons to
add a {{python3}} dependency to the Mesos codebase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8882) Python 2 is still used for our CLI, support scripts, and bindings. With Python 3 becoming a standard, development starts being hard and we should move to Python 3.
Armand Grillet created MESOS-8882: - Summary: Python 2 is still used for our CLI, support scripts, and bindings. With Python 3 becoming a standard, development starts being hard and we should move to Python 3. Key: MESOS-8882 URL: https://issues.apache.org/jira/browse/MESOS-8882 Project: Mesos Issue Type: Epic Components: cli, python api Reporter: Armand Grillet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8817) GSOC: Upgrade Mesos Web UI backend to use V1 Operator API
Armand Grillet created MESOS-8817: - Summary: GSOC: Upgrade Mesos Web UI backend to use V1 Operator API Key: MESOS-8817 URL: https://issues.apache.org/jira/browse/MESOS-8817 Project: Mesos Issue Type: Task Components: webui Reporter: Armand Grillet This is a project IDEA for [Google Summer of Code|https://summerofcode.withgoogle.com/] (GSOC). To discuss this or other ideas with your potential mentor from the Apache Mesos project, sign up and post to the [d...@mesos.apache.org|mailto:d...@mesos.apache.org] list, including "[GSOC]" in the subject. You can also comment this Jira issue if you have an account. h2. What is the issue? The Mesos UI currently uses [unversioned REST endpoints|http://mesos.apache.org/documentation/latest/endpoints/] to show data regarding the cluster. Best practices would be to use the newer [Operator HTTP API|http://mesos.apache.org/documentation/latest/operator-http-api/] instead, but this upgrade requires changes in the backend that have not been done yet. Using this new API would allow us in the future to stream the state of the cluster and thus have a more responsive and easily upgradable UI. h2. What would you do during your Summer of Code? This project would require an upgrade of our current Angular web app to send new types of requests (e.g. Mesos can answer synchronously or not) and read from endpoints returning different information compared to the old ones. This project is also the opportunity to improve the organization of our Angular controllers to have a more straightfoward logic from getting the data to showing it to the users. h2. Who will help you? If you accept to work on this project, you will be mentored by [Armand Grillet|https://reviews.apache.org/users/ArmandGrillet/] and shepherded by [Benjamin Mahler|https://reviews.apache.org/users/bmahler/]. Benjamin has maintained the Mesos Web UI for 5 years and I am currently working on improvements to it (more front-end related). We both have a keen interest in improving this Mesos component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8025) Update the master field in the new CLI config to accept a URL instead of an
[ https://issues.apache.org/jira/browse/MESOS-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442474#comment-16442474 ] Armand Grillet commented on MESOS-8025: --- https://reviews.apache.org/r/66683/ > Update the master field in the new CLI config to accept a URL instead of an > > - > > Key: MESOS-8025 > URL: https://issues.apache.org/jira/browse/MESOS-8025 > Project: Mesos > Issue Type: Improvement > Components: cli > Environment: This will be useful in cases where the master is behind > a proxy or when the master is sitting directly on port 80. >Reporter: Kevin Klues >Assignee: Armand Grillet >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8795) Catch up new CLI features to be the same as the old one.
Armand Grillet created MESOS-8795: - Summary: Catch up new CLI features to be the same as the old one. Key: MESOS-8795 URL: https://issues.apache.org/jira/browse/MESOS-8795 Project: Mesos Issue Type: Task Reporter: Armand Grillet Assignee: Armand Grillet https://github.com/mesosphere/mesos-cli -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8779) Create .mesos/config.toml automatically if it does not exist for CLI.
Armand Grillet created MESOS-8779:
-
Summary: Create .mesos/config.toml automatically if it does not
exist for CLI.
Key: MESOS-8779
URL: https://issues.apache.org/jira/browse/MESOS-8779
Project: Mesos
Issue Type: Improvement
Reporter: Armand Grillet
Assignee: Armand Grillet
Instead of printing an error message, the CLI should create an empty file
{{config.toml}} if it does not exist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8775) Restructure Web UI to make updates simpler to do.
Armand Grillet created MESOS-8775: - Summary: Restructure Web UI to make updates simpler to do. Key: MESOS-8775 URL: https://issues.apache.org/jira/browse/MESOS-8775 Project: Mesos Issue Type: Improvement Reporter: Armand Grillet Assignee: Armand Grillet The controllers are currently all in a file called controllers.js and the webui has a very nested structure, both can be improved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8589) click "master" on the Mesos UI returns blank page, need refresh to show
[ https://issues.apache.org/jira/browse/MESOS-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430838#comment-16430838 ] Armand Grillet commented on MESOS-8589: --- Same issue on Google Chrome, doesn't work on 1.5.0 but does on 1.4.2. > click "master" on the Mesos UI returns blank page, need refresh to show > --- > > Key: MESOS-8589 > URL: https://issues.apache.org/jira/browse/MESOS-8589 > Project: Mesos > Issue Type: Bug > Components: webui >Affects Versions: 1.5.0 >Reporter: Meng Zhu >Priority: Major > Labels: ui > Attachments: Screen Shot 2018-02-15 at 1.46.30 PM.png > > > When click the "mater" tab in the following page (image attached), it will > return a blank page. Needs to hit refresh to get page loaded (using safari on > Mac OSX) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8308) CommandExecutorCheckTest.CommandCheckTimeout is flaky on Windows
[
https://issues.apache.org/jira/browse/MESOS-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415007#comment-16415007
]
Armand Grillet commented on MESOS-8308:
---
+1, failing consistently on my updated/new review requests.
> CommandExecutorCheckTest.CommandCheckTimeout is flaky on Windows
>
>
> Key: MESOS-8308
> URL: https://issues.apache.org/jira/browse/MESOS-8308
> Project: Mesos
> Issue Type: Bug
> Environment: Windows 10
>Reporter: Andrew Schwartzmeyer
>Assignee: Eric Mumau
>Priority: Major
> Labels: executor, windows
>
> The test {{CommandExecutorCheckTest.CommandCheckTimeout}} can be flaky on
> Windows. If the system is under heavy load, the PowerShell command can fail
> poorly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-8240) Add an option to build the new CLI and run unit tests.
[ https://issues.apache.org/jira/browse/MESOS-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383600#comment-16383600 ] Armand Grillet commented on MESOS-8240: --- https://reviews.apache.org/r/65705/ > Add an option to build the new CLI and run unit tests. > -- > > Key: MESOS-8240 > URL: https://issues.apache.org/jira/browse/MESOS-8240 > Project: Mesos > Issue Type: Improvement > Components: cli >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > An update of the discarded [https://reviews.apache.org/r/52543/] > Also needs to be available for CMake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-7971) PersistentVolumeEndpointsTest.EndpointCreateThenOfferRemove test if flaky
[
https://issues.apache.org/jira/browse/MESOS-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371372#comment-16371372
]
Armand Grillet commented on MESOS-7971:
---
Looks like it's happening again:
https://reviews.apache.org/r/64211/#review197842
> PersistentVolumeEndpointsTest.EndpointCreateThenOfferRemove test if flaky
> -
>
> Key: MESOS-7971
> URL: https://issues.apache.org/jira/browse/MESOS-7971
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Vinod Kone
>Priority: Major
> Labels: flaky-test, mesosphere
>
> Saw this when testing 1.4.0-rc5
> {code}
> [ RUN ] PersistentVolumeEndpointsTest.EndpointCreateThenOfferRemove
> I0912 05:40:27.335222 30860 cluster.cpp:162] Creating default 'local'
> authorizer
> I0912 05:40:27.338429 30867 master.cpp:442] Master
> 2bd1e8eb-e314-4181-9ed3-d397ec1dbede (6aa774430302) started on
> 172.17.0.3:54639
> I0912 05:40:27.338472 30867 master.cpp:444] Flags at startup: --acls=""
> --agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
> --allocation_interval="50ms" --allocator="HierarchicalDRF"
> --authenticate_agents="true" --authenticate_frameworks="true"
> --authenticate_http_frameworks="true" --authenticate_http_readonly="true"
> --authenticate_http_readwrite="true" --authenticators="crammd5"
> --authorizers="local" --credentials="/tmp/hH0YXe/credentials"
> --filter_gpu_resources="true" --framework_sorter="drf" --help="false"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_framework_authenticators="basic" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_agent_ping_timeouts="5" --max_completed_frameworks="50"
> --max_completed_tasks_per_framework="1000"
> --max_unreachable_tasks_per_framework="1000" --port="5050" --quiet="false"
> --recovery_agent_removal_limit="100%" --registry="in_memory"
> --registry_fetch_timeout="1mins" --registry_gc_interval="15mins"
> --registry_max_agent_age="2weeks" --registry_max_agent_count="102400"
> --registry_store_timeout="100secs" --registry_strict="false" --roles="role1"
> --root_submissions="true" --user_sorter="drf" --version="false"
> --webui_dir="/usr/local/share/mesos/webui" --work_dir="/tmp/hH0YXe/master"
> --zk_session_timeout="10secs"
> I0912 05:40:27.338778 30867 master.cpp:494] Master only allowing
> authenticated frameworks to register
> I0912 05:40:27.338788 30867 master.cpp:508] Master only allowing
> authenticated agents to register
> I0912 05:40:27.338793 30867 master.cpp:521] Master only allowing
> authenticated HTTP frameworks to register
> I0912 05:40:27.338799 30867 credentials.hpp:37] Loading credentials for
> authentication from '/tmp/hH0YXe/credentials'
> I0912 05:40:27.353009 30867 master.cpp:566] Using default 'crammd5'
> authenticator
> I0912 05:40:27.353183 30867 http.cpp:1026] Creating default 'basic' HTTP
> authenticator for realm 'mesos-master-readonly'
> I0912 05:40:27.353364 30867 http.cpp:1026] Creating default 'basic' HTTP
> authenticator for realm 'mesos-master-readwrite'
> I0912 05:40:27.353482 30867 http.cpp:1026] Creating default 'basic' HTTP
> authenticator for realm 'mesos-master-scheduler'
> I0912 05:40:27.353588 30867 master.cpp:646] Authorization enabled
> W0912 05:40:27.353605 30867 master.cpp:709] The '--roles' flag is deprecated.
> This flag will be removed in the future. See the Mesos 0.27 upgrade notes for
> more information
> I0912 05:40:27.353742 30868 hierarchical.cpp:171] Initialized hierarchical
> allocator process
> I0912 05:40:27.353775 30872 whitelist_watcher.cpp:77] No whitelist given
> I0912 05:40:27.356655 30873 master.cpp:2163] Elected as the leading master!
> I0912 05:40:27.356675 30873 master.cpp:1702] Recovering from registrar
> I0912 05:40:27.356868 30874 registrar.cpp:347] Recovering registrar
> I0912 05:40:27.357390 30874 registrar.cpp:391] Successfully fetched the
> registry (0B) in 494080ns
> I0912 05:40:27.357483 30874 registrar.cpp:495] Applied 1 operations in
> 31911ns; attempting to update the registry
> I0912 05:40:27.357919 30874 registrar.cpp:552] Successfully updated the
> registry in 391936ns
> I0912 05:40:27.358018 30874 registrar.cpp:424] Successfully recovered
> registrar
> I0912 05:40:27.358413 30868 master.cpp:1801] Recovered 0 agents from the
> registry (129B); allowing 10mins for agents to re-register
> I0912 05:40:27.358482 30867 hierarchical.cpp:209] Skipping recovery of
> hierarchical allocator: nothing to recover
> W0912 05:40:27.364050 30860 process.cpp:3196] Attempted to spawn already
> running process files@172.17.0.3:54639
> I0912 05:40:27.365372 30860 containerizer.cpp:246] Using isolation:
>
[jira] [Created] (MESOS-8583) Autotools and Cmake do not give the same permissions on files in build/bin/.
Armand Grillet created MESOS-8583:
-
Summary: Autotools and Cmake do not give the same permissions on
files in build/bin/.
Key: MESOS-8583
URL: https://issues.apache.org/jira/browse/MESOS-8583
Project: Mesos
Issue Type: Bug
Components: build
Affects Versions: 1.6.0
Reporter: Armand Grillet
Using CMake, the files in {{build/bin}} will have for access rights:
{code:java}
ls -l
total 84
-rw--x. 1 agrillet agrillet 1583 Feb 14 10:13 gdb-mesos-agent.sh
-rw--x. 1 agrillet agrillet 1577 Feb 14 10:13 gdb-mesos-local.sh
-rw--x. 1 agrillet agrillet 1586 Feb 14 10:13 gdb-mesos-master.sh
-rw--x. 1 agrillet agrillet 1554 Feb 14 10:13 gdb-mesos-tests.sh
-rw--x. 1 agrillet agrillet 1543 Feb 14 10:13 lldb-mesos-agent.sh
-rw--x. 1 agrillet agrillet 1545 Feb 14 10:13 lldb-mesos-local.sh
-rw--x. 1 agrillet agrillet 1548 Feb 14 10:13 lldb-mesos-master.sh
-rw--x. 1 agrillet agrillet 1522 Feb 14 10:13 lldb-mesos-tests.sh
-rw--x. 1 agrillet agrillet 1840 Feb 14 10:13 mesos-agent-flags.sh
-rw--x. 1 agrillet agrillet 1047 Feb 14 10:13 mesos-agent.sh
-rw--x. 1 agrillet agrillet 929 Feb 14 10:13 mesos-local-flags.sh
-rw--x. 1 agrillet agrillet 1053 Feb 14 10:13 mesos-local.sh
-rw--x. 1 agrillet agrillet 892 Feb 14 10:13 mesos-master-flags.sh
-rw--x. 1 agrillet agrillet 1056 Feb 14 10:13 mesos-master.sh
-rw--x. 1 agrillet agrillet 1200 Feb 14 10:13 mesos.sh
-rw--x. 1 agrillet agrillet 901 Feb 14 10:13 mesos-tests-flags.sh
-rw--x. 1 agrillet agrillet 1056 Feb 14 10:13 mesos-tests.sh
-rw--x. 1 agrillet agrillet 1825 Feb 14 10:13 valgrind-mesos-agent.sh
-rw--x. 1 agrillet agrillet 1825 Feb 14 10:13 valgrind-mesos-local.sh
-rw--x. 1 agrillet agrillet 1828 Feb 14 10:13 valgrind-mesos-master.sh
-rw--x. 1 agrillet agrillet 1825 Feb 14 10:13 valgrind-mesos-tests.sh{code}
Using Autotools, the permissions are not the same:
{code}
ls -l
total 104
-rwxrwxr-x. 1 agrillet agrillet 1592 Feb 14 10:32 gdb-mesos-agent.sh
-rwxrwxr-x. 1 agrillet agrillet 1586 Feb 14 10:32 gdb-mesos-local.sh
-rwxrwxr-x. 1 agrillet agrillet 1595 Feb 14 10:32 gdb-mesos-master.sh
-rwxrwxr-x. 1 agrillet agrillet 1592 Feb 14 10:32 gdb-mesos-slave.sh
-rwxrwxr-x. 1 agrillet agrillet 1563 Feb 14 10:32 gdb-mesos-tests.sh
-rwxrwxr-x. 1 agrillet agrillet 1552 Feb 14 10:32 lldb-mesos-agent.sh
-rwxrwxr-x. 1 agrillet agrillet 1554 Feb 14 10:32 lldb-mesos-local.sh
-rwxrwxr-x. 1 agrillet agrillet 1557 Feb 14 10:32 lldb-mesos-master.sh
-rwxrwxr-x. 1 agrillet agrillet 1552 Feb 14 10:32 lldb-mesos-slave.sh
-rwxrwxr-x. 1 agrillet agrillet 1531 Feb 14 10:32 lldb-mesos-tests.sh
-rw-rw-r--. 1 agrillet agrillet 1840 Feb 14 10:32 mesos-agent-flags.sh
-rwxrwxr-x. 1 agrillet agrillet 1047 Feb 14 10:32 mesos-agent.sh
-rw-rw-r--. 1 agrillet agrillet 929 Feb 14 10:32 mesos-local-flags.sh
-rwxrwxr-x. 1 agrillet agrillet 1053 Feb 14 10:32 mesos-local.sh
-rw-rw-r--. 1 agrillet agrillet 901 Feb 14 10:32 mesos-master-flags.sh
-rwxrwxr-x. 1 agrillet agrillet 1056 Feb 14 10:32 mesos-master.sh
-rwxrwxr-x. 1 agrillet agrillet 1209 Feb 14 10:32 mesos.sh
-rw-rw-r--. 1 agrillet agrillet 1840 Feb 14 10:32 mesos-slave-flags.sh
-rwxrwxr-x. 1 agrillet agrillet 1047 Feb 14 10:32 mesos-slave.sh
-rw-rw-r--. 1 agrillet agrillet 901 Feb 14 10:32 mesos-tests-flags.sh
-rwxrwxr-x. 1 agrillet agrillet 1056 Feb 14 10:32 mesos-tests.sh
-rwxrwxr-x. 1 agrillet agrillet 1834 Feb 14 10:32 valgrind-mesos-agent.sh
-rwxrwxr-x. 1 agrillet agrillet 1834 Feb 14 10:32 valgrind-mesos-local.sh
-rwxrwxr-x. 1 agrillet agrillet 1837 Feb 14 10:32 valgrind-mesos-master.sh
-rwxrwxr-x. 1 agrillet agrillet 1834 Feb 14 10:32 valgrind-mesos-slave.sh
-rwxrwxr-x. 1 agrillet agrillet 1834 Feb 14 10:32 valgrind-mesos-tests.sh
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-8579) Autotools always rebuilds things when Python enabled
Armand Grillet created MESOS-8579:
-
Summary: Autotools always rebuilds things when Python enabled
Key: MESOS-8579
URL: https://issues.apache.org/jira/browse/MESOS-8579
Project: Mesos
Issue Type: Bug
Components: build
Reporter: Armand Grillet
Attachments: make.txt
See file attached, the second {{build (MESOS-8240)$ nice make -j16}} should not
do anything but it does.
Configuration: {{../configure --disable-java}}
After doing {{../configure --disable-java --disable-python}}, the issue is gone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-8240) Add an option to build the new CLI and run unit tests.
[ https://issues.apache.org/jira/browse/MESOS-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358496#comment-16358496 ] Armand Grillet commented on MESOS-8240: --- https://reviews.apache.org/r/65585 > Add an option to build the new CLI and run unit tests. > -- > > Key: MESOS-8240 > URL: https://issues.apache.org/jira/browse/MESOS-8240 > Project: Mesos > Issue Type: Improvement >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > An update of the discarded [https://reviews.apache.org/r/52543/] > Also needs to be available for CMake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8240) Add an option to build the new CLI and run unit tests.
[ https://issues.apache.org/jira/browse/MESOS-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353730#comment-16353730 ] Armand Grillet commented on MESOS-8240: --- https://reviews.apache.org/r/65529/ > Add an option to build the new CLI and run unit tests. > -- > > Key: MESOS-8240 > URL: https://issues.apache.org/jira/browse/MESOS-8240 > Project: Mesos > Issue Type: Improvement >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > An update of the discarded [https://reviews.apache.org/r/52543/] > Also needs to be available for CMake. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-8503) Improve UI when displaying frameworks with many roles.
[ https://issues.apache.org/jira/browse/MESOS-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-8503: - Assignee: Armand Grillet > Improve UI when displaying frameworks with many roles. > -- > > Key: MESOS-8503 > URL: https://issues.apache.org/jira/browse/MESOS-8503 > Project: Mesos > Issue Type: Task >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > Attachments: Screen Shot 2018-01-29 à 10.38.05.png > > > The /roles UI endpoint displays all the roles of each framework in a table: > !Screen Shot 2018-01-29 à 10.38.05.png! > This is not readable if a framework has many roles. We thus need to provide a > solution to only display a few roles per framework and show more when a user > wants to see all of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MESOS-8503) Improve UI when displaying frameworks with many roles.
[ https://issues.apache.org/jira/browse/MESOS-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet updated MESOS-8503: -- Shepherd: Benjamin Mahler > Improve UI when displaying frameworks with many roles. > -- > > Key: MESOS-8503 > URL: https://issues.apache.org/jira/browse/MESOS-8503 > Project: Mesos > Issue Type: Task >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > Attachments: Screen Shot 2018-01-29 à 10.38.05.png > > > The /roles UI endpoint displays all the roles of each framework in a table: > !Screen Shot 2018-01-29 à 10.38.05.png! > This is not readable if a framework has many roles. We thus need to provide a > solution to only display a few roles per framework and show more when a user > wants to see all of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8503) Improve UI when displaying frameworks with many roles.
Armand Grillet created MESOS-8503: - Summary: Improve UI when displaying frameworks with many roles. Key: MESOS-8503 URL: https://issues.apache.org/jira/browse/MESOS-8503 Project: Mesos Issue Type: Task Reporter: Armand Grillet Attachments: Screen Shot 2018-01-29 à 10.38.05.png The /roles UI endpoint displays all the roles of each framework in a table: !Screen Shot 2018-01-29 à 10.38.05.png! This is not readable if a framework has many roles. We thus need to provide a solution to only display a few roles per framework and show more when a user wants to see all of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-8495) Use folder structure in Roles tab
Armand Grillet created MESOS-8495:
-
Summary: Use folder structure in Roles tab
Key: MESOS-8495
URL: https://issues.apache.org/jira/browse/MESOS-8495
Project: Mesos
Issue Type: Task
Components: webui
Reporter: Armand Grillet
Assignee: Armand Grillet
Attachments: Screen Shot 2018-01-26 à 13.21.06.png
Current table structure:
!Screen Shot 2018-01-26 à 13.21.06.png!
Instead, we should display by default:
* slave_public
* slave_public/dcos-edgelb_pools_edgelb-persistent-pool-role
* slave_public/kubernetes-role
Even better, we should have a way to collapse all the {{slave_public/}} roles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MESOS-8454) Add a download link for master and agent logs in WebUI
[ https://issues.apache.org/jira/browse/MESOS-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333246#comment-16333246 ] Armand Grillet edited comment on MESOS-8454 at 1/25/18 11:48 AM: - [https://reviews.apache.org/r/65246/] was (Author: armandgrillet): [https://reviews.apache.org/r/65245/] [https://reviews.apache.org/r/65246/] > Add a download link for master and agent logs in WebUI > -- > > Key: MESOS-8454 > URL: https://issues.apache.org/jira/browse/MESOS-8454 > Project: Mesos > Issue Type: Improvement > Components: webui >Reporter: Vinod Kone >Assignee: Armand Grillet >Priority: Major > > Just like task sandboxes, it would be great for us to provide a download link > for mesos and agent logs in the WebUI. Right now the the log link opens up > the pailer, which is not really convenient to do `grep` and such while > debugging. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-8486) Webui should display role limits.
[ https://issues.apache.org/jira/browse/MESOS-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet reassigned MESOS-8486: - Assignee: Armand Grillet > Webui should display role limits. > - > > Key: MESOS-8486 > URL: https://issues.apache.org/jira/browse/MESOS-8486 > Project: Mesos > Issue Type: Task > Components: webui >Reporter: Benjamin Mahler >Assignee: Armand Grillet >Priority: Major > > With the addition of quota limits (see MESOS-8068), the UI should be updated > to display the per role limit information. Specifically, the 'Roles' tab > needs to be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-6551) Add attach/exec commands to the Mesos CLI
[
https://issues.apache.org/jira/browse/MESOS-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-6551:
-
Assignee: Armand Grillet (was: Kevin Klues)
> Add attach/exec commands to the Mesos CLI
> -
>
> Key: MESOS-6551
> URL: https://issues.apache.org/jira/browse/MESOS-6551
> Project: Mesos
> Issue Type: Task
> Components: cli
>Reporter: Kevin Klues
>Assignee: Armand Grillet
>Priority: Critical
> Labels: debugging, mesosphere
>
> After all of this support has landed, we need to update the Mesos CLI to
> implement {{attach}} and {{exec}} functionality as outlined in the Design Doc
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MESOS-8240) Add an option to build the new CLI and run unit tests.
[ https://issues.apache.org/jira/browse/MESOS-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armand Grillet updated MESOS-8240: -- Sprint: Mesosphere Sprint 70, Mesosphere Sprint 73 (was: Mesosphere Sprint 70, Mesosphere Sprint 72) > Add an option to build the new CLI and run unit tests. > -- > > Key: MESOS-8240 > URL: https://issues.apache.org/jira/browse/MESOS-8240 > Project: Mesos > Issue Type: Improvement >Reporter: Armand Grillet >Assignee: Armand Grillet >Priority: Major > > An update of the discarded https://reviews.apache.org/r/52543/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326155#comment-16326155
]
Armand Grillet commented on MESOS-8414:
---
[~kaysoky] could you please take a look as you have worked on
[https://reviews.apache.org/r/43963/] ?
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
>Assignee: Armand Grillet
>Priority: Major
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-inspect.json, docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code:java}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code:java}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
[https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384]
appears to never be reached as {{ipAddressValue->value}} is an empty string.
What happens according to {{docker logs}}:
{code:java}
The system has no more ptys. Ask your system administrator to create more.
while executing
"spawn -noecho echo out849cd741-4ba7-429c-979f-da5cb0b16e0c"
("eval" body line 1)
invoked from within
"eval [list spawn -noecho] $argv"
invoked from within
"if {[string compare [lindex $argv 0] "-p"] == 0} {
# pipeline
set stty_init
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code:java}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
[https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384]
appears to never be reached as {{ipAddressValue->value}} is an empty string.
What happens according to {{docker logs}}:
{code:java}
The system has no more ptys. Ask your system administrator to create more.
while executing
"spawn -noecho echo out849cd741-4ba7-429c-979f-da5cb0b16e0c"
("eval" body line 1)
invoked from within
"eval [list spawn -noecho] $argv"
invoked from within
"if {[string compare [lindex $argv 0] "-p"] == 0} {
# pipeline
set stty_init
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384
appears to never be reached as {{ipAddressValue->value}} is an empty string.
What happens according to {{docker logs}}:
{code}
The system has no more ptys. Ask your system administrator to create more.
while executing
"spawn -noecho echo out849cd741-4ba7-429c-979f-da5cb0b16e0c"
("eval" body line 1)
invoked from within
"eval [list spawn -noecho] $argv"
invoked from within
"if {[string compare [lindex $argv 0] "-p"] == 0} {
# pipeline
set stty_init "-echo"
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384
appears to never be reached as {{ipAddressValue->value}} is an empty string.
What happens according to {{docker logs}}:
{code}
The system has no more ptys. Ask your system administrator to create more.
while executing
"spawn -noecho echo out849cd741-4ba7-429c-979f-da5cb0b16e0c"
("eval" body line 1)
invoked from within
"eval [list spawn -noecho] $argv"
invoked from within
"if {[string compare [lindex $argv 0] "-p"] == 0} {
# pipeline
set stty_init "-echo"
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Shepherd: Alexander Rukletsov
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
>Assignee: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-inspect.json, docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Sprint: Mesosphere Sprint 72
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
>Assignee: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-inspect.json, docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for
[jira] [Assigned] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet reassigned MESOS-8414:
-
Assignee: Armand Grillet
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
>Assignee: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-inspect.json, docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00)
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384
appears to never be reached as {{ipAddressValue->value}} is an empty string.
was:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Attachment: docker-inspect.json
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-inspect.json, docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
>
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
After further testing,
https://github.com/apache/mesos/blob/51a3bd95bd2d740a39b55634251abeadb561e5c8/src/docker/docker.cpp#L384
appears to never be reached.
was:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Attachment: docker-logs.txt
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt,
> docker-logs.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
>
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Attachment: centos6-vlog2.txt
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
> Attachments:
> centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt, centos6-vlog2.txt
>
>
> You can find the verbose logs attached.
> The most interesting part:
> {code}
> I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
> I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
> 12130ns
> I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
> 'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
> I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding
> task status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
> I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
> I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
> successfully handled status update TASK_FAILED (Status UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for
> status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> executor(1)@172.16.10.110:38499
> I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state:
> TASK_FAILED, status update state: TASK_FAILED)
> I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
> (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
> I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took
> 30948ns
> I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
> TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
> framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
> master@172.16.10.110:37252
> I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
> 7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
> scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
> I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
> cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
> ports(allocated: *):[31000-32000] of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
> f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
> (ip-172-16-10-110.ec2.internal)
> I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
> status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
> for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
> status update stream for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
> successfully handled status update acknowledgement (UUID:
> 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
> f09c89e1-aa62-4662-bda8-15a2c87f412e-
> I0108
[jira] [Updated] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armand Grillet updated MESOS-8414:
--
Description:
You can find the verbose logs attached.
The most interesting part:
{code}
I0108 16:35:45.887037 17805 sched.cpp:897] Received 1 offers
I0108 16:35:45.887070 17805 sched.cpp:921] Scheduler::resourceOffers took
12130ns
I0108 16:35:45.985957 17808 docker.cpp:349] Unable to detect IP Address at
'NetworkSettings.Networks.host.IPAddress', attempting deprecated field
I0108 16:35:45.986428 17809 task_status_update_manager.cpp:328] Received task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986552 17809 task_status_update_manager.cpp:383] Forwarding task
status update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00)
for task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to the agent
I0108 16:35:45.986654 17809 slave.cpp:5209] Forwarding the update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- to master@172.16.10.110:37252
I0108 16:35:45.986795 17809 slave.cpp:5102] Task status update manager
successfully handled status update TASK_FAILED (Status UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986829 17809 slave.cpp:5118] Sending acknowledgement for status
update TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task
1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
executor(1)@172.16.10.110:38499
I0108 16:35:45.986901 17805 master.cpp:7890] Status update TASK_FAILED (Status
UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.986928 17805 master.cpp:7946] Forwarding status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.986984 17805 master.cpp:10193] Updating the state of task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- (latest state: TASK_FAILED,
status update state: TASK_FAILED)
I0108 16:35:45.987047 17805 sched.cpp:990] Received status update TASK_FAILED
(Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- from slave(1)@172.16.10.110:37252
I0108 16:35:45.987103 17805 sched.cpp:1029] Scheduler::statusUpdate took 30948ns
I0108 16:35:45.987112 17805 sched.cpp:1048] Sending ACK for status update
TASK_FAILED (Status UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of
framework f09c89e1-aa62-4662-bda8-15a2c87f412e- to
master@172.16.10.110:37252
I0108 16:35:45.987221 17805 master.cpp:5826] Processing ACKNOWLEDGE call
7f544700-215b-4d27-ab43-b48e19592d00 for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- (default) at
scheduler-4ad5073e-c1db-4c34-9c43-e656c280a724@172.16.10.110:37252 on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0
I0108 16:35:45.987267 17805 master.cpp:10299] Removing task 1 with resources
cpus(allocated: *):2; mem(allocated: *):1024; disk(allocated: *):1024;
ports(allocated: *):[31000-32000] of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e- on agent
f09c89e1-aa62-4662-bda8-15a2c87f412e-S0 at slave(1)@172.16.10.110:37252
(ip-172-16-10-110.ec2.internal)
I0108 16:35:45.987473 17807 task_status_update_manager.cpp:401] Received task
status update acknowledgement (UUID: 7f544700-215b-4d27-ab43-b48e19592d00) for
task 1 of framework f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987561 17807 task_status_update_manager.cpp:538] Cleaning up
status update stream for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987814 17807 slave.cpp:3974] Task status update manager
successfully handled status update acknowledgement (UUID:
7f544700-215b-4d27-ab43-b48e19592d00) for task 1 of framework
f09c89e1-aa62-4662-bda8-15a2c87f412e-
I0108 16:35:45.987849 17807 slave.cpp:8935] Completing task 1
{code}
was:
You can find the verbose logs attached.
The interesting part:
> DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
> --
>
> Key: MESOS-8414
> URL: https://issues.apache.org/jira/browse/MESOS-8414
> Project: Mesos
> Issue Type: Bug
> Components: test
> Environment: CentOS 6, Docker version 1.7.1, build 786b29d
>Reporter: Armand Grillet
> Attachments: centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt
>
>
> You can find the verbose logs attached.
>
[jira] [Created] (MESOS-8414) DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6
Armand Grillet created MESOS-8414: - Summary: DockerContainerizerTest.ROOT_DOCKER_Logs fails on CentOS 6 Key: MESOS-8414 URL: https://issues.apache.org/jira/browse/MESOS-8414 Project: Mesos Issue Type: Bug Components: test Reporter: Armand Grillet Attachments: centos6-ssl-DockerContainerizerTest.ROOT_DOCKER_Logs.txt You can find the verbose logs attached. The interesting part: -- This message was sent by Atlassian JIRA (v6.4.14#64029)
