Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-113511

Update runc to 1.3.1

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • rhel-9.6
    • container-tools
    • None
    • No
    • Critical
    • rhel-container-tools
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      There are a few upstream Kubernetes tests that are flaky on OCP. We’re comparing the results and noticed that in upstream Kubernetes CI they are running ** runc 1.3.0, while OCP is still on runc 1.2.4.

      To properly bisect this problem, we need to ensure we’re using the same settings downstream. One step is updating to runc 1.3.1 (the latest version), since the same tests are not flaky upstream.

      This way, we can work on de-flaking downstream tests step by step and make sure we are comparing apples to apples, rather than apples to oranges.

      What is the impact of this issue to you?

      It will block the 4.20 OCP release

      Please provide the package NVR for which the bug is seen:

      I don't have the reproducer but here's the OCP bug: https://issues.redhat.com/browse/OCPBUGS-61220

      How reproducible is this bug?:

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      Actual results

              container-runtime-eng Container Runtime Eng Bot
              skunkerk Sohan Kunkerkar
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: