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

Move rhel-els-container-8.4.0 to E4S/AUS repos

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • rhel-8.4.0.z
    • rhel-els-container
    • None
    • None
    • None
    • rhel-sst-container-tools
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      Updates for ELS base image when release goes from EUS to AUS/TUS

      SP - make any infrastructure changes to support 8.4 TUS / AUS, including the 8.4 els base image - N/A - This should be setup with SP following the regular templates (TBD what OSCI needs to do for 8.6 or greater)

      RHEL devel - Make the following updates to the ELS base image when a release goes from EUS to AUS:

      Update content_sets.yml to use E4S repos and not EUS

      E4S repos are needed for x86_64 and ppc64le support for OSP. AUS and TUS are x86_64 only.

      All updates that go to TUS also go to AUS and E4S repos. So Freshmaker will notice that TUS/AUS/E4S CVE fixes impact the ELS base images built with E4S repos and rebuild the images.

      Container-tools updates that we release with product version = TUS also go to AUS and E4S repos.

      Update container.yml and image-build.conf to use x86_64 and ppc64le archs. When Freshmaker, SP, or OSCI rebuild the 8.y ELS images (when in TUS after EUS EOL), they will build them for both x86_64 and ppc64le.

      OSCI - when any ELS base image for RHEL 8.6 or greater goes to EUS or TUS, change the “fallback content sets” for these images in batches.yml to use EUS repos for EUS and use E4S repos for TUS.

              rhn-support-jnovy Jindrich Novy
              rhn-support-jnovy Jindrich Novy
              Container Runtime Eng Bot Container Runtime Eng Bot
              David Darrah David Darrah (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: