PI95398: BIG SQL INSTALL OR UPGRADE FINALIZE PHASE FAILS WITH "SSH: COULD NOT RESOLVE HOSTNAME ... NAME OR SERVICE NOT KNOWN"

APAR status

• Closed as fixed if next.

Error description

• Big SQL install or upgrade Finalize phase fails with "ssh:
  Could not resolve hostname
  /etc/ambari-agent/conf/hostname.sh: Name or service not known"
  Upgrading or installing a patch on a cluster with custom host
  names may result in the Finalize phase failing.  The problem
  may occur if Ambari is set up to use custom or private host
  names, which requires a new property 'hostname_script' be added
  to the ambari-agent.ini file.
  The Finalize phase of the upgrade script may fail with the
  following error messages:
  Finalize phase failed with the following error
  [2017-12-15 03:15:01,331]    INFO: Big SQL service model
  created successfully in Ambari
  [2017-12-15 03:15:01,331]    INFO: Registering component
  BIGSQL_HEAD of service BIGSQL via REST
  [2017-12-15 03:15:01,404]    INFO: - Request in progress:
  0.00% with   0 seconds elapsed
  [2017-12-15 03:15:16,434]   ERROR: Register BIGSQL_HEAD via
  REST failed with status "FAILED". Please try again manually.
  Last few lines from upgrade.log file
  [ambari@abc-m-1 ~]$ tail -f /var/ibm/bigsql/logs/upgrade.log
  [2017-12-15 03:15:01,319]   DEBUG: Ambari REST: POST
  http://abc-m-1.fyre.ibm.com:8081/api/v1/clusters/abccp72/hosts/a
  bc-m-5-priv.fyre.ibm.com/host_components/BIGSQL_WORKER
  [2017-12-15 03:15:01,330]   DEBUG: BIGSQL service component
  BIGSQL_WORKER registered with host abc-m-5-priv.fyre.ibm.com in
  Ambari successfully
  [2017-12-15 03:15:01,331]    INFO: Big SQL service model
  created successfully in Ambari
  [2017-12-15 03:15:01,331]    INFO: Registering component
  BIGSQL_HEAD of service BIGSQL via REST
  [2017-12-15 03:15:01,331]   DEBUG: Ambari REST: PUT
  http://abc-m-1.fyre.ibm.com:8081/api/v1/clusters/abccp72/service
  s/BIGSQL/components/BIGSQL_HEAD
  [2017-12-15 03:15:01,331]   DEBUG: Payload is {'RequestInfo':
  {'context': u'Register BIGSQL_HEAD via REST'}, 'Body':
  {'ServiceComponentInfo': {'state': 'INSTALLED'}}}
  [2017-12-15 03:15:01,391]   DEBUG: Ambari REST: GET
  http://abc-m-1.fyre.ibm.com:8081/api/v1/clusters/abccp72/request
  s/82
  [2017-12-15 03:15:01,404]    INFO: - Request in progress:
  0.00% with   0 seconds elapsed
  [2017-12-15 03:15:16,418]   DEBUG: Ambari REST: GET
  http://abc-m-1.fyre.ibm.com:8081/api/v1/clusters/abccp72/request
  s/82
  [2017-12-15 03:15:16,434]   ERROR: Register BIGSQL_HEAD via
  REST failed with status "FAILED". Please try again manually.
  From the Ambari user interface, the error seen is:
  ssh: Could not resolve hostname
  /etc/ambari-agent/conf/hostname.sh: Name or service not known
  ERROR: Failed to deploy custom action script. RC = 65280
  Verify the user running Ambari has passwordless SSH to the
  Ambari server host and retry.
  

Local fix

Problem summary

• See problem description
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels