Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-11701

openstackclient infinite reconcile loop when cluster/namespace default nodeSelector is configured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhos-18.0.4
    • rhos-18.0.0, rhos-18.0.1, rhos-18.0.2, rhos-18.0.3, rhos-18.0 FR 1 (Nov 2024)
    • openstack-operator
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • No Docs Impact
    • openstack-operator-bundle-container-1.0.6-5
    • None
    • Release Note Not Required
    • Moderate

      OpenShift supports cluster or namespace default nodeSelector annotations which, when configured, will mutate the nodeSelector field in a pod spec.

      This is not compatible with the current spec comparison logic for the openstackclient pod. The controller restores the nodeSelector back to the expected value on each reconcile and recreates the pod.

              rhn-engineering-owalsh Oliver Walsh
              rhn-support-dhill Dave Hill
              rhos-conplat-core-operators
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: