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

catalogd-controller-manager pod request CPU is high

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.17.0
    • 4.14
    • OLM / Registry
    • Important
    • No
    • Veritas OLM Sprint 256
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the `catalogd-controller-manager` pod could become unschedulable, and the OLM Operator would fail to install. With this fix, CPU requests are reduced for the related resources, and the issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-29705[*OCPBUGS-29705*])
      Show
      * Previously, the `catalogd-controller-manager` pod could become unschedulable, and the OLM Operator would fail to install. With this fix, CPU requests are reduced for the related resources, and the issue no longer occurs. (link: https://issues.redhat.com/browse/OCPBUGS-29705 [* OCPBUGS-29705 *])
    • Bug Fix
    • Done

      Description of problem:

          Running Openshift 4.14 TechPreview on Openstack. The operator olm fails to install. The pod catalogd-controller-manager is unable to schedule.

Events:
  Type     Reason            Age                    From               Message
  ----     ------            ----                   ----               -------
  Warning  FailedScheduling  17m                    default-scheduler  0/3 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  8m47s (x2 over 13m)    default-scheduler  0/3 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  11m                    default-scheduler  0/3 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  7m40s                  default-scheduler  0/3 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  5m34s                  default-scheduler  0/6 nodes are available: 3 Insufficient cpu, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 Insufficient cpu, 3 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  5m26s (x2 over 5m32s)  default-scheduler  0/6 nodes are available: 3 Insufficient cpu, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 Insufficient cpu, 3 Preemption is not helpful for scheduling..

There are two containers. One requests 5m cpu and the other one requests 1 cpu

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

          4.14.0-0.nightly-2024-02-19-225157

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              rh-ee-jkeister Jordan Keister
              itbrown@redhat.com Itshak Brown
              Jian Zhang Jian Zhang
              Alex Dellapenta Alex Dellapenta
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: