Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C4385200C00 for ; Wed, 18 Jan 2017 19:45:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C30DF160B43; Wed, 18 Jan 2017 18:45:41 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1A147160B22 for ; Wed, 18 Jan 2017 19:45:40 +0100 (CET) Received: (qmail 68686 invoked by uid 500); 18 Jan 2017 18:45:40 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 68676 invoked by uid 99); 18 Jan 2017 18:45:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2017 18:45:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DE4C8C0333 for ; Wed, 18 Jan 2017 18:45:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id iEL_h9apFMuX for ; Wed, 18 Jan 2017 18:45:36 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2E3695F576 for ; Wed, 18 Jan 2017 18:45:31 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9B222E59CB for ; Wed, 18 Jan 2017 18:45:27 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 811AE25286 for ; Wed, 18 Jan 2017 18:45:26 +0000 (UTC) Date: Wed, 18 Jan 2017 18:45:26 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-19585) Client config tags may not be saved by agent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 18 Jan 2017 18:45:42 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828537#comment-15828537 ] Hudson commented on AMBARI-19585: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6481 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6481/]) AMBARI-19585. Client config tags may not be saved by agent (Attila (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=753a5b0362c53b1d8677ff5cf0806ac1058baf4b]) * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/Controller.py * (edit) ambari-agent/src/test/python/ambari_agent/TestController.py > Client config tags may not be saved by agent > -------------------------------------------- > > Key: AMBARI-19585 > URL: https://issues.apache.org/jira/browse/AMBARI-19585 > Project: Ambari > Issue Type: Bug > Components: ambari-agent > Affects Versions: 2.5.0 > Reporter: Doroszlai, Attila > Assignee: Doroszlai, Attila > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19585.patch > > > Ambari agent does not save the config tags (eg. "V1") during component installation if it cannot determine that the component is a client. For this decision it requests the list of services/components right after it receives the first status command, which might happen after some client components are already installed. If the initial tags are missing, no subsequent config changes trigger updates on the affected host (except forced update via "Service Actions > Refresh configs"). -- This message was sent by Atlassian JIRA (v6.3.4#6332)