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

Move yum clean metadata and yum makecache to the beginning of conversion

    XMLWordPrintable

Details

    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • 2022-Q3

    Description

      After talking with mbocek@redhat.com on 9/12/2021, we discovered that may be necessary to move the calls from yum clean metadata and yum makecache to the beginning of a conversion. This is because we can make sure that the yum cache is properly populated and at the newest version right before we try to do any checks on the system, such as these: https://github.com/oamg/convert2rhel/blob/6de1d2ecf6c366641bd194eaed140c37febd3f2b/convert2rhel/checks.py#L60

      This was the pull request that introduced the cache generation: https://github.com/oamg/convert2rhel/pull/196

      Attachments

        Issue Links

          is cloned by

          Task - Represents a small unit of work that is not end-user facing. RHELC-700 [el7] Move yum clean metadata and yum makecache to the beginning of conversion

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. RHELC-134 Clean yum cache of disabled repos

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHELC-956 [el7] Clean yum cache of disabled repos

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              rolivier@redhat.com Rodolfo Olivieri
              rolivier@redhat.com Rodolfo Olivieri
              Martin Litwora
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: