Known Issues
Ambari 2.6 has the following known issues, scheduled for resolution in a future release. Also, refer to the Ambari Troubleshooting Guide for additional information.
Table 1.3. Ambari 2.6 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-22469 | BUG- 91993 | Ambari Sever 2.5.x set up as an Ambari Views Server (standalone server with a second Ambari Server registered as a remote server) fails when upgraded to version 2.6.0. ERROR: Error executing schema upgrade, please check the server logs. ERROR: Error output from schema upgrade command: ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories. at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203) at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418) Caused by: org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories. at org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510) at org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194) at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923) at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200) ... 1 more ERROR: Ambari server upgrade failed. Please look at /var/log/ambari-server/ambari-server.log, for more details. ERROR: Exiting with exit code 11. REASON: Schema upgrade failed. | No known workaround. Please contact Hortonworks Customer Support for assistance. |
AMBARI-22323 | BUG-90852 | If IOP Migration documentation is not followed closely, the "Remove IOP Select" button may not be available in the Ambari UI. | If that has happened to you, you must run the following command on all hosts in the cluster: rpm -e --nodeps iop-select
|