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

Request serving scheduler not cleaning up old placeholder deployments

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Undefined
    • 4.16.0
    • 4.15
    • HyperShift
    • Moderate
    • No
    • Hypershift Sprint 253
    • 1
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

        When using cluster size tagging and related request serving node scheduler, if a cluster is deleted while in the middle of resizing its request serving pods, the placeholder deployment that was created for it is not cleaned up.

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

         HyperShift main (4.16)

      How reproducible:

         Always 

      Steps to Reproduce:

          1. Setup a management cluster with request-serving machinesets
          2. Create a hosted cluster
          3. Add workers to the hosted cluster so that it changes size
          4. Delete the hosted cluster after the it's tagged with the new size but before nodes for its corresponding placeholder pods are created.
          

      Actual results:

          The placeholder deployment is never removed from the `hypershift-request-serving-autosizing-placeholder` namespace

      Expected results:

          The placeholder deployment is removed when the cluster is deleted.

      Additional info:

       

       

       

      Attachments

        Activity

          People

            cewong@redhat.com Cesar Wong
            cewong.openshift Cesar Wong
            Jie Zhao Jie Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: