Known Issues
Ambari 2.6.1 has the following known issues, scheduled for resolution in a future release. Also, refer to the Ambari Troubleshooting Guide for additional information.
Table 1.5. Ambari 2.6.1 Known Issues
Apache Jira |
HWX Jira |
Problem |
Solution |
---|---|---|---|
AMBARI-24536 | BUG-109839 | When SPNEGO is enabled (`ambari-server setup-kerberos`), the SSO (`ambari-server setup-sso`) redirect no longer works. | No known workaround. Do not enable both kerberos and SSO using ambari-server setup. |
AMBARI-22906 | BUG-95744 | After upgrading Ambari to 2.6.1.0, registering a new HDP version fails with the following error message: Cannot read property 'gpl.license.accepted' of undefined | Upgrade Ambari to version 2.6.1.5 before upgrading HDP to version 2.6.4. See steps below: |
ST-3620 | SmartSense scheduler doesn't initiate capture. |
After successful upgrade, all services (including SmartSense) should be up and running. | |
N/A |
BUG-94823 |
Upgrading Ambari 2.5.x to 2.6.x and AMS to 2.6.1 without changing the JDK version from 1.7 to 1.8 causes the Metrics Collector services start to fail. The Ambari Metrics Collector 2.6.1 requires JDK 8.
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py", line 207, in <module> AMSServiceCheck().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 375, in execute method(env) File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk return fn(*args, **kwargs) File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py", line 159, in service_check raise Fail("All metrics collectors are unavailable.") resource_management.core.exceptions.Fail: All metrics collectors are unavailable.
|
|
N/A | BUG-82900 | If hosts are in maintenance mode during the Enable Kerberos wizard, the kerberos client is not installed, and keytabs and principals are not created for these hosts. |
|
N/A | Bug-93305 | Oozie Spark workflows are failing with the following exception due to missing py4j and pyspark files after patch upgrade: Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SparkMain], main() threw exception, Missing py4j and/or pyspark zip files. Please add them to the lib folder or to the Spark sharelib. org.apache.oozie.action.hadoop.OozieActionConfiguratorException: Missing py4j and/or pyspark zip files. Please add them to the lib folder or to the Spark sharelib. | The workaround is to manually copy these files to HDFS. To do that follow the steps below:
|
N/A | Bug-93805 | If any hosts with master components are in maintenance mode, patch upgrade cannot proceed even if these master components are unrelated to the patch upgrade. | Please take these hosts out of maintenance mode before proceeding. |
N/A | Bug-92232 | When patching HDFS using Express Upgrade, HBase may stop responding because HDFS is shut down completely. | You may Ignore and Proceed when the HBase Service Check is run and fails. Alternatively, you may pause the upgrade, restart HBase, then resume the upgrade. |
AMBARI-22491 | BUG-91896 | When moving a Metrics Collector to a host, if a ZooKeeper server is not installed on that host, a new ZooKeeper service will be erroneously installed. | No known workaround. |