PI42819: Collective join or replicate with --useHostCredentials option co mpletes even if host credentials are missing.

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Use of collective join or replicate with
  --useHostCredentials, without  performing collective
  registerHost first can result in a configuration where
  remote servers cannot be stopped or started.  If using the
  adminCenter, an incorrect error message of server (name)
  does not exist is produced.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile Collectives          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Collective join or replicate with --    *
  *                      useHostCredentials option completes     *
  *                      even if host credentials are missing.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Use of collective join or replicate with --useHostCredentials,
  without  performing collective registerHost first can result in
  a configuration where remote servers cannot be stopped or
  started.  If using the adminCenter, an incorrect error message
  of server (name) does not exist is produced.
  

Problem conclusion

• The code is updated so an exception and explanatory message are
  produced if use of host credentials is requested when they do
  not exist.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Use either the collective registerHost or the collective
  updateHost command to establish host credentials prior to
  running the join or replicate commands.
  

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

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP