[
https://issues.apache.org/jira/browse/AURORA-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zameer Manji updated AURORA-794:
--------------------------------
Sprint: Twitter Aurora Q4 Sprint 3
> Client erroneously prints "Job not found" when job exists
> ---------------------------------------------------------
>
> Key: AURORA-794
> URL: https://issues.apache.org/jira/browse/AURORA-794
> Project: Aurora
> Issue Type: Bug
> Components: Client, Usability
> Reporter: Bill Farner
> Assignee: Zameer Manji
>
> In this case, i'm trying to create a job that already exists. The 'message
> from scheduler' lines have the correct error, but the client goes on to claim
> "Job not found". I'm not sure if there is really a good string for the
> client to make up in this case, as the scheduler will have the real reason
> the request failed.
> {noformat}
> $ aurora2 job create -v devcluster/www-data/devel/hello_world
> /vagrant/hello_world.aurora
> log(info): Creating job hello_world
> log(info): Creating job hello_world
> log(info): Starting new HTTP connection (1): vagrant-ubuntu-trusty-64
> log(info): Starting new HTTP connection (1): vagrant-ubuntu-trusty-64
> log(info): Starting new HTTP connection (1): vagrant-ubuntu-trusty-64
> log(info): Starting new HTTP connection (1): vagrant-ubuntu-trusty-64
> log(info): Message from scheduler: Job already exists:
> www-data/devel/hello_world
> log(info): Message from scheduler: Job already exists:
> www-data/devel/hello_world
> job create failed because job not found
> log(info): Error executing command: Job not found
> log(info): Error executing command: Job not found
> Error executing command: Job not found
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
