Bug 2041764

Summary: ifup is missing on system but shipped by package
Product: Red Hat Enterprise Linux 9 Reporter: Chandan Chouhan <cchouhan>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.0CC: atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, till
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-18 09:09:49 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 Chandan Chouhan 2022-01-18 09:01:20 UTC 
Description of problem:ifup is missing on system but shipped by package


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

# rpm -qa | grep -i NetworkManager
NetworkManager-1.36.0-0.1.el9.x86_64

How reproducible:

- Install "NetworkManager" package.
- Run command ifup, it says the command does not exist but the binary is shipped by package.

Steps to Reproduce:
1. Install "NetworkManager" package.

2. Run below commands to verify it is shipped by "NetworkManager" package.

# yum provides "*/usr/sbin/ifup"

NetworkManager-1:1.36.0-0.1.el9.x86_64 : Network connection manager and user applications
Repo        : rhel-9-for-x86_64-baseos-beta-rpms
Matched from:
Filename    : /usr/sbin/ifup

# rpm -ql NetworkManager | grep -i "/usr/sbin/ifup"
/usr/sbin/ifup

3. But its not there on system.

# ls -l /usr/sbin/ifup
ls: cannot access '/usr/sbin/ifup': No such file or directory



Actual results:

# ls -l /usr/sbin/ifup
ls: cannot access '/usr/sbin/ifup': No such file or directory

Expected results:
"/usr/sbin/ifup" should be there on system
Comment 1 Thomas Haller 2022-01-18 09:09:49 UTC 
this is a duplicate of bug 2022418. Closing. Thank you.

*** This bug has been marked as a duplicate of bug 2022418 ***