[
https://issues.apache.org/jira/browse/AMBARI-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204062#comment-14204062
]
Hudson commented on AMBARI-8234:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #176 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/176/])
AMBARI-8234.Hosts bulk options: remove state filter on start/stop all
components.(xiwang) (xiwang:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=087f24cdd7824c1c5e51a8c9b5ddc9017b0d9a15)
* ambari-web/app/controllers/main/host.js
> Hosts bulk options: remove state filter on start/stop all components
> --------------------------------------------------------------------
>
> Key: AMBARI-8234
> URL: https://issues.apache.org/jira/browse/AMBARI-8234
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8234.patch
>
>
> Issue: Host list -> selected hosts -> start all components is refusing to
> work - says nothing to do.
> *Reason*: start all components will filter all host components with 'desired
> state=INSTALLED' which should be "actual state=INSTALLED", so sometimes the
> filtered host components are empty, but in fact there are components need to
> start.
> *Solution*: take out this HostRoles/state filtering and issue Start on all
> the host components for the selected hosts regardless of the actual state.
> The server should just ignore Start command on host components whose actual
> state is STARTED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
