[AMBARI-13017] Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.3.0
• Component/s: ambari-server

Environment

all

• Assignee: Magyari Sandor Szilard
• Reporter: Magyari Sandor Szilard
• Created: 04/Sep/15 16:25
• Updated: 14/Apr/16 12:18
• Resolved: 24/Sep/15 20:22

Description

PROBLEM: Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint.
For instance, on the sandbox which uses blueprint to install falcon(attached to this bug) outputs the following for
grep -i ext /etc/oozie/conf/oozie-site.xml
<name>oozie.services.ext</name>
on a cluster that install falcon via add service via the webui, running grep -i ext /etc/oozie/conf/oozie-site.xml produces
<name>oozie.service.ELService.ext.functions.coord-action-create</name>
<name>oozie.service.ELService.ext.functions.coord-sla-create</name>
<name>oozie.service.ELService.ext.functions.coord-sla-submit</name>
Hence, the blueprint install will be missing needed properties.
IMPACT: falcon will not operate as expected
STEPS TO REPRODUCE:
1. Install cluster via ambari blueprint attached.
2. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml
3. Install cluster via ambari webui UI
4. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml you should proper complete set of configs.

Issue Links

• is duplicated by: AMBARI-15882 Oozie-falcon integration properties to be considered in case of blueprint deployments