- Previously, an
ip linkcommand was called before the master device was properly set. Consequently, the slaves could be in the
unknownstate. This has been fixed by calling
ip linkfor master after the device is installed properly, and all slaves are up. As a result, all slaves are in the expected state and connected to the master device.
- Previously, the naming policy for VLAN names was too strict. Consequently, the
ifdownutility failed to work with descriptively-named interfaces. To fix this bug, the name format check has been removed and
ifdownnow works as expected.
- Prior to this update, there was a typographic error in the
/etc/sysconfig/network-scripts/ifup-aliasesfile, which caused the duplicate check to fail. The typo has been corrected and the check works again.
BONDING_OPTSvariable was applied by the
ifuputility on a slave interface, even if the master was already on and had active slaves. This caused an error message to be returned by
ifup. To address this bug, it is now checked whether the master does not have any active slaves before applying
BONDING_OPTS, and no error messages are returned.
- Prior to this update, the
arpingutility, which checks for IP address duplicates in the network, failed when the parent device was not up. Consequently, the failure was handled the same way as finding of a second IP address in the network. To fix this bug,
ifup-aliasesfiles have been set to be checked whether the master device is up before the duplicity check is run. As a result, no error messages are returned when the parent device is down in the described scenario.
rename_device.cfile did not correspond with VLAN interfaces, and thus could lead to improperly named physical interfaces. A patch has been provided to address this bug and interfaces are now named predictably and properly.
- When calling the
vgchange -a ycommand instead of
vgchange -a ayon the
netfsinterface by the
rc.sysinitdaemon, all volumes were activated. This update provides a patch to fix this bug. Now, only the volumes declared to be activated are actually activated. If the list is not declared, all volumes are activated by default.
- Previously, when a slave was attached to a master interface, which did not have a correct mode set, the interface did not work properly and could eventually cause a kernel oops. To fix this bug, the
BONDING_OPTSvariables are set before the master interface is brought up, which is the correct order of setting.
- If there was a process blocking a file system from unmounting, the
/etc/init.d/haltscript tried to kill all processes currently using the file system, including the script itself. Consequently, the system became unresponsive during reboot. With this update, shutdown script PIDs are excluded from the kill command, which enables the system to reboot normally.
- When the
ifuputility was used to set up a master interface, the
BONDING_OPTSvariables were not applied. Consequently, bonding mode configuration done through the
ifcfgutility had no effect. A patch has been provided to fix this bug.
BONDING_OPTSare now applied and bonding mode works in the described scenario.
- If a network bond device had a name that was a substring of another bond device, both devices changed their states due to an incorrect test of the bond device name. A patch has been provided in the regular expression test and bond devices change their states as expected.
udevdaemon is an event-driven hot-plug agent. Previously, an
udevevent for serial console availability was emitted only on boot. If runlevels were changed, the process was not restarted, because the event had already been processed. Consequently, the serial console was not restarted when entering and then exiting runlevel 1. With this update, the
fedora.serial-console-availableevent is emitted on the post-stop of the serial console, and the console is now restarted as expected.
- Prior to this update, no check if an address had already been used was performed for alias interfaces. Consequently, an already used IP address could be assigned to an alias interface. To fix this bug, the IP address is checked whether it is already used. If it is, an error message is returned and the IP address is not assigned.
- Previously, the
initutility tried to add a bond device even if it already existed. Consequently, a warning message was returned. A patch that checks whether a bond device already exists has been provided and warning messages are no longer returned.
- Prior to this update, the
crypttab(5)manual page did not describe handling white spaces in passwords. Now, the manual page has been updated and contains information concerning a password with white spaces.
crypttab (5)manual page contained a typografic error (crypptab insted of crypttab), which has now been corrected.
- Previously, usage description was missing in the
/init/serial.conffiles and this information was not returned in error messages. With this update, the information has been added to the aforementioned files and is now returned via an error message.
- Prior to this update, the
/dev/shmfile system was mounted by the
dracututility without attributes from the
/etc/fstabfile. To fix this bug,
/dev/shmis now remounted by the
rc.sysinitscript. As a result,
/dev/shmnow contains the attributes from
- Previous version of the
sysconfig.txtfile instructed users to put the
VLAN=yesoption in the global configuration file. Consequently, interfaces with names containing a dot were recognized as VLAN interfaces. The
sysconfig.txtfile has been changed so that the VLAN describing line instructs users to include the VLAN option in the interface configuration file, and the aforementioned devices are no longer recognized as VLAN interfaces.
sysconfig.txtfile advised users to use the
saslauthd -acommand instead of
saslauthd -v, which caused the command to fail with an error message. In
sysconfig.txt, the error in the command has been corrected and the
saslauthdutility now returns expected results.
- When the
ifuputility initiated VLAN interfaces, the
sysctlvalues were not used. With this update,
sysctlvalues in the described scenario and VLAN interfaces are configured as expected.
brctldaemon is used to connect two Ethernet segments in a protocol-independent way, based on an Ethernet address, rather than an IP address. In order to provide a simple and centralized bridge configuration, bridge options can now be used via
BRIDGING_OPTS. As a result, a space-separated list of bridging options for either a bridge device or a port device can be added when the
ifuputility is used.
- The updated
halt.localfile has been enhanced with new variables to reflect the character of call. This change leaves users with better knowledge of how
halt.localwas called during a halt sequence.
- With this update, it is possible to disable duplicate address detection in order to allow administrators to use direct routing without ARP checks.