Issue: In HA installations of SAM, you may run into a situation where bootstrap has not been executed.

Result: When bootstrap has not been started, the UI displays the following message:

1. No component definitions found.
2. Please run ./bin/streamline bootstrap to 
initialize the component definitions.

Workaround for a secured cluster:

kinit -kt /etc/security/keytabs/streamline.service.keytab 
streamline-{cluster_name_in_lower-case}@domain

Workaround for an unsecured cluster:

cd /usr/hdf/current/streamline
./bootstrap/bootstrap.sh

Issue: When NiFi is installed on an Ambari-managed HDP cluster, NiFi information is not available in Ambari Metrics.

Workaround: There is no workaround for this issue.

Issue: The Ambari Server upgrade fails when the HDP Search (Solr) or HDF management pack is installed.

Error Message:

File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line 896, in install_mpack
    (mpack_metadata, mpack_name, mpack_version, mpack_staging_dir, mpack_archive_path) = _install_mpack(options, replay_mode)
  File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line 792, in _install_mpack
    process_service_definitions_artifact(artifact, artifact_source_dir, options)
  File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line 515, in process_service_definitions_artifact
    create_symlink(src_service_definitions_dir, dest_service_definitions_dir, file, options.force)
  File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line 235, in create_symlink
    create_symlink_using_path(src_path, dest_link, force)
  File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line 247, in create_symlink_using_path
    sudo.symlink(src_path, dest_link)
  File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", line 123, in symlink
    os.symlink(source, link_name)
OSError: [Errno 17] File exists

Workaround for HDP Search mpack: To work around this issue, enter the following commands:

rm -rf /var/lib/ambari-server/resources/common-services_05_06_17_19_49.old/SOLR
rm -rf /var/lib/ambari-server/resources/common-services/SOLR

Workaround for HDF mpack: To work around this issue, enter the following commands:

rm -rf /var/lib/ambari-server/resources/common-services/NIFI/ 
rm -rf /var/lib/ambari-server/resources/common-services_17_02_17_18_20.old/NIFI/ 
rm -rf /var/lib/ambari-server/resources/common-services_20_06_17_15_47.old/NIFI/ 

	Note
	In each case, the date-time pattern is a timestamp of the management pack file and differs in every case.

Issue: You may experience a schema error when upgrading to Ambari 2.5.1.

Error Message:

WARN [main] DBAccessorImpl:814 - Error executing query: UPDATE request AS a SET cluster_host_info = b.cluster_host_info FROM stage AS b WHERE a.request_id = b.request_id, errorCode = 0, message = ERROR: column b.cluster_host_info does not exist 
Position: 45 
20 Jun 2017 19:45:23,466 ERROR [main] SchemaUpgradeHelper:209 - Upgrade failed. 
org.postgresql.util.PSQLException: ERROR: column b.cluster_host_info does not exist 
Position: 45

Workaround: To work around this issue, re-add the column to the stage table before issuing the 'ambari-server upgrade' command.

Example for updating the Ambari Postgres database: