On Tue, Feb 11, 2014 at 12:13:49PM +0100, Thierry Parmentelat wrote: > Hello Laine; please see inline — many thanks for the feedback in any case — Thierry > > > 4) Even if you are installing/upgrading libvirt-daemon-config-network > > and the system doesn't already have a default network in place, *if > > libvirt-daemon-config-network package is installed/updated after the > > libvirt-daemon package is installed/updated (i.e. libvirtd has already > > been restarted), then the newly placed default.xml will not be > > recognized until the libvirtd service is again restarted. (actually it > > appears that yum (or maybe rpm) is smart enough to do upgrade the files > > from all packages before running any %post scripts, so that may not be a > > problem). > > I value your explanations very much > however it seems that in our case: > . this is observed in a test framework, and we run into this problem right after installing for the first time, there’s no upgrading in the loop > . I should probably have added the extract below to the report > this is captured at build-time when preparing the image that these nodes will be running > as you can see the post install snippet responsible for creating the /etc/libvirt/… stub fails because at that time, the source from /usr/share/libvirt is not available yet > > Installing : libvirt-client-1.2.1-0.x86_64 242/340 > Installing : libvirt-python-1.2.1-0.x86_64 243/340 > ... > Installing : libvirt-daemon-1.2.1-0.x86_64 249/340 > Installing : libvirt-daemon-driver-secret-1.2.1-0.x86_64 250/340 > Installing : libvirt-daemon-driver-nodedev-1.2.1-0.x86_64 251/340 > Installing : libvirt-daemon-config-network-1.2.1-0.x86_64 252/340 > /var/tmp/rpm-tmp.4piryn: line 3: /usr/share/libvirt/networks/default.xml: No such file or directory > ln: failed to create symbolic link '/etc/libvirt/qemu/networks/autostart/default.xml': No such file or directory > warning: %post(libvirt-daemon-config-network-1.2.1-0.x86_64) scriptlet failed, exit status 1 > Non-fatal POSTIN scriptlet failure in rpm package libvirt-daemon-config-network-1.2.1-0.x86_64 > Installing : libvirt-daemon-driver-uml-1.2.1-0.x86_64 253/340 > Installing : libvirt-daemon-config-nwfilter-1.2.1-0.x86_64 254/340 > Installing : ebtables-2.0.10-11.fc20.x86_64 255/340 > Installing : libvirt-daemon-driver-nwfilter-1.2.1-0.x86_64 256/340 > ... > Installing : libvirt-daemon-driver-network-1.2.1-0.x86_64 276/340 > Installing : libvirt-daemon-driver-lxc-1.2.1-0.x86_64 277/340 Yep, this is pretty clear that we have a missing dep. libvirt-daemon-config-network Requires libvirt-daemon, which is fine when we do *not* have driver modules enabled. In your case though we do have driver modules enabled, so we must add a dep on libvirt-daemon-driver-network from config-network Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list