aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-784) Client reports "update has started" for no-op update
Date Thu, 02 Oct 2014 16:24:35 GMT

    [ https://issues.apache.org/jira/browse/AURORA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156711#comment-14156711
] 

Bill Farner commented on AURORA-784:
------------------------------------

[~maximk] what are your thoughts on this?  It relates to https://reviews.apache.org/r/26158/,
where you preferred a no-op returned {{OK}}, but this appears to have an impedance mismatch
with the client.  Which should change?

> Client reports "update has started" for no-op update
> ----------------------------------------------------
>
>                 Key: AURORA-784
>                 URL: https://issues.apache.org/jira/browse/AURORA-784
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client, Usability
>            Reporter: Bill Farner
>
> When initiating a scheduler-driven update that is actually a no-op, the client will print

> {noformat}
> Scheduler-driven update of job devcluster/www-data/devel/hello_world has started.
> {noformat}
> In this case, the scheduler is returning a message indicating the no-op:
> {noformat}
> Job is unchanged by proposed update.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message