IBM Support

PH11844: Joining a member to a pre-18.0.0.2 controller fails with default collective-wide ssh key

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Joining a collective member to a back level collective
    controller fails when the collective is configured to use a
    collective-wide ssh key.
    

Local fix

  • Workaround:
    
    Add the member using the same level the controller has
    Once the member has been joined, upgrade the member
    to the new Fix Pack level.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty ND collectives               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Joining a member at 18.0.0.2 or later   *
    *                      to a controller at 18.0.0.1 or earlier  *
    *                      fails.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Joining a member at 18.0.0.2 or later to a controller at
    18.0.0.1 or earlier fails with
    Error: CWWKX0218E: The MBean
    'WebSphere:feature=collectiveController,type=CollectiveRegistrat
    ion,name=CollectiveRegistration' does not have an attribute by
    the name 'PublicSSHKey'.
    
    When collective join option --useCollectiveSSHKey=false is
    specified it fails with
    Error: java.lang.IllegalArgumentException: CWWKX9012E: The
    CollectiveRegistration MBean join operation could not be
    completed. There is an unrecognized property:
    collectiveSSHKeySupported.
    

Problem conclusion

  • Level detection is corrected so that join works with default
    options and fails with specific error message when incompatible
    option --useCollectiveSSHKey=true is used.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 19.0.0.5.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH11844

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-07

  • Closed date

    2019-05-29

  • Last modified date

    2019-05-29

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021