5.5. Known Issues for Oozie

BUG-7933: Oozie failed at smoke test in secured cluster
Problem: Oozie fails smoke tests in secured cluster.
Workaround:
1. Download the following files attached to, https://issues.apache.org/jira/browse/AMBARI-2879:
  - check_oozie_status.sh
  - oozieSmoke.sh
2. Replace /var/lib/ambari-agent/puppet/modules/hdp-nagios/files/check_oozie_status.sh with the downloaded file.
3. On the Nagios Server host machine, restart Nagios using the following command:
```
service nagios start
```
4. Replace /var/lib/ambari-agent/puppet/modules/hdp-oozie/files/oozieSmoke.sh with the downloaded file all the hosts in your cluster.
5. Restart Oozie on the Oozie Server host machine using the following command:
```
 sudo su -l $OOZIE_USER -c "cd $OOZIE_LOG_DIR/log; /usr/lib/oozie/bin/oozie-start.sh" 
```
  where:
  - $OOZIE_USER is the Oozie Service user. For example, oozie
  - $OOZIE_LOG_DIR is the directory where Oozie log files are stored (for example: /var/log/oozie).
BUG-10265: TestBundleJobsFilter test fails on RHEL 6.3, Oracle 6.3 and SUSE clusters with Postgres
Problem: TestBundleJobsFilter test fails on RHEL v6.3, Oracle v6.3, and SUSE clusters with PostgreSQL.
This issue is caused due to the strict typing of PostgreSQL which restricts the auto casting of string integer to an integer. The issue is reported when string representation of integer values is substituted into a query for PostgreSQL on the JPA layer.