Description of problem: system-config-network-tui does not display or permit the configuration of ONBOOT. I had to edit /etc/sysconfig/network-scripts/ifcfg-eth0 to get the network to get ONBOOT=yes, which is an easy workaround, but the tui config tool should support changing it (I'm quite certain it used to). Version-Release number of selected component (if applicable): system-config-network-tui-1.5.97-1.fc11.noarch How reproducible: 100% This system is fully updated F11 installed via the text mode installer without NetworkManager. The only change required to get networking to be configured on boot was to change ONBOOT=no to ONBOOT=yes in /etc/sysconfig/network-scripts/ifcfg-eth0
I've updated the version to F13, as I just installed F13 Alpha and it still doesn't permit configuring ONBOOT. Editing ifcfg-eth0 still works.
I looked briefly through the code, and it still seems to be able to set onboot, although I'm not a Python wizard. I wonder if this behavior might be related to the fact that this is a virtio interface on a virtual machine. Here's the udev info. F13 ~ # udevinfo info -a -p /sys/class/net/eth0/ Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/virtio-pci/virtio0/net/eth0': KERNEL=="eth0" SUBSYSTEM=="net" DRIVER=="" ATTR{addr_len}=="6" ATTR{dev_id}=="0x0" ATTR{ifalias}=="" ATTR{iflink}=="2" ATTR{ifindex}=="2" ATTR{features}=="0x190a69" ATTR{type}=="1" ATTR{link_mode}=="0" ATTR{address}=="52:54:00:34:70:e6" ATTR{broadcast}=="ff:ff:ff:ff:ff:ff" ATTR{carrier}=="1" ATTR{dormant}=="0" ATTR{operstate}=="unknown" ATTR{mtu}=="1500" ATTR{flags}=="0x1003" ATTR{tx_queue_len}=="1000" looking at parent device '/devices/virtio-pci/virtio0': KERNELS=="virtio0" SUBSYSTEMS=="virtio" DRIVERS=="virtio_net" ATTRS{device}=="1" ATTRS{vendor}=="6900" ATTRS{status}=="0x00000007" ATTRS{modalias}=="virtio:d00000001v00001AF4" ATTRS{features}=="11000101110111011111000000001000" looking at parent device '/devices/virtio-pci': KERNELS=="virtio-pci" SUBSYSTEMS=="" DRIVERS=="" F13 ~ #
I installed F13 on bare metal and I cannot set ONBOOT on that system, either.
F14 also.
Harald, what's up with this BZ? Is the tool not supposed to be able to set ONBOOT? The behavior is the same in RHEL 6.3.
(In reply to comment #5) > Harald, what's up with this BZ? Is the tool not supposed to be able to set > ONBOOT? The behavior is the same in RHEL 6.3. system-config-network is officially dead... although, we will fix it in RHEL6.3 and maybe also in F17
(In reply to comment #6) > system-config-network is officially dead... although, we will fix it in > RHEL6.3 and maybe also in F17 What's the right way to configure networking in text only mode? I'm happy to hack the ifcfg files, but I'd rather not go behind the system's back if it doesn't expect it.
(In reply to comment #7) > (In reply to comment #6) > > system-config-network is officially dead... although, we will fix it in > > RHEL6.3 and maybe also in F17 > > What's the right way to configure networking in text only mode? I'm happy > to hack the ifcfg files, but I'd rather not go behind the system's back if > it doesn't expect it. nag the NetworkManager guys for a TUI in RHEL7
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.