[
https://issues.apache.org/jira/browse/AMBARI-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309926#comment-14309926
]
Tom Beerbower commented on AMBARI-9527:
---------------------------------------
[~ncole]
I think that it will work on the upgrade item now that your change to
ActionScheduler went in. Prior to that I think that it would be stuck on
HOLDING. I think that it is more logical to do it on the Upgrade since we are
trying to abort the entire upgrade.
Sorry, didn't mean to confuse things. Just pointing out that it should work
either way.
Again, I think that aborting the Upgrade (as you suggested) is a better
approach.
> RU: FE must issue an ABORTED to an upgrade before starting a downgrade
> ----------------------------------------------------------------------
>
> Key: AMBARI-9527
> URL: https://issues.apache.org/jira/browse/AMBARI-9527
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: AMBARI-9527.patch, AMBARI-9527_2.patch
>
>
> The FE must issue an ABORTED call to a current upgrade before issuing the
> downgrade request.
> The UI must also wait for the abort to complete before starting an upgrade.
> The UI is telling me the upgrade is completely finished and the button goes
> away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)