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

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.2.2
• Component/s: ambari-server
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 15/Mar/16 03:33
• Updated: 15/Mar/16 19:12
• Resolved: 15/Mar/16 14:33

Description

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:

/etc/foo/conf (physical conf files placed here)
/usr/hdp/<version>/foo/conf -> /etc/foo/conf

Ambari then uses conf-select to change this:

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

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.

Issue Links

• links to: Reviewboard