Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-7017

DPA goes in error state when node affinity is specified with podConfig

XMLWordPrintable

    • Quality / Stability / Reliability
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None

      Description of problem:

      DPA reporting error when the podConfig value is empty and nodeAgent affinity is specified. DPA should only report error when podConfig.nodeSelector is specified and its not matching with nodeAgent.LoadAffinityConfig

       

      Version-Release number of selected component (if applicable):

      OADP 1.5.3

       

      How reproducible:
      Always

       

      Steps to Reproduce:
      1. Create a dpa with podConfig and nodeAgent affinity. Attached an example below:- 

      $ oc get dpa -o yaml ts-dpa
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  creationTimestamp: "2025-11-18T07:39:14Z"
  generation: 1
  name: ts-dpa
  namespace: openshift-adp
  resourceVersion: "60468"
  uid: 5770a496-a23a-4305-8e92-31b93b0a23ea
spec:
  backupLocations:
  - velero:
      credential:
        key: cloud
        name: cloud-credentials-gcp
      default: true
      objectStorage:
        bucket: oadp1370314b8sb
        prefix: velero-e2e-ac45e82c-c451-11f0-83df-5ea249a46219
      provider: gcp
  configuration:
    nodeAgent:
      enable: true
      loadAffinity:
      - nodeSelector:
          matchExpressions:
          - key: foo
            operator: In
            values:
            - bar
      podConfig:
        resourceAllocations: {}
      uploaderType: kopia
    velero:
      defaultPlugins:
      - openshift
      - gcp
      - kubevirt
      - hypershift
      - csi
      disableFsBackup: false
  logFormat: text
  podDnsConfig: {}
  snapshotLocations: []
status:
  conditions:
  - lastTransitionTime: "2025-11-18T07:39:14Z"
    message: when spec.configuration.nodeAgent.PodConfig is set, spec.configuration.nodeAgent.LoadAffinityConfig
      must define matchLabels
    reason: Error
    status: "False"
    type: Reconciled

      Actual results:

      DPA goes in error state. 

       

      Expected results: 

      Dpa should report error only when nodeAgent.podConfig.nodeSelector is not matching with spec.configuration.nodeAgent.LoadAffinityConfig

       

      Additional info:

              wnstb Wes Hayutin
              rhn-support-prajoshi Prasad Joshi
              Prasad Joshi Prasad Joshi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: