IT34213: sethagrp -u command incorrectly reports 'High Availability configuration already migrated' when command actually fails.

APAR status

• Closed as program error.

Error description

• When issuing the 'sethagrp -u' command after migrating the
  first appliance in an HA group from MQ 8.0 to MQ 9.1.0.x, the
  command reported  'High availability configuration already
  migrated' and completed successfully, however, the queue
  managers did not fail over to the upgraded appliance as
  expected. Second appliance had to be upgraded and the 'sethagrp
  -u' reissued for the queue managers to be migrated successfully.
  
  The sethagrp logs shows that for each queue manager, the
  sethagrp reported: High availability configuration already
  migrated.
  
  Mon Aug 31 09:16:19 CEST 2020: { Entering sethagrp -u HAQM1
  
  Mon Aug 31 09:16:20 CEST 2020:  pcs resource show HAQM1_clone
  Mon Aug 31 09:16:21 CEST 2020:  Error: unable to get cib
  Error: unable to get cib
  Mon Aug 31 09:16:21 CEST 2020:  rc(1)
  Mon Aug 31 09:16:21 CEST 2020:  High availability configuration
  already migrated
  Mon Aug 31 09:16:21 CEST 2020:   The sethagrp command succeeded.
  Mon Aug 31 09:16:21 CEST 2020: } Leaving sethagrp 0
  
  
  Once second appliance was upgraded, the sethagrp -u was issued
  again and this time it worked. The logs shows...
  
  Mon Aug 31 09:49:56 CEST 2020: { Entering sethagrp -u HAQM1
  Mon Aug 31 09:50:00 CEST 2020:  Migration complete
  Mon Aug 31 09:50:00 CEST 2020:   The sethagrp command succeeded.
  Mon Aug 31 09:50:00 CEST 2020: } Leaving sethagrp 0
  

Local fix

• Confirm that the queue manager has failed over to the upgraded
  appliance as expected after sethagrp -u reports successful
  completion. If it has not, wait a few minutes for the cluster
  processes on the appliance to synchronize data and retry the
  command
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All MQ Appliance users using HA configuration.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A timing window existed whereby if the sethagrp -u command was
  run before the internal HA cluster services had fully
  initialized on the other (upgraded) appliance, the command would
  fail internally. A logic error meant that the sethagrp command
  incorrectly reported success in response to this scenario.
  

Problem conclusion

• The code has been modified to report an error message if the
  command fails unexpectedly. The command should then be manually
  retried after a short delay to allow the upgraded appliance to
  initialize its internal HA cluster services.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.11
  v9.2 LTS   9.2.0.5
  v9.x CD    9.2.5
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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

• Fixed component name

  MQ APPLIANCE M2

• Fixed component ID

  5737H4700

Applicable component levels