Jonathan Hurley created AMBARI-15419:
----------------------------------------
Summary: 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
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, include files which we don't
track.
Now the upgrade scnenario. If you already have {{/usr/hdp/2.3.0.0}} install,
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
