[AURORA-330] aurora update should fail gracefully if job is not a service

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.8.0
• Component/s: Client
• Sprint: Twitter Aurora Q1'15 Sprint 1, Twitter Aurora Q1'15 Sprint 2
• Story Points: 2
• Assignee: Bill Farner
• Reporter: Bhuvaneswaran A
• Created: 18/Apr/14 21:43
• Updated: 04/May/15 14:28
• Resolved: 04/Feb/15 01:20

Description

14:31 < bhuvan> a quick note on aurora. when we update a job and if the job is finished before update command, the update command fail. is it a known issue?
14:32 < wickman> i think updates require that the job is a Service(), which means there is no such thing as "finished"
14:32 < wickman> since on completion they will just be restarted
14:34 ! dlester dlester@apache/committer/dlester has joined #aurora
14:34 < bhuvan> does it mean we can't update a job that is running with service=False?
14:35 < wickman> i believe so (somebody else correct me if i'm wrong)
14:35 < wickman> i think the reason it's that way is because kill/create has the same semantics for something with service=False
14:40 < mkhutornenko> bhuvan: thanks for brining this up. I think the updater should do a pre-check and bail out gracefully if the job is not a service
14:40 < bhuvan> mkhutornenko: ok. i'll file a bug.
14:40 < mkhutornenko> bhuvan: thanks, I was just typing to suggest it

Issue Links

• is duplicated by: AURORA-1015 Paused update survives past job lifetime
• is related to: AURORA-964 Scheduler updater successfully updates a non-existent job