Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1878092

Summary: Leapp fails with "Could not create a symlink to enable leapp_resume.service"
Product: Red Hat Enterprise Linux 7 Reporter: Christophe Besson <cbesson>
Component: leapp-repositoryAssignee: Leapp team <leapp-notifications>
Status: CLOSED ERRATA QA Contact: Alois Mahdal <amahdal>
Severity: medium Docs Contact:
Priority: high    
Version: 7.8CC: jcastran, mmacura, pstodulk
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: leapp-repository-0.12.0-1.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 06:40:13 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 Christophe Besson 2020-09-11 10:03:09 UTC
Description of problem:
The reboot after the leapp upgrade sequence fails while trying to enable the leapp_resume service.
The issue occurs because /etc/systemd/system/default.target.wants doesn't exist in this environment.
Additionally, it seems there is an error while printing this error, in the function print_error().

Version-Release number of selected component (if applicable):
leapp-repository-0.10.0-2.el7_8.noarch

How reproducible:
100% for the customer with an Azure VM.
Unable to reproduce in my test env on a kVM, the directory always exists.

Steps to Reproduce:
1. Install a RHEL 7.8 an Azure VM with RHSM
2. Run leapp upgrade
3. Reboot

Actual results:
[  782.135796] localhost upgrade[660]: 2020-09-04 20:52:30.132317 [ERROR] Actor: create_systemd_service
[  782.135796] localhost upgrade[660]: Message: Could not create a symlink to enable leapp_resume.service
[  782.135796] localhost upgrade[660]: Summary:
[  782.186649] localhost upgrade[660]: Traceback (most recent call last):
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp3", line 6, in <module>
[  782.186649] localhost upgrade[660]:     sys.exit(leapp.cli.main())
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/cli/__init__.py", line 18, in main
[  782.186649] localhost upgrade[660]:     cli.command.execute('leapp version {}'.format(VERSION))
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/utils/clicmd.py", line 103, in execute
[  782.186649] localhost upgrade[660]:     args.func(args)
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/utils/clicmd.py", line 125, in called
[  782.186649] localhost upgrade[660]:     self.target(args)
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/cli/upgrade/__init__.py", line 243, in upgrade
[  782.186649] localhost upgrade[660]:     report_errors(workflow.errors)
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/utils/output.py", line 75, in report_errors
[  782.186649] localhost upgrade[660]:     print_error(error)
[  782.186649] localhost upgrade[660]:   File "/root/tmp_leapp_py3/leapp/utils/output.py", line 53, in print_error
[  782.186649] localhost upgrade[660]:     v=details[detail].rstrip().replace('\n', '\n' + ' ' * (6 + len(detail)))))
[  782.186649] localhost upgrade[660]: TypeError: string indices must be integers
[  782.292773] localhost python3[49521]: detected unhandled Python exception in '/root/tmp_leapp_py3/leapp3'
[  782.292899] localhost python3[49521]: can't communicate with ABRT daemon, is it running? [Errno 2] No such file or directory
[  782.292921] localhost python3[49521]: error sending data to ABRT daemon:
[  782.647176] localhost upgrade[660]: Container sysroot failed with error code 1.


Expected results:
The actor create_systemd_service should not fail.

Additional info:
1) The issue is known internally, so linking that.
2) Workaround: add the rd.upgrade.break=upgrade parameter and create the missing directory from the emergency shell. Once it is done, exit the shell to continue the upgrade process.

Comment 2 Petr Stodulka 2020-09-17 16:00:06 UTC
The issue is fixed in the current upstream devel version by this PR: https://github.com/oamg/leapp-repository/pull/520

Comment 7 errata-xmlrpc 2020-11-04 06:40:13 UTC
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, leapp-repository, and cockpit-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-2020:4882