ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <>
Subject [jira] [Commented] (AMBARI-1774) Ambari does not push the config updates to the client/gateway node
Date Wed, 03 Apr 2013 17:31:25 GMT


Sumit Mohanty commented on AMBARI-1774:

* Let's not take dependency on the logic to identify smoke-test candidates for this feature.
There are two reasons for selecting candidates for smoke test and the second (multiple master
component start) does not apply to this JIRA. Also reasons to run smoke test may evolve in

> Ambari does not push the config updates to the client/gateway node
> ------------------------------------------------------------------
>                 Key: AMBARI-1774
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>         Attachments: AMBARI-1774.patch
> What happens is this, lets say you pick a
> host as a gateway which has no service daemons running.
> If you make the config changes, they can only be deployed to daemon
> nodes currently and cant be deployed to client nodes as of now. This
> is a bug in Ambari since you will never be able to update the client
> configs on a gateway node since the server will never push it to a
> client node (since no start/stop is happening on that node).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message