preupg(1)

NAME
preupg - The Preupgrade Assistant performs an assessment of the system from the "upgradability" point of view

SYNOPSIS
preupg can be used if the modules are installed on the system preupg [-l, --list-contents] preupg [-d, --debug] [--skip-common] [-s, --scan PATH] [-m, --mode MODE] [--force] [--text] [--kickstart] [--dst-arch] preupg [-v, --verbose] [--riskcheck] preupg [-c, --contents PATH] preupg [--cleanup]

DESCRIPTION
preupg is the main binary file of the Preupgrade Assistant.

OPTIONS

-c, --contents PATH
    Generates a content for the Preupgrade Assistant usage.

-d, --debug
    Makes the Preupgrade Assistant log with the debugging information.

--cleanup
    Cleans all files created by preupg about the previous state of the machine.

--force
    Suppresses the user's interaction.

--kickstart
    Generates Kickstart.

-l, --list
    Shows a list of installed modules.

-m, --mode MODE
    Selects one (or both) from the possible modes: migrate or upgrade. Both modes are used by default. upgrade is used for in-place upgrades on the same machine by fedup or redhat-upgrade-tool. migrate is used for Kickstart migration with a new clean installation and the settings of the new system as close as possible to the settings of the original system.

-s, --scan PATH
    Executes the selected assessment taken from the option list.

--skip-common
    Skips generating common log files generated during the previous assessment.

--riskcheck
    Returns a value which depends on the INPLACE RISK results. If verbose mode is mentioned, it shows all in-place risks generated during the assessment. Return values are 0 for SLIGHT or MEDIUM risk, 1 for HIGH risk and 2 for EXTREME risk.

--text
    Converts HTML results into a text form by elinks, lynx or w3m.

-v, --verbose
    Shows more information during the assessment. Verbose can be repeated more times.

--dst-arch
    Specifies the destination architecture for migrations. Allowed options are: i386-x86_64 or ppc-ppc64.

RETURN STATES
preupg command returns several return values. Possible return values are: 0 - preupg works properly and the modules exit with results PASS. 10 - preupg works properly but modules finish with 10. Modules exit with results NOT_APPLICABLE, NOT_CHECKED, NOT_SELECTED. 11 - preupg works properly but modules finish with 11. Modules exit with results INFORMATIONAL. 12 - preupg works properly but modules finish with 12. Modules exit with results FIXED, NEEDS_INSPECTION or NEEDS_ACTION. 13 - preupg works properly but modules finish with 13. Modules exit with results FAILED. 14 - preupg works properly but modules finish with 14. Modules exit with results UNKNOWN. 15 - preupg works properly but modules finish with 15. Modules exit with results ERROR. 20 - preupg cannot find a proper upgrade scenario. 21 - preupg is executed with parameters mode and select-rules. This is not allowed. 22 - preupg is executed with parameters riskcheck, cleanup and kickstart. These options are not allowed to be used together. 23 - preupg has to be executed as root. 24 - preupg has to be executed before the Kickstart generation. 25 - openscap and openscap-engine-sce are not installed on the system. 26 - You specified a text convertor which is not allowed. Allowed convertors are w3m, lynx and elinks. 27 - The /usr/share/preupgrade/common/scripts.txt file is missing. The Preupgrade Assistant is not installed properly and needs to be reinstalled. 28 - We have detected some troubles with sending the report to WEB-UI. Check if it is installed.

NOTES
All common log files are stored in the /var/cache/preupgrade/common directory. Assessment results are stored in the /root/preupgrade directory. Tarballs with the assessments are stored in the /root/preupgrade-results directory.

AUTHORS
Petr Hracek, <phracek@redhat.com> (man page)