Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE0A3F771 for ; Wed, 3 Apr 2013 21:43:15 +0000 (UTC) Received: (qmail 34409 invoked by uid 500); 3 Apr 2013 21:43:15 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 34376 invoked by uid 500); 3 Apr 2013 21:43:15 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 34319 invoked by uid 99); 3 Apr 2013 21:43:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 21:43:15 +0000 Date: Wed, 3 Apr 2013 21:43:15 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-1774) Ambari does not push the config updates to the client/gateway node MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-1774: ------------------------------------ Attachment: AMBARI-1774-3.patch Incorporated comments. > Ambari does not push the config updates to the client/gateway node > ------------------------------------------------------------------ > > Key: AMBARI-1774 > URL: https://issues.apache.org/jira/browse/AMBARI-1774 > 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-2.patch, AMBARI-1774-3.patch, 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: http://www.atlassian.com/software/jira