[jira] [Commented] (AURORA-1666) Allow health check to not run as job's role `role`
[
https://issues.apache.org/jira/browse/AURORA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243845#comment-15243845
]
Dmitriy Shirchenko commented on AURORA-1666:
https://reviews.apache.org/r/46290/
> Allow health check to not run as job's role `role`
> --
>
> Key: AURORA-1666
> URL: https://issues.apache.org/jira/browse/AURORA-1666
> Project: Aurora
> Issue Type: Story
>Reporter: Dmitriy Shirchenko
>Assignee: Dmitriy Shirchenko
>
> We have an issue with new permission demotion as our containers run as the
> same user and we don't care what user they run as.
> I propose a flag to disable this demotion and allow health check to keep
> running as root if we want this. Maybe this can be done at thermos executor
> level.
> {code}
> E0415 20:32:51.799864 6 aurora_executor.py:118] Traceback (most recent call
> last):
> File "apache/aurora/executor/aurora_executor.py", line 116, in _run
> self._start_status_manager(driver, assigned_task)
> File "apache/aurora/executor/aurora_executor.py", line 161, in
> _start_status_manager
> status_checker = status_provider.from_assigned_task(assigned_task,
> self._sandbox)
> File "apache/aurora/executor/common/health_checker.py", line 248, in
> from_assigned_task
> pw_entry = pwd.getpwnam(assigned_task.task.job.role)
> KeyError: 'getpwnam(): name not found: meta-umonitor-worker'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AURORA-1468) Replace org.apache.aurora.commons.zookeeper with a Apache Curator
[ https://issues.apache.org/jira/browse/AURORA-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243803#comment-15243803 ] John Sirois commented on AURORA-1468: - 3c: Implement plumbing for Curator as the service discovery system: https://reviews.apache.org/r/46286/ > Replace org.apache.aurora.commons.zookeeper with a Apache Curator > - > > Key: AURORA-1468 > URL: https://issues.apache.org/jira/browse/AURORA-1468 > Project: Aurora > Issue Type: Task > Components: Scheduler >Reporter: Bill Farner >Assignee: John Sirois >Priority: Minor > Labels: newbie++ > > We should not continue to maintain our own ZooKeeper client and recipes. > Let's use curator instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AURORA-1667) Sort out vagrant box versioning
Joshua Cohen created AURORA-1667: Summary: Sort out vagrant box versioning Key: AURORA-1667 URL: https://issues.apache.org/jira/browse/AURORA-1667 Project: Aurora Issue Type: Task Reporter: Joshua Cohen I tried to commit the update to Mesos 0.27.2 today but ran into an issue provisioning the Vagrant environment. This turns out to be caused by me having not run `vagrant box update`. We should look into a solution that doesn't require this manual step. We should also look into pinning the box version referenced by vagrant so we can make these changes atomically in the future. Pinning the box version may also solve the need to run vagrant box update as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1666) Allow health check to not run as job's role `role`
[
https://issues.apache.org/jira/browse/AURORA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243736#comment-15243736
]
Dmitriy Shirchenko commented on AURORA-1666:
Sounds [~zmanji] is onboard with suggestion of adding a thermos_executor flag.
> Allow health check to not run as job's role `role`
> --
>
> Key: AURORA-1666
> URL: https://issues.apache.org/jira/browse/AURORA-1666
> Project: Aurora
> Issue Type: Story
>Reporter: Dmitriy Shirchenko
>Assignee: Dmitriy Shirchenko
>
> We have an issue with new permission demotion as our containers run as the
> same user and we don't care what user they run as.
> I propose a flag to disable this demotion and allow health check to keep
> running as root if we want this. Maybe this can be done at thermos executor
> level.
> {code}
> E0415 20:32:51.799864 6 aurora_executor.py:118] Traceback (most recent call
> last):
> File "apache/aurora/executor/aurora_executor.py", line 116, in _run
> self._start_status_manager(driver, assigned_task)
> File "apache/aurora/executor/aurora_executor.py", line 161, in
> _start_status_manager
> status_checker = status_provider.from_assigned_task(assigned_task,
> self._sandbox)
> File "apache/aurora/executor/common/health_checker.py", line 248, in
> from_assigned_task
> pw_entry = pwd.getpwnam(assigned_task.task.job.role)
> KeyError: 'getpwnam(): name not found: meta-umonitor-worker'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AURORA-1666) Allow health check to not run as job's role `role`
[
https://issues.apache.org/jira/browse/AURORA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Shirchenko reassigned AURORA-1666:
--
Assignee: Dmitriy Shirchenko
> Allow health check to not run as job's role `role`
> --
>
> Key: AURORA-1666
> URL: https://issues.apache.org/jira/browse/AURORA-1666
> Project: Aurora
> Issue Type: Story
>Reporter: Dmitriy Shirchenko
>Assignee: Dmitriy Shirchenko
>
> We have an issue with new permission demotion as our containers run as the
> same user and we don't care what user they run as.
> I propose a flag to disable this demotion and allow health check to keep
> running as root if we want this. Maybe this can be done at thermos executor
> level.
> {code}
> E0415 20:32:51.799864 6 aurora_executor.py:118] Traceback (most recent call
> last):
> File "apache/aurora/executor/aurora_executor.py", line 116, in _run
> self._start_status_manager(driver, assigned_task)
> File "apache/aurora/executor/aurora_executor.py", line 161, in
> _start_status_manager
> status_checker = status_provider.from_assigned_task(assigned_task,
> self._sandbox)
> File "apache/aurora/executor/common/health_checker.py", line 248, in
> from_assigned_task
> pw_entry = pwd.getpwnam(assigned_task.task.job.role)
> KeyError: 'getpwnam(): name not found: meta-umonitor-worker'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AURORA-1666) Allow health check to not run as job's role `role`
Dmitriy Shirchenko created AURORA-1666:
--
Summary: Allow health check to not run as job's role `role`
Key: AURORA-1666
URL: https://issues.apache.org/jira/browse/AURORA-1666
Project: Aurora
Issue Type: Story
Reporter: Dmitriy Shirchenko
We have an issue with new permission demotion as our containers run as the same
user and we don't care what user they run as.
I propose a flag to disable this demotion and allow health check to keep
running as root if we want this. Maybe this can be done at thermos executor
level.
{code}
E0415 20:32:51.799864 6 aurora_executor.py:118] Traceback (most recent call
last):
File "apache/aurora/executor/aurora_executor.py", line 116, in _run
self._start_status_manager(driver, assigned_task)
File "apache/aurora/executor/aurora_executor.py", line 161, in
_start_status_manager
status_checker = status_provider.from_assigned_task(assigned_task,
self._sandbox)
File "apache/aurora/executor/common/health_checker.py", line 248, in
from_assigned_task
pw_entry = pwd.getpwnam(assigned_task.task.job.role)
KeyError: 'getpwnam(): name not found: meta-umonitor-worker'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AURORA-1665) DbCronJobStore is missing @Timed annotations
Zameer Manji created AURORA-1665:
Summary: DbCronJobStore is missing @Timed annotations
Key: AURORA-1665
URL: https://issues.apache.org/jira/browse/AURORA-1665
Project: Aurora
Issue Type: Bug
Reporter: Zameer Manji
{{DBCronJobStore}} lacks @Timed annotations on its operations. Adding these
will allow for greater visibility into storage related operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AURORA-1584) Aurora 0.13.0 release candidate
[ https://issues.apache.org/jira/browse/AURORA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Farrell resolved AURORA-1584. -- Resolution: Fixed Vote passed, released 0.13.0-rc0 as Apache Aurora 0.13.0 > Aurora 0.13.0 release candidate > --- > > Key: AURORA-1584 > URL: https://issues.apache.org/jira/browse/AURORA-1584 > Project: Aurora > Issue Type: Task >Reporter: Bill Farner >Assignee: Jake Farrell > Fix For: 0.13.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1584) Aurora 0.13.0 release candidate
[ https://issues.apache.org/jira/browse/AURORA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Farrell updated AURORA-1584: - Fix Version/s: (was: 0.14.0) 0.13.0 > Aurora 0.13.0 release candidate > --- > > Key: AURORA-1584 > URL: https://issues.apache.org/jira/browse/AURORA-1584 > Project: Aurora > Issue Type: Task >Reporter: Bill Farner >Assignee: Jake Farrell > Fix For: 0.13.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1663) Wrong version of VirtualBox guest additions
[ https://issues.apache.org/jira/browse/AURORA-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242941#comment-15242941 ] Vitaly Stakhovsky commented on AURORA-1663: --- Actually, there is an issue (maybe it is a subject of another ticket). And the first thing I see is this warning that the VirtualBox guest additions are wrong. At this point I have no clue whether this is a culprit or not. From this message I gather that the guest additions are not workable. When you call this warning harmless, do you mean that everything should work without the guest additions ? If this is the case, maybe they should be removed from apache-aurora/dev-environment ? The warning then will disappear. If not, the root cause must be fixed, and the warning will also disappear. > Wrong version of VirtualBox guest additions > --- > > Key: AURORA-1663 > URL: https://issues.apache.org/jira/browse/AURORA-1663 > Project: Aurora > Issue Type: Bug > Components: Deploy > Environment: Windows, VirtualBox5 >Reporter: Vitaly Stakhovsky >Assignee: Vitaly Stakhovsky >Priority: Minor > > I follow the instructions on the 'Getting Started' page for Windows. If I use > VirtualBox 5, I am getting a warning: > The guest additions on this VM do not match the installed version of > VirtualBox! > ... > Guest Additions Version: 4.3.36 > VirtualBox Version: 5.0 > Apparently, this is because the apache-aurora/dev-environment Vagrant box is > now used instead of ubuntu/trusty64 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1584) Aurora 0.13.0 release candidate
[ https://issues.apache.org/jira/browse/AURORA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Farrell updated AURORA-1584: - Fix Version/s: (was: 0.13.0) 0.14.0 > Aurora 0.13.0 release candidate > --- > > Key: AURORA-1584 > URL: https://issues.apache.org/jira/browse/AURORA-1584 > Project: Aurora > Issue Type: Task >Reporter: Bill Farner >Assignee: Jake Farrell > Fix For: 0.14.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
