[jira] [Commented] (AMBARI-15419) After EU Some Services Fail To Start Because of Missing JKS Files

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195653#comment-15195653 ] 

Hudson commented on AMBARI-15419:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.2 #513 (See [https://builds.apache.org/job/Ambari-branch-2.2/513/])
AMBARI-15419 - After EU Some Services Fail To Start Because of Missing (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d00d7bcefb8ed09b8b74316f8e06a2f2805a0266])
* ambari-server/src/test/python/stacks/2.0.6/hooks/after-INSTALL/test_after_install.py
* ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
* ambari-server/src/test/python/stacks/2.2/common/test_conf_select.py
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py


> 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)