Return-Path: <issues-return-13787-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
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 6A205200B32
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed,  8 Jun 2016 12:11:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 68CD9160A29; Wed,  8 Jun 2016 10:11:22 +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 E10BF160A2E
	for <archive-asf-public@cust-asf.ponee.io>; Wed,  8 Jun 2016 12:11:21 +0200 (CEST)
Received: (qmail 88088 invoked by uid 500); 8 Jun 2016 10:11:21 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 88059 invoked by uid 99); 8 Jun 2016 10:11:21 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2016 10:11:21 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id EF8812C1F5D
	for <issues@ambari.apache.org>; Wed,  8 Jun 2016 10:11:20 +0000 (UTC)
Date: Wed, 8 Jun 2016 10:11:20 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12976807.1465380616000.25603.1465380680979@Atlassian.JIRA>
In-Reply-To: <JIRA.12976807.1465380616000@Atlassian.JIRA>
References: <JIRA.12976807.1465380616000@Atlassian.JIRA> <JIRA.12976807.1465380616468@arcas>
Subject: [jira] [Updated] (AMBARI-17114) DevDeploy: Ambari server is not
 started because of invalid config
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Wed, 08 Jun 2016 10:11:22 -0000


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

Dmitry Lysnichenko updated AMBARI-17114:
----------------------------------------
    Affects Version/s: 2.4.0

> DevDeploy: Ambari server is not started because of invalid config
> -----------------------------------------------------------------
>
>                 Key: AMBARI-17114
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17114
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17114.patch
>
>
> ambari-server/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml was edited in 4452d0b4e5f028aef00dfdc28d731e7b1d94961f, and introduced invalid structure:
> {noformat}
> ...
> </services>
> </services>
> </upgrade-config-changes>
> {noformat}



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