You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Jing Chen (JIRA)" <ji...@apache.org> on 2016/10/09 08:52:21 UTC

[jira] [Assigned] (AURORA-1737) Descheduling a cron job checks role access before job key existence

     [ https://issues.apache.org/jira/browse/AURORA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Chen reassigned AURORA-1737:
---------------------------------

    Assignee: Jing Chen

> Descheduling a cron job checks role access before job key existence
> -------------------------------------------------------------------
>
>                 Key: AURORA-1737
>                 URL: https://issues.apache.org/jira/browse/AURORA-1737
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Joshua Cohen
>            Assignee: Jing Chen
>            Priority: Minor
>
> Trying to deschedule a cron job for a non-existent role returns a permission error rather than a no-such-job error. This leads to confusion for users in the event of a typo in the role.
> Given that jobs are world-readable, we should check for a valid job key before applying permissions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)