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

Repository Maintenance Pod Affinity configuration missing in DPA spec

XMLWordPrintable

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

      None

      Show
      None
    • False
    • oadp-operator-bundle-container-1.5.0-103
    • ToDo
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None

      Description of problem:

      The new configurations for repository maintenance job pod affinity is missing from the DPA spec

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

      1.5.0

      How reproducible:

      Always

      Steps to Reproduce:

      CONTEXT: OBSERVED WHILE TESTING

      https://github.com/openshift/oadp-operator/blob/3d79865dc1abf79052fa1f169a42747e1c70a766/docs/scheduling_and_node_affinity.md#2-configuring-repository-maintenance-new-in-oadp-15

      oc explain dataprotectionapplication.spec.configuration
      GROUP:      oadp.openshift.io
      KIND:       DataProtectionApplication
      VERSION:    v1alpha1
      
      FIELD: configuration <Object>
      
      
      DESCRIPTION:
          configuration is used to configure the data protection application's server
          config
          
      FIELDS:
        nodeAgent	<Object>
          NodeAgent is needed to allow selection between kopia or restic
      
        restic	<Object>
          (do not use warning) restic field is for backwards compatibility and
          will be removed in the future. Use nodeAgent field instead
      
        velero	<Object>
          <no description>
      

      Actual results:

      No key "repositoryMaintenance" and related configs.

      Expected results:

      There should be repositoryMaintenance job affinity config available to configure.

      Additional info:

              rhn-engineering-mpryc Michal Pryc
              rhn-support-ssingla Sachin Singla
              Sachin Singla Sachin Singla
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: