Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-22956

When build capability is disabled, ConfigObserver controller does not run

XMLWordPrintable

    • Important
    • No
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Hide
       ---------- edited for release notes ----------
      * Previously, when the `Build` cluster capability was not enabled, the ConfigObserver controller failed to synchronize the build informer and could not start successfully. With this release, the ConfigObserver controller successfully starts when the `Build` capability is not enabled. (link:https://issues.redhat.com/browse/OCPBUGS-22956[*OCPBUGS-22956*])
       ---------- edited for release notes ----------
      Without this patch, when build capability is not enabled, ConfigObserver controller tries to sync build informer and fails on this syncing and as a result, controller can not accomplish the tasks that is assigned. This fix enables ConfigObserver successfully starts, when build capability is not enabled.
      Show
       ---------- edited for release notes ---------- * Previously, when the `Build` cluster capability was not enabled, the ConfigObserver controller failed to synchronize the build informer and could not start successfully. With this release, the ConfigObserver controller successfully starts when the `Build` capability is not enabled. (link: https://issues.redhat.com/browse/OCPBUGS-22956 [* OCPBUGS-22956 *])  ---------- edited for release notes ---------- Without this patch, when build capability is not enabled, ConfigObserver controller tries to sync build informer and fails on this syncing and as a result, controller can not accomplish the tasks that is assigned. This fix enables ConfigObserver successfully starts, when build capability is not enabled.
    • Bug Fix
    • Done
    • 11/20: best case target 4.14.4

      Description of problem:

      ConfigObserver controller waits until the all given informers are marked as synced including the build informer. However, when build capability is disabled, that causes ConfigObserver's blockage and never runs.

This is likely only happening on 4.15 because capability watching mechanism was bound to ConfigObserver in 4.15.

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

      4.15

      How reproducible:

      Launch cluster-bot cluster via "launch 4.15.0-0.nightly-2023-11-05-192858,openshift/cluster-openshift-controller-manager-operator#315 no-capabilities"

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      ConfigObserver controller stuck in failure

      Expected results:

      ConfigObserver controller runs and successfully clear all deployer service accounts when deploymentconfig capability is disabled.

      Additional info:

       

              aguclu@redhat.com Arda Guclu
              aguclu@redhat.com Arda Guclu
              Jitendar Singh Jitendar Singh
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: