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

Missing checks for (in)correct target version format

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • leapp-repository-0.22.0-5.el8_10
    • No
    • Moderate
    • rhel-upgrades
    • 20
    • 2
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • All
    • None

      .What were you trying to do that didn't work?

      While testing leapp for the CTC1, leapp started to traceback unexpectedly when a target version (--target) provided in an invalid format.

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      leapp-0.19.0-3.el8_10.noarch
      leapp-upgrade-el8toel9-0.22.0-4.el8_10.noarch

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. Install leapp
      2. run leapp preupgrade --no-rhsm --target {} with any target in invalid format ["9", "9.", "09.0", "1A", "abc", "A.B", "9.a", "8.4.bad"]
      3. observe the traceback

      Expected results

      Error: Unexpected format of target version: 9.a. The required format is 'X.Y' (major and minor version).

      Actual results

      leapp produces a traceback - e.g. ValueError: Versions have to be in the form of '<integer>.<integer>' but provided was '['8.10', '9.a']'

        1. 4.leapp.out
          4 kB
        2. 3.leapp.out
          10 kB
        3. 1.leapp.out
          11 kB

              tcerna Tereza Zelinková
              ddiblik@redhat.com Daniel Diblik
              leapp-notifications leapp-notifications
              RHEL Upgrades QE Team RHEL Upgrades QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: