Red Hat Bugzilla – Bug 89915
config-network won't allow activation without an edit
Last modified: 2007-04-18 12:53:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021209
Description of problem:
I have two profiles set up for the same network card (three, really, but
apparently the Common profile should be unused). When trying to activate the
device, nothing happens, unless I first do a change (any change) and save the
profile first. Switching between profiles does not help. Using
redhat-config-network-cmd to activate the device always yields just a dump of
all network parameters.
This bug was present for me in the previous version as well (the one shipping
with rh9), but I used neat to choose profiles and activate the network. With
this version, however, neat throws an exception no matter what I do (i'm filing
a separate bug on this), so this issue - which I'd just about forgotten about,
suddenly became a bit more urgent. This issue was not present in rh8.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create two profiles for the same device
2. Save, reboot, log in
3. run redhat-network-control and try to activate the currently selected profile
Actual Results: nothing
Expected Results: activate the device
fixed in 1.2.4-3
Nope, the new version doesn't fix it. Instead, now not even making a change will
make the tool activate the network. I can get the network to start just fine
using ifup directly, so the basic config is at least functional.
1.2.6 fixes it.
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.