[
https://issues.apache.org/jira/browse/AURORA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Cohen resolved AURORA-1737.
----------------------------------
Resolution: Cannot Reproduce
I can no longer reproduce this problem. Not sure what changed to fix it, but
resolving as cannot reproduce. If it comes back we can re-open.
> 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)
