Sandor Magyari created AMBARI-13017: ---------------------------------------
Summary: Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint Key: AMBARI-13017 URL: https://issues.apache.org/jira/browse/AMBARI-13017 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Environment: all Reporter: Sandor Magyari Priority: Critical 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)