IJ53481: MMHEALTH CLUSTER SHOW IS NOT REFLECTING THE CORRECT STATUS WHEN GUI DESIGNATION MOVES TO A DIFFERENT NODE.

APAR status

• Closed as program error.

Error description

• When monitoring gets stopped and restarted due to movement of
  pods an error occurred which prevented the communication of that
  change to the cluster manager. More likely in CNSA than a
  classic scale deployment
  

Local fix

• As a possible workaround call mmhealth node show --resync -a.
  

Problem summary

• When monitoring gets stopped and restarted due to movement of
  pods an error occurred which prevented the communication of that
  change to the cluster manager. More likely in CNSA than a
  classic scale deployment
  

Problem conclusion

• This problem is fixed in 5.2.2.1
  To see all Spectrum Scale APARs and their respective
  Fix solutions refer to page: 
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale
  _apars.html
  
  
  Benefits of the solution:
  mmhealth cluster show (and CR status) will match the correct
  status and count of pods being deployed.
  
  Work Around:
  As a possible workaround call mmhealth node show --resync -a.
  
  Problem trigger:
  When monitoring gets stopped and restarted due to movement of
  pods an error occurred which prevented the communication of that
  change to the cluster manager.
  
  Symptom:
  Error output/message
  
  Platforms affected:
  ALL Linux OS environments
  
  Functional Area affected:
  System Health
  
  Customer Impact:
  High Importance
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels