Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-1373

MCO pod using sandboxed containers scc causes it to fail

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • High
    • OCP 4.11
    • 4.10-1.2.0
    • Operator
    • None
    • 1
    • False
    • False
    • Kata Sprint #215, Kata Sprint #219, Kata Sprint #220
    • 0
    • 0.0

    Description

      Description

      Installed OSC on a cluster and then CNV. After reboot of node (due to CNV installation) an mco-controller pod
      (machine config operator) doesn't come up.

      Steps to reproduce

      1. Install OSC
      2. Install CNV
      3. watch mco pods

      Expected result

      All mco pods should come up

      Actual result

      One mco pod on a master note does not come up because it was labelled to use the osc scc.

      Impact

      Because the osc scc is not available on master node the MCO pod can't run and the node is degraded

      Env

      OCP 4.10 cluster with OSC and CNV installed

      Additional helpful info

      <logs, screenshot, doc links, etc.>

      Attachments

        Activity

          People

            rhgkurz Greg Kurz
            ehadley Eric Hadley
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: