Bug 1958993 - Leapp can print a confusing warning when the NetworkManager has been completely removed
Summary: Leapp can print a confusing warning when the NetworkManager has been complete...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Leapp Notifications Bot
QA Contact: upgrades-and-conversions
URL:
Whiteboard:
Depends On:
Blocks: 1818088
TreeView+ depends on / blocked
 
Reported: 2021-05-10 14:37 UTC by Christophe Besson
Modified: 2023-07-31 07:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-4906 0 None None None 2023-05-11 08:04:57 UTC

Description Christophe Besson 2021-05-10 14:37:04 UTC 
Description of problem:
During the leapp_resume.service, at the very end of the upgrade, customer reported a confusing warning:

May  6 15:50:54 <HOSTNAME> leapp3[1735]: 2021-05-06 15:50:54.29  WARNING  PID: 2126 leapp.workflow.FirstBoot.network_manager_update_connections: Error calling nm-update-client-ids script: Command ['/usr/bin/python3', 'tools/nm-update-client-ids.py'] failed with exit code 1.

As per the sosreport, the NetworkManager has been completely removed from that system, and ifcfg files contain the directive NM_CONTROLLED=no. All was going well, but this warning should not be shown in this case, since that python script tries to connect to the NM daemon.

Version-Release number of selected component (if applicable):
leapp-repository-0.13.0-2.el7_9

How reproducible:
100% for the customer. Not tested internally.
Note You need to log in before you can comment on or make changes to this bug.