Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 85920 - redhat-config-network-cmd does not work
redhat-config-network-cmd does not work
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2003-03-10 16:06 EST by ajs
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-11 10:10:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:183 normal SHIPPED_LIVE Updated redhat-config-network package available 2003-08-11 00:00:00 EDT

  None (edit)
Description ajs 2003-03-10 16:06:48 EST
Description of problem:
After configuring multiple profiles, I can not activate a brofile with the 
redhat-config-network-cmd command

Version-Release number of selected component (if applicable):
[root@sonylap1 sysconfig]# rpm -qf $(which redhat-config-network-cmd)

How reproducible:

Steps to Reproduce:
1. Configure multiple profiles
2. try to activate one with e.g. redhat-config-network-cmd --profile static

Actual results:
[root@sonylap1 sysconfig]# redhat-config-network-cmd --profile static --activate
Switching to profile static
usage: ifdown <device name>
usage: ifdown <device name>
Missing config file ../networking/profiles/static/ifcfg-eth0.

Expected results:

Additional info:
Comment 2 Harald Hoyer 2003-08-11 10:10:22 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.