APAR status
Closed as program error.
Error description
problem after upgrading to Spectrum Scale 5.0.5.3 and it appears that due to a mismatch between the 5.0.0.1 minReleaseLevel and the Spectrum Scale code level of 5.0.5.3 that the mmcommon script was failing to call tspcachescan correctly.
Local fix
Problem summary
On clusters having minReleaseLevel at 5.0.1, with mixed version nodes available from 5.0.1.X through till 5.0.5.X nodes and where the Gateway node is at level 5.0.5.X - the newer level of Gateway nodes finds it hard to co-exist with the older level nodes causing a recovery failure repeatedly.
Problem conclusion
Benefits of the solution: For mixed version nodes in a cluster with Gateway nodes at the latest 5.0.5.X levels, the fix makes it easier to proceed and complete recovery procedures. Work around: None available. Problem trigger: Triggering AFM Fileset recovery on a mixed version cluster with Gateway node at the 5.0.5.X level and minReleaseLevel on the cluster is at the 5.0.1 level Symptom: Unexpected Behavior Platforms affected: ALL Linux OS environments (AFM Gateway nodes) Functional Area affected: AFM Customer Impact: High Importance
Temporary fix
Comments
APAR Information
APAR number
IJ29186
Reported component name
SPEC SCALE ADV
Reported component ID
5737F35AP
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-11-09
Closed date
2020-11-09
Last modified date
2020-11-09
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 ADV
Fixed component ID
5737F35AP
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
03 December 2020