Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Sat, 8 Nov 2014 00:57:33 +0000 (UTC)
From: "Maxim Khutornenko (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12753870.1415407774000.450999.1415408253791@Atlassian.JIRA>
In-Reply-To: <JIRA.12753870.1415407774000@Atlassian.JIRA>
References: <JIRA.12753870.1415407774000@Atlassian.JIRA>
 <JIRA.12753870.1415407774013@arcas>
Subject: [jira] [Commented] (AURORA-922) Confusing message when stuck update
 needs to be canceled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Maxim Khutornenko commented on AURORA-922:
------------------------------------------

{quote}
We should really add the ability to list locks and remove them instead of calling it cancel-update.
{quote}
This will not be a pressing issue once we move to server updates. Also, there is a /locks endpoint in the UI to self-serve when needed.

> Confusing message when stuck update needs to be canceled
> --------------------------------------------------------
>
>                 Key: AURORA-922
>                 URL: https://issues.apache.org/jira/browse/AURORA-922
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Usability
>            Reporter: Joshua Cohen
>
> If you try to act on a job that has an aborted update in flight, you get a message along the lines of:
> {noformat}
> Unable to perform operation for: cluster/some/job/key. Use override/cancel option.
> {noformat}
> The "use override/cancel option" refers to running {{aurora job cancel-update ...}}, but that's not clear from the message.


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