IT35145: IBM SPECTRUM PROTECT PLUS CONTAINER BACKUP SUPPORT PVC SNAPSHOT FAILS DUE TO SLA REASSIGNMENT

APAR status

• Closed as program error.

Error description

• Snapshots of Persistent Volume Claim (PVC) will fail if the SLA
  of the PVC is changed from one SLA to another SLA after a
  previous snapshot operations has been successfully performed.
  
  This error will produce the following error message during the
  snapshot operation:
  
  CTGGK3089 An unexpected error occurred during the backup.
  KeyError('sla',) This error occurred while performing back up of
  PersistentVolumeClaim <Cluster Name>:<Namespace>:<PVC Name>.
  
  The key phrase is in the error message is KeyError('sla',)
  
  This error will occur on OpenShift and Kubernetes platforms.
  

Local fix

• Delete the BaasReq objects of each Persistent Volume Claim using
  the following commands:
  
  Kubernetes:
  kubectl delete baasreq --namespace <namespace of PVC> <Name of
  PVC>
  
  OpenShift:
  oc delete baasreq --namespace <namespace of PVC> <Name of PVC>
  
  Then perform a snapshot operation on each SLA that is assigned
  to the affected Persistent Volume Claims. The BaasReq objects of
  each Persistent Volume Claim will be recreated during the
  snapshot operation.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus Container Backup Support level     *
  * 10.1.7 on Kubernetes and OpenShift environments.             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in Spectrum Protect Plus Container     *
  * Backup Support levels 10.1.7 ifix2 and 10.1.8. Note that     *
  * this is subject to change at the discretion of IBM           *
  ****************************************************************
  

Problem conclusion

• This problem has been fixed so that after encountering condition
  BaasReq object lack an SLA field, the new behavior is that
  BaasReq objects will be updated to have a correct SLA field and
  snapshots continue.
  

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:

Modules/Macros

• k8s      ocp
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels