Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1.0
-
None
-
None
-
HDP 2.3
Description
When provisioning an Ambari cluster via a blueprint that was taken from an existing cluster install, Ambari fails with a list index out of range error on the metrics collector.
I suspect this is due to not supplying all host_groups in the mapping json at cluster creation time but there was no validation on missing host groups to prevent this scenario so it fails late half way through the install.
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py", line 58, in <module> AmsMonitor().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 216, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py", line 29, in install self.configure(env) # for security File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py", line 32, in configure import params File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py", line 54, in <module> metric_collector_host = ams_collector_hosts[0] IndexError: list index out of range