Uploaded image for project: 'Red Hat Developer Hub Bugs'
  1. Red Hat Developer Hub Bugs
  2. RHDHBUGS-1577

UI pod stays 'Pending' when using the operator

XMLWordPrintable

    • 1
    • False
    • Hide

      None

      Show
      None
    • True
    • Hide
      The Red Hat Developer Hub (RHDH) pod created by the RHDH Operator may not be scheduled on some clusters due to missing resource requests, causing the RHDH application to be unavailable.
      This update adds CPU and memory requests to the default configuration of the Operator, so that RHDH pods can be scheduled and start properly.
      Show
      The Red Hat Developer Hub (RHDH) pod created by the RHDH Operator may not be scheduled on some clusters due to missing resource requests, causing the RHDH application to be unavailable. This update adds CPU and memory requests to the default configuration of the Operator, so that RHDH pods can be scheduled and start properly.
    • Bug Fix
    • Proposed
    • RHDH Core Team 3256

      Description of problem:

      i'm trying to use the operator to spawn DH instance on a ROSA 4.15 cluster. The UI pod does not start and I see the following issue in `Events` : `0/2 nodes are available: 2 Insufficient cpu. preemption: 0/2 nodes are available: 2 No preemption victims found for incoming pod..`. I looked at the Deployment, and see that while the containers have limits, they do not have requests.

      The cluster has 8 CPU. I install the gitops and pipeline operators. The overview reports about 6.7 of available CPU.

      I install the developer-hub operator and create a backstage instance. There's still more than 6 CPU available reported in the Overview console page. Yet the pod isn't scheduled.

      Adding the following `requests` field to the `deployment.yaml` of `backstage-default-config` for both containers fixes the issue.
      ```
      requests:
      cpu: 125m
      memory: 128Mi
      ```

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Get a ROSA cluster via clusterbot
      2. install the GitOps and Pipelines operators
      3. Install the Developer Hub operator
      4. Create a new backstage instace

      Actual results:

      1. UI pod is created but is not scheduled, stays in `Pending` status.

      Expected results:

      1. UI pod is in `Running` status.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      Slack thread

              gazarenk-1 Gennady Azarenkov
              rarnaud@redhat.com Romain Arnaud
              RHIDP - Install
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: