IJ42222: NODE DESIGNATION FOR PMCOLLECTOR IS NOT REMOVED AFTER A POD IS RESCHEDULED TO ANOTHER NODE

APAR status

• Closed as program error.

Error description

• Node designation for pmcollector is not removed
  after a pod is rescheduled to another node
  

Local fix

• Restart system health monitoring on the affected
  core pod with 'mmsysmoncontrol restart'
  

Problem summary

• Node designation for pmcollector is not removed
  after a pod is rescheduled to another node
  

Problem conclusion

• This problem is fixed in 5.1.5 PTF 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:
  Node designation works as expected on core pods
  
  Work Around:
  Restart system health monitoring on the affected
  core pod with 'mmsysmoncontrol restart'
  Problem trigger
  pmcollector pod gets rescheduled to another node
  Symptom: Unexpected Results/Behavior
  Functional Area affected: System Health
  Customer Impact: Suggested
  

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