Re: [libvirt] [Users] Vdsm/libvir error during deploy

On Mon, Dec 24, 2012 at 02:18:48PM +0100, Joop wrote:
Dan Kenigsberg wrote:
Which version of libvirt is installed on your host?
libvirt-1.0.1-2.fc17.x86_64 libvirt-client-1.0.1-2.fc17.x86_64 libvirt-daemon-1.0.1-2.fc17.x86_64 libvirt-daemon-config-network-1.0.1-2.fc17.x86_64 libvirt-daemon-config-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-interface-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-lxc-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-network-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nodedev-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-qemu-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-secret-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-storage-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-uml-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-xen-1.0.1-2.fc17.x86_64 libvirt-lock-sanlock-1.0.1-2.fc17.x86_64 libvirt-python-1.0.1-2.fc17.x86_64
From virt-preview repo [fedora-virt-preview] name=Virtualization packages from Rawhide built for latest Fedora baseurl=http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearc... enabled=1 skip_if_unavailable=1 gpgcheck=0
What is the output of the following python script on your machine? Mine says "1". Could it be that your libvirt says "0"?
=============
from vdsm import libvirtconnection
conn = libvirtconnection.get() netXml = """<network> <name>test</name> <forward mode='passthrough'> <interface dev='em1'/> </forward> </network> """
net = conn.networkDefineXML(netXml) net.create() print net.isPersistent() net.destroy() net.undefine()
0 libvir: Network Driver error : Network not found: no network with matching uuid Traceback (most recent call last): File "test.py", line 16, in <module> net.undefine() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2154, in undefine if ret == -1: raise libvirtError ('virNetworkUndefine() failed', net=self) libvirt.libvirtError: Network not found: no network with matching uuid
So '0' :-(( Suppose that error isn't good either. Should I downgrade to an earlier version of libvirt?
Please try. My guess is that this is a libvirt bug added by http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20818... in libvirt 1.0.1. More authoritative answer is expected by those added to the CC line.

Dan Kenigsberg wrote:
On Mon, Dec 24, 2012 at 02:18:48PM +0100, Joop wrote:
Dan Kenigsberg wrote:
Which version of libvirt is installed on your host?
libvirt-1.0.1-2.fc17.x86_64 libvirt-client-1.0.1-2.fc17.x86_64 libvirt-daemon-1.0.1-2.fc17.x86_64 libvirt-daemon-config-network-1.0.1-2.fc17.x86_64 libvirt-daemon-config-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-interface-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-lxc-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-network-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nodedev-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-qemu-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-secret-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-storage-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-uml-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-xen-1.0.1-2.fc17.x86_64 libvirt-lock-sanlock-1.0.1-2.fc17.x86_64 libvirt-python-1.0.1-2.fc17.x86_64
From virt-preview repo [fedora-virt-preview] name=Virtualization packages from Rawhide built for latest Fedora baseurl=http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearc... enabled=1 skip_if_unavailable=1 gpgcheck=0
What is the output of the following python script on your machine? Mine says "1". Could it be that your libvirt says "0"?
=============
from vdsm import libvirtconnection
conn = libvirtconnection.get() netXml = """<network> <name>test</name> <forward mode='passthrough'> <interface dev='em1'/> </forward> </network> """
net = conn.networkDefineXML(netXml) net.create() print net.isPersistent() net.destroy() net.undefine()
0 libvir: Network Driver error : Network not found: no network with matching uuid Traceback (most recent call last): File "test.py", line 16, in <module> net.undefine() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2154, in undefine if ret == -1: raise libvirtError ('virNetworkUndefine() failed', net=self) libvirt.libvirtError: Network not found: no network with matching uuid
So '0' :-(( Suppose that error isn't good either. Should I downgrade to an earlier version of libvirt?
Please try. My guess is that this is a libvirt bug added by http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20818... in libvirt 1.0.1. More authoritative answer is expected by those added to the CC line.
Went back to libvirt-0.10. from the danken repo and now it works. Will reinstall st01 in the same way as a test. Thanks for the help and have a nice X-mas. Joop

On 2012年12月25日 00:15, Joop wrote:
Dan Kenigsberg wrote:
On Mon, Dec 24, 2012 at 02:18:48PM +0100, Joop wrote:
Dan Kenigsberg wrote:
Which version of libvirt is installed on your host?
libvirt-1.0.1-2.fc17.x86_64 libvirt-client-1.0.1-2.fc17.x86_64 libvirt-daemon-1.0.1-2.fc17.x86_64 libvirt-daemon-config-network-1.0.1-2.fc17.x86_64 libvirt-daemon-config-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-interface-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-lxc-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-network-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nodedev-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-qemu-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-secret-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-storage-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-uml-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-xen-1.0.1-2.fc17.x86_64 libvirt-lock-sanlock-1.0.1-2.fc17.x86_64 libvirt-python-1.0.1-2.fc17.x86_64
From virt-preview repo [fedora-virt-preview] name=Virtualization packages from Rawhide built for latest Fedora baseurl=http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearc... enabled=1 skip_if_unavailable=1 gpgcheck=0
What is the output of the following python script on your machine? Mine says "1". Could it be that your libvirt says "0"?
=============
from vdsm import libvirtconnection
conn = libvirtconnection.get() netXml = """<network> <name>test</name> <forward mode='passthrough'> <interface dev='em1'/> </forward> </network> """
net = conn.networkDefineXML(netXml) net.create() print net.isPersistent() net.destroy() net.undefine()
0 libvir: Network Driver error : Network not found: no network with matching uuid Traceback (most recent call last): File "test.py", line 16, in<module> net.undefine() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2154, in undefine if ret == -1: raise libvirtError ('virNetworkUndefine() failed', net=self) libvirt.libvirtError: Network not found: no network with matching uuid
So '0' :-(( Suppose that error isn't good either. Should I downgrade to an earlier version of libvirt?
Please try. My guess is that this is a libvirt bug added by http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20818... in libvirt 1.0.1. More authoritative answer is expected by those added to the CC line.
Right, it's the regression introduced by 0211fd6e04, the new defined network is not marked as persistent, and it's removed from the internal maintained list by net.destroy(), that's why the error comes ("no network with matching uuid").
Went back to libvirt-0.10. from the danken repo and now it works. Will reinstall st01 in the same way as a test.
Thanks for the help and have a nice X-mas.
Joop
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Osier Yang wrote:
On 2012年12月25日 00:15, Joop wrote:
Dan Kenigsberg wrote:
On Mon, Dec 24, 2012 at 02:18:48PM +0100, Joop wrote:
Dan Kenigsberg wrote:
Which version of libvirt is installed on your host?
libvirt-1.0.1-2.fc17.x86_64 libvirt-client-1.0.1-2.fc17.x86_64 libvirt-daemon-1.0.1-2.fc17.x86_64 libvirt-daemon-config-network-1.0.1-2.fc17.x86_64 libvirt-daemon-config-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-interface-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-lxc-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-network-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nodedev-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-nwfilter-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-qemu-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-secret-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-storage-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-uml-1.0.1-2.fc17.x86_64 libvirt-daemon-driver-xen-1.0.1-2.fc17.x86_64 libvirt-lock-sanlock-1.0.1-2.fc17.x86_64 libvirt-python-1.0.1-2.fc17.x86_64
From virt-preview repo [fedora-virt-preview] name=Virtualization packages from Rawhide built for latest Fedora baseurl=http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearc...
enabled=1 skip_if_unavailable=1 gpgcheck=0
What is the output of the following python script on your machine? Mine says "1". Could it be that your libvirt says "0"?
=============
from vdsm import libvirtconnection
conn = libvirtconnection.get() netXml = """<network> <name>test</name> <forward mode='passthrough'> <interface dev='em1'/> </forward> </network> """
net = conn.networkDefineXML(netXml) net.create() print net.isPersistent() net.destroy() net.undefine()
0 libvir: Network Driver error : Network not found: no network with matching uuid Traceback (most recent call last): File "test.py", line 16, in<module> net.undefine() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2154, in undefine if ret == -1: raise libvirtError ('virNetworkUndefine() failed', net=self) libvirt.libvirtError: Network not found: no network with matching uuid
So '0' :-(( Suppose that error isn't good either. Should I downgrade to an earlier version of libvirt?
Please try. My guess is that this is a libvirt bug added by http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=0211fd6e04cdc402da20818...
in libvirt 1.0.1. More authoritative answer is expected by those added to the CC line.
Right, it's the regression introduced by 0211fd6e04, the new defined network is not marked as persistent, and it's removed from the internal maintained list by net.destroy(), that's why the error comes ("no network with matching uuid").
Went back to libvirt-0.10. from the danken repo and now it works. Will reinstall st01 in the same way as a test.
Thanks for the help and have a nice X-mas. Re-installed two other hosts in the same manner using libvirt-0.10.1-2 from the danken repo and both work. Will keep on eye on libvirt to see when this is fixed and then try an upgrade.
Thanks, Joop

Sorry I forgot to edit the libvirt version, this is what is installed now and atleast works on on host, going to test the next host and then add a gluster cluster. libvirt-0.10.1-2.fc17.x86_64 libvirt-client-0.10.1-2.fc17.x86_64 libvirt-daemon-0.10.1-2.fc17.x86_64 libvirt-daemon-config-network-0.10.1-2.fc17.x86_64 libvirt-daemon-config-nwfilter-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-interface-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-libxl-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-lxc-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-network-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-nodedev-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-nwfilter-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-qemu-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-secret-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-storage-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-uml-0.10.1-2.fc17.x86_64 libvirt-daemon-driver-xen-0.10.1-2.fc17.x86_64 libvirt-lock-sanlock-0.10.1-2.fc17.x86_64 libvirt-python-0.10.1-2.fc17.x86_64
participants (3)
-
Dan Kenigsberg
-
Joop
-
Osier Yang