[AURORA-794] Client erroneously prints "Job not found" when job exists

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Fix Version/s: 0.8.0
• Component/s: Client, Usability
• Sprint: Twitter Aurora Q4 Sprint 3
• Assignee: Zameer Manji
• Reporter: Bill Farner
• Created: 03/Oct/14 17:09
• Updated: 04/May/15 14:31
• Resolved: 07/Nov/14 20:30

Description

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.

$ 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

Issue Links

• blocks: AURORA-872 0.7.0 Release Candidate
• is related to: AURORA-793 Client prints redundant messages