Blasted Fedora, the F20 release is still a mess

Well some of the update packages are a mess anyway.

Did a simple ‘yum update’ on the VM host machine. Something in one of the rpm pre/post update scripts decided to destroy the network configuration completely. The host server plus all the VMs on that machine just went off the network.

The hard drive light on the host server was still blinking, so plugged a screen into it. An ‘ifconfig’ command showed the entite network setup had been blown away as part of the update; only physical interfaces showed and with no assigned ip-addresses; the bridge configuration was also gone.

Bother. Had to ‘virsh destroy’ all the VMs (as without a network I couldn’t login to them to shut them down cleanly) and reboot.

On the reboot it reran the network scripts correctly and bridging is back and the host and guests accessable again.

I probably should go CentOS, but I have started using a lot of the new features in Fedora that probably won’t be rolled into RedHat for a few years yet, so I’m sort of stuck with Fedora.

Which is relatively stable apart from stupid little things like this.

About mark

At work, been working on Tandems for around 30yrs (programming + sysadmin), plus AIX and Solaris sysadmin also thrown in during the last 20yrs; also about 5yrs on MVS (mainly operations and automation but also smp/e work). At home I have been using linux for decades. Programming background is commercially in TAL/COBOL/SCOBOL/C(Tandem); 370 assembler(MVS); C, perl and shell scripting in *nix; and Microsoft Macro Assembler(windows).
This entry was posted in Unix. Bookmark the permalink.