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 2152377

Summary: Leapp fails : Actor quagga_to_frr unexpectedly terminated with exit code: 1
Product: Red Hat Enterprise Linux 7 Reporter: paygupta
Component: leapp-repositoryAssignee: Leapp Notifications Bot <leapp-notifications-bot>
Status: CLOSED MIGRATED QA Contact: upgrades-and-conversions
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.9CC: pstodulk
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-12 12:35:22 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 paygupta 2022-12-11 10:50:26 UTC
Description of problem:

During final phase of leapp upgrade system goes to Emergency mode with below error :

=========================================================================================
Actor quagga_to_frr unexpectedly terminated with exit code: 1 - Please check the above details
=========================================================================================

Version-Release number of selected component (if applicable):

leapp-0.15.0-2.el7_9.noarch
leapp-deps-0.15.0-2.el7_9.noarch
leapp-upgrade-el7toel8-0.17.0-1.el7_9.noarch
leapp-upgrade-el7toel8-deps-0.17.0-1.el7_9.noarch

quagga-0.99.22.4-5.el7_4.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install "quagga" package on RHEL 7.9 system
2. Install leapp packages
3. Run leapp preupgrade
4. RUn leapp upgrade
5. Reboot the system 
6. Boot from Upgrade initramfs

Actual results:

System goes to Emergency mode with below error :

 ====> * quagga_to_frr
         Edit frr configuration on the new system.
 Process Process-224:
 Traceback (most recent call last):
   File "/usr/lib64/python3.6/multiprocessing/process.py", line 258, in _bootstrap
     self.run()
   File "/usr/lib64/python3.6/multiprocessing/process.py", line 93, in run
     self._target(*self._args, **self._kwargs)
   File "/root/tmp_leapp_py3/leapp/repository/actor_definition.py", line 72, in _do_run
     actor_instance.run(*args, **kwargs)
   File "/root/tmp_leapp_py3/leapp/actors/__init__.py", line 289, in run
     self.process(*args)
   File "/etc/leapp/repos.d/system_upgrade/el7toel8/actors/quaggatofrr/actor.py", line 23, in process
     process_facts(quagga_facts)
   File "/etc/leapp/repos.d/system_upgrade/el7toel8/actors/quaggatofrr/libraries/quaggatofrr.py", line 99, in process_facts
     _copy_config_files(QUAGGA_CONF_FILES, FRR_CONF_FILES)
   File "/etc/leapp/repos.d/system_upgrade/el7toel8/actors/quaggatofrr/libraries/quaggatofrr.py", line 82, in _copy_config_files
     shutil.copy(full_path, dest_path)
   File "/usr/lib64/python3.6/shutil.py", line 245, in copy
     copyfile(src, dst, follow_symlinks=follow_symlinks)
   File "/usr/lib64/python3.6/shutil.py", line 121, in copyfile
     with open(dst, 'wb') as fdst:
 IsADirectoryError: [Errno 21] Is a directory: '/etc/frr/'
 ==============================================================================================
 Actor quagga_to_frr unexpectedly terminated with exit code: 1 - Please check the above details
 ==============================================================================================
 Debug output written to /var/log/leapp/leapp-upgrade.log
 ============================================================
                           REPORT
 ============================================================
 A report has been generated at /var/log/leapp/leapp-report.json
 A report has been generated at /var/log/leapp/leapp-report.txt
 ============================================================
                        END OF REPORT
 ============================================================

Expected results:

Upgrade should complete without any error.

Comment 4 Petr Stodulka 2023-01-27 13:32:16 UTC
The fix has been merged in upstream and will be part of the next release:
* https://github.com/oamg/leapp-repository/pull/1008

Comment 5 Petr Stodulka 2023-01-27 13:41:37 UTC
My apologize, I switched the bug. This issue dissapears with this release due to mentioned fix also, as the frr package will be installed during the upgrade, however we want to keep it opened to deliver additional fix that will work as a seatbelt in case it happens (for whatever reason) that frr packages will not be installed.

Comment 6 RHEL Program Management 2023-09-12 12:34:11 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 7 RHEL Program Management 2023-09-12 12:35:22 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.