[jira] [Resolved] (STORM-1655) Flux doesn't set return code to non-zero when there's any exception while deploying topology to remote cluster

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim resolved STORM-1655.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Merged into master and 1.x-branch.

> Flux doesn't set return code to non-zero when there's any exception while deploying topology to remote cluster
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-1655
>                 URL: https://issues.apache.org/jira/browse/STORM-1655
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: Flux
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> Flux.runCli() swallows any Exceptions when deploying topology remotely, while StormSubmitter.submitTopology() can throw exceptions.
> (AlreadyAliveException, InvalidTopologyException, AuthorizationException, and so on)
> It just prints warning log, and return code is 0, not non-zero.
> You can easily reproduce via deploying same topology twice with Flux.



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