The following table lists selected issues resolved in Ambari 2.0.2:
Table 1.2. Ambari 2.0.2 Fixed Issues
Apache Jira | HWX Jira | Feature Area | Summary |
---|---|---|---|
BUG-41469 |
Ambari Web |
Oozie HA: Ambari quick link is not correct. | |
BUG-38022 |
Stack > Ranger |
Ranger usersync bind password is not hidden. | |
BUG-36869 |
Stack > Ranger |
Ranger plugin enable script in ambari tries to create amb_ranger_admin user even if it already exists | |
BUG-41379 |
Stack > Upgrade |
During HDP 2.1 to 2.2.6 upgrade dfs.journalnode.edits.dir is incorrectly changed. | |
BUG-40159 |
Ambari Web |
BE-issue with auto-update of HDP.repo with default baseurl. | |
BUG-38915 |
Performance |
Ambari Server deadlocks when adding service / adding host. | |
BUG-40114 |
Ambari Web |
Add Service Wizard resets local hdp repo to public repo. | |
BUG-40214 |
Performance |
Heartbeats are often lost during deploy. | |
BUG-41628 |
Performance |
AMS Causes Two Active ResourceManagers | |
BUG-40241 |
Alerts |
Alert Notifications : save button is disabled when creating alert notification. | |
BUG-41648 |
Security |
Access to admin level functionality must be authorized for the REST API |
The following table lists selected issues resolved in Ambari 2.0.1:
Table 1.3. Ambari 2.0.1 Fixed Issues
Apache Jira | HWX Jira | Feature Area | Summary |
---|---|---|---|
BUG-27127 |
Ambari Web |
Updated spinner | |
BUG-36943 |
Stack > General |
Stack advisor fails for larger clusters | |
BUG-36759 |
Ambari Web |
Admin View: About says Ambari 2.0.0, but it's 2.0.1 | |
BUG-36741 |
Ambari Upgrade |
Upgrade 2.0.0 > 2.0.1 on Ubuntu 12 - commands failures | |
BUG-36656 |
Rolling Upgrade |
Upgrade to 2.0.1, unable to RU (can't get past Installing...) | |
BUG-36643 |
Ambari Upgrade |
Upgrade 2.0.0->2.0.1 on Oracle database failed | |
BUG-36348 |
Alerts |
Upgrade 1.6.1 > 2.0.1: Nagios not removed | |
BUG-36340 |
Ambari Upgrade |
Cannot upgrade Ambari 2.0 > 2.0.1 on SLES 11.3 | |
BUG-36433 |
Views |
IllegalStateException: work already begun on this thread | |
BUG-36358 |
Rolling Upgrade |
RU: wrong version of tez.tar.gz uploaded to HDFS | |
BUG-36282 |
Alerts |
Alerts: do not expose subject + body for SNMP traps | |
BUG-34364 |
Metrics |
AMS config warning message is confusing | |
BUG-36173 |
Ambari Web |
Unable to register host with non-root ssh user | |
BUG-36255 |
Ambari Upgrade |
Cannot start ambari-server after Ambari-only upgrade to 2.0.1 | |
BUG-36184 |
Views |
Views: ViewContext is not injecting | |
BUG-36179 |
Performance |
Reduce time between ActionScheduler wake-ups | |
BUG-35936 |
Stack > General |
Remove <latest> element from gluster 2.1 and 2.2 stack definitions | |
BUG-36021 |
Views |
404 error on Slider view | |
BUG-34813 |
Stack > Spark |
Spark version is incorrect in the HDP 2.2 stack | |
BUG-36238 |
Ambari Upgrade |
If selinux is disabled via /etc/selinux/config, cluster deployment fails | |
BUG-35938 |
Stack > YARN |
ATS heapsize does not take effect | |
BUG-34358 |
Metrics |
AMS: navigating graph time ranges are not correct | |
BUG-35943 |
Ambari Upgrade |
Renaming of ambari-sequences.sequence_value handled inappropriately during upgrade | |
BUG-35944 |
Ambari Upgrade |
Agent upgrade loses custom hostname config | |
BUG-35244 |
Ambari Upgrade |
Ambari 1.7.0 > 2.0 upgrade fails due to failure to upgrade properties file | |
BUG-35574 |
Views |
Views: IllegalAccessError: tried to access class | |
BUG-35247 |
Rolling Upgrade |
RU: HiveServer2 restart fails, --deregister exit code 255 | |
BUG-34779 |
Manual Upgrade |
UPGRADE: Update UpgradeCatalog-*ison files for stacks HDP 2.0 to 2.2.x and HDP 2.1 to 2.2.x | |
BUG-34363 |
Ambari Upgrade |
Internal Exception: org.postgresql.util.PSQLException: ERROR: column "config_attributes" does not exist | |
BUG-35021 |
Rolling Upgrade |
RU: Oozie upgrade fails when using Oracle DB | |
BUG-34369 |
Ambari Upgrade |
Ambari upgrade from 1.7.0 to 2.0 fails to restart ZooKeeper server due to missing symlink | |
BUG-34820 |
Security |
Local root user's group is being assigned to hadoop | |
BUG-34657 |
Ambari Upgrade |
UPGRADE: DUE TO CHANGES IN AMBARI API, some response validations should be allowed with a warning message | |
BUG-34811 |
Alerts |
Ambari Agent holding socket open on 50070 prevents NameNode from starting | |
BUG-35246 |
Performance |
Ambari Server deadlock when mapping hosts | |
BUG-34386 |
Kerberos |
Ambari unable to start services use non-default kinit_path_local | |
BUG-34372 |
Manual Upgrade |
Client-only services need restart to advertise version | |
BUG-35945 |
Performance |
Some service components are missing from API response; this causes problems | |
BUG-34356 |
Stack > Hive |
When databases exist with LOCATIONs outside of hive.metastore.warehouse.dirs, HS2 fails to start | |
BUG-34812 |
Rolling Upgrade |
BE issue: installation repo version is stuck in INSTALLING after sudden server restart | |
BUG-34370 |
Alerts |
Alerts: Hive Metastore and HS2 process alerts do not work with custom smoke user | |
BUG-34365 |
Alerts |
Unable to save SNMPv1 and SNMPv2c notification | |
BUG-34367 |
Ambari Web |
Hosts List Actions list always shows one more than what is selected | |
BUG-34371 |
Ambari Web |
When host agent registration fails, Retry button is missing | |
BUG-34357 |
Kerberos |
Cannot enable Kerberos with Ambari server running non-root | |
BUG-35946 |
Stack > HBase |
Unable to delete HBase Master | |
BUG-34362 |
Stack > Hive |
HiveServer2 does not install/start when running without sudo | |
BUG-34361 |
Kerberos |
The path(s) to the Kerberos utilities (kadmin, klist, etc.) should be configurable | |
BUG-34359 |
Alerts |
Alert notifications are not received without restarting Ambari Server | |
BUG-34360 |
Stack > Storm |
.log files are not placed in the changed directory in Ambari 1.6 and 1.7 | |
BUG-32250 |
Manual Upgrade |
configs.sh doConfigFileUpdate files when multiple occurrences of the word "properties" are found | |
BUG-36875 |
Stack > YARN |
"Capacity Scheduler" section in Ambari 2.0 does not allow spaces in properties |