Resource quotas cause backup errors

Resource quotas defined on the cluster can cause errors when you create a backup.

Symptoms

In the backup and restore log file (for example, cpdbr-oadp.log or CPD-CLI*.log), you see an error like in the following example:

message: 'Error creating: pods "zen-checkpoint-backup-job-dbg2h-5q7zh" is forbidden:
    failed quota: cpd-quota: must specify limits.cpu for: zen-checkpoint-backup; limits.memory
    for: zen-checkpoint-backup; requests.cpu for: zen-checkpoint-backup; requests.memory
    for: zen-checkpoint-backup'

Causes

Resource quota constraints prevent a backup job from creating a pod. As a result, the job time out.

Environment

This problem can occur when you try to create a backup with the Cloud Pak for Data OADP utility or IBM Fusion.

Diagnosing the problem

Check that resource quotas are present by running the following command:

oc get resourcequotas -n ${PROJECT_CPD_INST_OPERANDS}
Example output:

NAME        AGE     REQUEST                                                         LIMIT
cpd-quota   6d10h   requests.cpu: 84593m/200, requests.memory: 347562698Ki/1200Gi   limits.cpu: 247995m/800, limits.memory: 780777970483200m/1800Gi

Resolving the problem

Do the following steps:

  1. Add LimitRange to the ${PROJECT_CPD_INST_OPERANDS} project:
    apiVersion: v1
kind: LimitRange
metadata:
  name: cpu-resource-limits-2
  namespace: ${PROJECT_CPD_INST_OPERANDS}
spec:
  limits:
  - default:
      cpu: 300m
      memory: 200Mi
    defaultRequest:
      cpu: 200m
      memory: 200Mi
    type: Container
  2. Verify that the LimitRange was created:
    oc get LimitRange -A
    Example output:
    NAMESPACE                           NAME                    CREATED AT
${PROJECT_CPD_INST_OPERANDS}        cpu-resource-limits-2   <timestamp>
  3. Retry the backup.