Bug 2106065
Summary: | 'leapp preupgrade' traceback _sub_commands[cmdname].parser.error(leftover) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> |
Component: | leapp | Assignee: | Petr Stodulka <pstodulk> |
Status: | CLOSED ERRATA | QA Contact: | Michal Macura <mmacura> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.6 | CC: | mmacura |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | leapp-0.15.0-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-08 09:46:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Corey Marthaler
2022-07-11 16:31:17 UTC
Same thing for other cmds, something must not be installed properly? [root@hayes-01 ~]# leapp upgrade --reboot Traceback (most recent call last): File "/usr/bin/leapp", line 11, in <module> load_entry_point('leapp==0.14.0', 'console_scripts', 'leapp')() File "/usr/lib/python3.6/site-packages/leapp/cli/__init__.py", line 43, in main cli.command.execute('leapp version {}'.format(VERSION)) File "/usr/lib/python3.6/site-packages/leapp/utils/clicmd.py", line 105, in execute self._sub_commands[cmdname].parser.error(leftover) KeyError: 'leapp' Hi, thanks for the report. It's unrelated to /boot and boom. The problem is caused just by wrong instalation. On the system is installed just the leapp framework, without leapp repositories for upgrades. So there is not discovered any leapp subcommand. All required packages needs to be installed, which can be done by: # dnf install leapp-upgrade Or you can specifically install the specific package directly, e.g. leapp-upgrade-el8toel9 in your case. We will replace the traceback by proper error msg to make it more clear, like: ,,The 'upgrade' subcommand has not been discovered. Possibly the particular leapp repository has not been installed?" Note: It is important to understand that leapp component contains only the framework and basic utility (+ another devel/testing tools) to make the use of the framework more friendly. When the system should be upgraded, the proper leapp repository / repositories needs to be installed (which in our case installs also particular leapp CLI subcommands, like `preupgrade`, `upgrade`, ...). These repositories are provided by the leapp-repository component (srpm) on RHEL systems. To make it easy for people so they do not need to know how particular RPMs are named, we instruct them to install `leapp-upgrade` which covers all packages needed for the In-Place Upgrade. But as written above, the traceback is unfortunate and we agree that proper error msg should be delivered. This has been fixed in upstream by the following PR: https://github.com/oamg/leapp/pull/785 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (leapp bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:7591 |