Uploaded image for project: 'RHEL Conversions'
  1. RHEL Conversions
  2. RHELC-1291 versionlock.list file not backed up and restored after the rollback
  3. RHELC-1292

versionlock.list file not a backed up and restored after the rollback - Integration tests

XMLWordPrintable

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

      None

      Show
      None
    • False
    • Testable

      The parent issue RHELC-1291 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 versionlock.list file does not get backed up, thus not getting restored during the rollback.
      Reproducer:

      install yum-plugin-versionlock
      yum install -y yum-plugin-versionlock
      versionlock at least one of the packages
      yum versionlock kernel
      the versionlock is now set in both /etc/yum/pluginconf.d/versionlock.list and (if present) /etc/dnf/plugind/versionlock.list files, which are not empty
      run convert2rhel analysis
      convert2rhel -y analyze --debug
      convert2rhel recognizes the versionlock is set (file exist and is not empty)

      After the rollback both the versionlock.list files are empty.
      Same goes for the /var/lib/convert2rhel/backup/versionlock.list

            Unassigned Unassigned
            rhel-process-autobot RHEL Jira bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: