Uploaded image for project: 'RHEL Conversions'
  1. RHEL Conversions
  2. RHELC-676 Allow converting CentOS Stream 8 in upstream
  3. RHELC-1366

Allow converting CentOS Stream 8 in upstream - Integration tests

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Normal Normal
    • 2.0.0
    • None
    • None
    • 13
    • False
    • Hide

      None

      Show
      None
    • False
    • RHELBU-660 - Convert CentOS Stream to RHEL
    • 2024-R2
    • Testable

      The parent issue RHELC-676 has the label that triggered autocreation of this subtask to track the relative story point estimation for the integration test part of the issue.

      The parent issue description at the time of creation of this issue was:
      The work has been already started under https://github.com/oamg/convert2rhel/pull/267.

      Acceptance criteria:

      • The stream yum variable is passed to dnf after we remove centos-stream-repos package, likely through the `--setopt=stream=8-stream` dnf option
      • The system version detection is updated to read CentOS Stream 8 /etc/system-release
      • The systeminfo.id has the value "stream" when on CentOS Stream 8
      • A new config file, similar to the one for CentOS Linux 8, is created for CentOS Stream 8
      • The releasever dnf variable mapping is updated to allow CentOS Stream 8
      • Enable automation of running integration tests on CentOS Stream 8 using Packit/Testing Farm

      Additional information:

      # cat /etc/yum.repos.d/CentOS-Stream-BaseOS.repo 
      [baseos]
      name=CentOS Stream $releasever - BaseOS
      mirrorlist=http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=BaseOS&infra=$infra
      # python3 -c 'import dnf, pprint; db = dnf.Base(); pprint.pprint(db.conf.releasever)'
      '8'
      # cat /etc/yum/vars/stream 
      8-stream
      # rpm -qf /etc/yum/vars/stream 
      centos-stream-repos-8-6.el8.noarch
      

            ddiblik@redhat.com Daniel Diblik
            rhel-process-autobot RHEL Jira bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: