[
https://issues.apache.org/jira/browse/AURORA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambert reassigned AURORA-330:
------------------------------------
Assignee: Bill Farner
> aurora update should fail gracefully if job is not a service
> ------------------------------------------------------------
>
> Key: AURORA-330
> URL: https://issues.apache.org/jira/browse/AURORA-330
> Project: Aurora
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.5.0
> Reporter: Bhuvan Arumugam
> Assignee: Bill Farner
> Priority: Critical
> Labels: twitter
>
> 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 :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
