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

glibc: Run podman as part of glibc testing

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

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • rhel-10.1, rhel-9.7
    • glibc
    • Low
    • rhel-pt-c-libs
    • ssg_platform_tools
    • 2
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • None
    • None
    • All
    • Linux
    • None

      We should make sure that podman remains functional across glibc updates.

      If we use UBI images, we should end up with a reliable container repository, so there shouldn't be many failures related to infrastructure issues.

      Testing across all UBI

      For each update on 8/9/10 we should test all supported UBI.

      podman run --rm ubi9:latest python3 -c 'import threading; thr = threading.Thread(None, lambda: None); thr.start(); thr.join'
      

      Run it for ubi8, ubi9, ubi10 (once available).

      UBI update testing

      For the UBI version that matches the glibc version under test, copy the RPMs into a container and try to upgrade the container images using dnf update *.rpm. Then run the above python3 command in the container. Also run dnf clean expire-cache followed by dnf update -y. Neither should error.

              glibc-bugzilla Platform Tools - Libraries Bot
              fweimer@redhat.com Florian Weimer
              Platform Tools - Libraries Bot Platform Tools - Libraries Bot
              qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: