Return-Path: 
 <issues-return-1001-apmail-ambari-issues-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org
Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3CEB819062
	for <apmail-ambari-issues-archive@minotaur.apache.org>;
 Tue, 15 Mar 2016 14:34:34 +0000 (UTC)
Received: (qmail 61620 invoked by uid 500); 15 Mar 2016 14:34:34 -0000
Delivered-To: apmail-ambari-issues-archive@ambari.apache.org
Received: (qmail 61572 invoked by uid 500); 15 Mar 2016 14:34:34 -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 61549 invoked by uid 99); 15 Mar 2016 14:34:34 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2016 14:34:34 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id F3BF62C1F5D
	for <issues@ambari.apache.org>; Tue, 15 Mar 2016 14:34:33 +0000 (UTC)
Date: Tue, 15 Mar 2016 14:34:33 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12950166.1458012837000.22741.1458052473995@Atlassian.JIRA>
In-Reply-To: <JIRA.12950166.1458012837000@Atlassian.JIRA>
References: <JIRA.12950166.1458012837000@Atlassian.JIRA>
 <JIRA.12950166.1458012837209@arcas>
Subject: [jira] [Updated] (AMBARI-15419) After EU Some Services Fail To
 Start Because of Missing JKS Files
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-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-15419:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> After EU Some Services Fail To Start Because of Missing JKS Files
> -----------------------------------------------------------------
>
>                 Key: AMBARI-15419
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15419
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15419.patch
>
>
> During an upgrade, configuration files from the old stack are not copied to the new configuration folders created using {{conf-select}}. This means that files which Ambari does not track, are never included in the new configuration directories.
> This is what happens on a clean install:
> {noformat}
> /etc/foo/conf (physical conf files placed here)
> /usr/hdp/<version>/foo/conf -> /etc/foo/conf
> {noformat}
> Ambari then uses {{conf-select}} to change this:
> {noformat}
> /etc/foo/conf.backup (contents of original /etc/foo/conf folder)
> /etc/foo/conf -> /usr/hdp/<version>/foo/conf
> /usr/hdp/<version>/foo/conf -> /etc/foo/<version>/0
> /etc/foo/<version>/0   (physical conf files placed here)
> {noformat}
> But in this scenario, we make sure to seed {{/etc/foo/<version>/0}} with the files which were in {{/etc/foo/conf}} originally, including files which we don't track. This is to prevent files, like JKS keystores, from being lost.
> *Now the upgrade scenario:*
> ----
>  If you already have {{/usr/hdp/2.3.0.0}} installed, that means that you have {{/etc/foo/conf}} and all associated files already on the disk. When you distribute HDP 2.4, {{/usr/hdp/2.4.0.0}} is created. However, it cannot overwrite any existing configurations since you haven't upgraded yet. So, it basically does nothing with the configurations. We invoke {{conf-select}} to create {{/etc/foo/2.4.0.0/0}}, but it is never seeded with any values from {{/etc/foo/2.3.0.0/0}}.



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