[AMBARI-18567] Cannot start Oozie if WebHDFS is disabled

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 3.0.0, 2.5.0, 2.4.2
• Component/s: ambari-server
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 11/Oct/16 08:36
• Updated: 14/Oct/16 10:16
• Resolved: 14/Oct/16 09:30

Description

If WebHDFS is disabled, Oozie cannot be started due to missing import in service script.

  File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py", line 145, in oozie_service
    hdfs_share_dir_exists = shell.call(format("{kinit_if_needed} hadoop --config {hadoop_conf_dir} dfs -ls {hdfs_share_dir} | awk 'BEGIN {{count=0;}} /share/ {{count++}} END {{if (count > 0) {{exit 0}} else {{exit 1}}}}'"),
NameError: global name 'shell' is not defined

Issue Links

• is broken by: AMBARI-11558 Ooozie start takes too long
• relates to: AMBARI-18581 Oozie start script ignores sysprep_skip_copy_oozie_share_lib_to_hdfs flag
• links to: Review request