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

VolSync/Data Mover: nodeSelector used to create mover pod does not match Node's hostname label

XMLWordPrintable

    • False
    • Hide

      None

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

      Tracks https://github.com/backube/volsync/issues/420

      This may block data mover ci

      To reproduce, on the worker node that the pod with pvc to backup runs on (or just simply do this on all worker nodes) run the following

      oc label node/<nodename> kubernetes.io/hostname=somethingelse --overwrite

      Then try to use data mover.

          1.
          		 [RedHat QE] Verify Bug OADP-771 - VolSync/Data Mover: nodeSelector used to create mover pod does not match Node's hostname label Sub-task Closed Undefined Maya Peretz
          2.
          		 [IBM QE-Z] Verify Bug OADP-771 - VolSync/Data Mover: nodeSelector used to create mover pod does not match Node's hostname label Sub-task Release Pending Undefined SHIVA SAI K (Inactive)
          3.
          		 [IBM QE-P] Verify Bug OADP-771 - VolSync/Data Mover: nodeSelector used to create mover pod does not match Node's hostname label Sub-task Release Pending Undefined Sonia Garudi

              emcmulla@redhat.com Emily McMullan
              wnstb Wes Hayutin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: