The full testing of the leapp framework requires installation of the
leapp-repository builds to perform the in-place upgrade. Setting
the `INSTALL_LEAPP_FROM_COMPOSE` envar to `yes` implicates installation
of the leapp-repository packages for the test execution.
Also set LEAPP_UNSUPPORTED and LEAPP_DEVEL_* envars to be able
to perform upgrade also with old builds on the wanted new upgrade
path. We are going to resolve this in future.
The original tier0 test plans have been replaced by "new style" tests
and the original plans do not exist anymore. Updating so the tier0
test can be executed correctly.
- Bump leapp-framework to 6.1
- Create the /var/lib/leapp directory automatically if missing
- Recognize configuration files with the .yaml suffix only
- Fix CLI: allow to set falsy values as default for leapp's command options
- Resolves: RHEL-86206, RHEL-54382
- Rebase to new upstream version 0.19.0
- Add possibility to use a specified execution context for snactor run in an existing leapp.db
- Increase limits on the number of opened file descriptors and maximum size
of manipulated files when running leapp
- Resolves: RHEL-67622, RHEL-79411
- Minor improvement of the summary overview in the console output.
- Store metadata about the LEAPP plugins inside leapp audit db.
- Prevent leapp from starting if an instance is already runnning.
- Resolves: RHEL-27848, RHEL-25407
- Bump leapp-framework to 5.0
- Improve the report overview to include also information about errors
- Distinguish errors from valid reports in the generated txt report file
- Resolves: #2223312
- Bump leapp-framework to 4.0
- Improve the report summary output to make it more visible
- Fix processing data in remediation instructions with non-ascii characters
- Fix creation of Dialog for Component without choices
- Store tracebacks from actors in leapp.db
- Resolves: #2223312
