Uploaded image for project: 'RHEL Conversions'
  1. RHEL Conversions
  2. RHELC-777

[RFE]: When testing for latest kernel version, versions from different major releases should not be considered

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 0.22
    • convert2rhel
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • 2022-Q4, 2023-Q1, 2023-Q2
    • Testable

      Scenario:

      • A centos 7 client is registered to a Red Hat Satellite and consumes all centos and rhel content from it. No outside network access is allowed for the client.
      • With subscriptions being created for each product it is common for a user to have ALL centos repos under the same product. With a single subscription providing all centos repos or with Simple Content Access (SCA) enabled, a client of Satellite will get all versions of centos available (excluding registration and activation key settings).
      • This will cause a centos 7 system to fail the latest kernel check for a kernel version that is not applicable to the host's OS and ultimately fail the conversion.

       

      With each major release of centos linked to a new major version of a kernel, we should only be testing for the latest version of the major version applicable to the host that is converting.

      IE:

      • centos 7 checks for kernel-3* only
      • centos 8 checks for kernel-4* only
      • centos 9 checks for kernel-5* only
      • etc

       

      If this is not possible, then the statement in the official documentation in chapter 3, step 7, sub-step ii should illustrate a stricter requirement to have centos major release in different products and/or configure an activation key to 'override disable' non-matching centos repos that don't match the same major release of the host. Thi 

            mbocek@redhat.com Michal Bocek
            rhn-support-tasander Taft Sanders
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: