- Users - oVirt List Archives

virt-in-virt problem: DHCP failing for a container in a oVirt VM
by Will Dennis 06 May '16

06 May '16

--_000_F3282EEAFF180F43BAF1AD0A7C34739D3DA20Enjmailneclabscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, Have an interesting problem - I am running a VM in oVirt that is running Pr= oxmox VE 4.1 OS, which I have spun up a container on. The container is set= for DHCP, and I have verified that it is sending Discover packets as norma= l, and that these packets are making it out of the Proxmox VM to the oVirt = bridge (which is attached to a VLAN sub-interface of a bond interface.) How= ever, these packets do NOT make it past the oVirt bridge. The interesting t= hing is that the Proxmox VM (as well as any other VM I spin up on oVirt) wo= rks fine with DHCP. (I also have other oVirt VMs instantiated which are usi= ng LXD to spin up containers, and I have the same problem with those as wel= l.) I checked a bunch of stuff, and the only clue I could find is that it s= eems that the oVirt bridge is not learning the MAC for the container on the= VM, even though it does learn the VM's MAC, but I can capture DHCP traffic= coming from the container off the 'vnet0' interface which is joined to tha= t bridge... Info: =3D=3D=3D=3D=3D off Proxmox VM =3D=3D=3D=3D=3D Container's MAC address: 32:62:65:61:65:33 root@proxmox-02:~# ip link sh 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DE= FAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master= vmbr0 state UP mode DEFAULT group default qlen 1000 link/ether 00:1a:4a:16:01:57 brd ff:ff:ff:ff:ff:ff 3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP= mode DEFAULT group default link/ether 00:1a:4a:16:01:57 brd ff:ff:ff:ff:ff:ff 7: veth100i0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fa= st master vmbr0 state UP mode DEFAULT group default qlen 1000 link/ether fe:50:4f:3c:bd:b8 brd ff:ff:ff:ff:ff:ff link-netnsid 0 <<<= veth connection to container root@proxmox-02:~# brctl showmacs vmbr0 port no mac addr is local? ageing timer 1 00:12:3f:24:a4:54 no 112.88 1 00:1a:4a:16:01:56 no 0.02 1 00:1a:4a:16:01:57 yes 0.00 1 00:1a:4a:16:01:57 yes 0.00 1 00:24:50:dd:a2:05 no 1.37 1 18:03:73:e3:be:5a no 21.04 1 18:03:73:e3:ca:24 no 4.23 1 18:03:73:e3:cb:5b no 48.41 1 18:03:73:e3:cc:e5 no 91.93 1 18:03:73:e3:cd:b8 no 151.04 1 18:03:73:e3:ce:43 no 0.80 1 18:03:73:e3:d0:a4 no 290.74 1 18:03:73:e3:d4:26 no 34.06 1 18:03:73:e3:d5:3d no 6.36 1 18:03:73:e4:23:08 no 88.76 1 18:03:73:e4:25:92 no 111.86 1 18:03:73:e4:26:2f no 9.54 1 18:03:73:e4:2b:4c no 114.86 1 18:03:73:e4:31:15 no 263.91 1 18:03:73:e4:6c:19 no 6.36 1 18:03:73:e4:7e:0a no 103.06 1 18:03:73:e8:16:e0 no 23.21 2 32:62:65:61:65:33 no 5.08 <<< container's M= AC learned on Proxmox bridge 1 34:17:eb:9b:e0:29 no 265.22 1 34:17:eb:9b:f8:ea no 114.86 1 44:d3:ca:7e:3c:ff no 0.00 1 78:2b:cb:3b:ca:b9 no 284.70 1 78:2b:cb:92:cb:cb no 279.70 1 78:2b:cb:93:08:a8 no 287.05 1 b8:ca:3a:7a:70:63 no 4.83 1 f8:bc:12:69:bb:a3 no 121.82 2 fe:50:4f:3c:bd:b8 yes 0.00 2 fe:50:4f:3c:bd:b8 yes 0.00 =3D=3D=3D=3D=3D off oVirt node that has Proxmox VM =3D=3D=3D=3D (relevant lines from 'ip link show') 2: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue s= tate UP mode DEFAULT 3: enp4s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_f= ast master bond0 state UP mode DEFAULT qlen 1000 4: enp4s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_f= ast master bond0 state UP mode DEFAULT qlen 1000 8: bond0.169@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueu= e master 169-net state UP mode DEFAULT 10: bond0.180@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noque= ue master 180-net state UP mode DEFAULT 12: bond0.207@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noque= ue master 207-net state UP mode DEFAULT 13: 207-net: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state= UP mode DEFAULT 30: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast mast= er 207-net state UNKNOWN mode DEFAULT qlen 500 <<< veth connection to Proxm= ox VM 31: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast mast= er 207-net state UNKNOWN mode DEFAULT qlen 500 [root@ovirt-node-03 ~]# brctl show bridge name bridge id STP enabled interfaces 169-net 8000.0015177be9da no bond0.169 180-net 8000.0015177be9da no bond0.180 207-net 8000.0015177be9da no bond0.207 vnet0 vnet1 ;vdsmdummy; 8000.000000000000 no ovirtmgmt 8000.00218535086a no enp12s0f0 [root@ovirt-node-03 ~]# tcpdump -i vnet0 -vvv -s 1500 '(port 67 or port 68)= ' tcpdump: WARNING: vnet0: no IPv4 address assigned tcpdump: listening on vnet0, link-type EN10MB (Ethernet), capture size 1500= bytes 12:52:07.628571 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto = UDP (17), length 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Reque= st from 32:62:65:61:65:33 (oui Unknown), length 300, xid 0x9efc4849, secs 9= 4, Flags [none] (0x0000) Client-Ethernet-Address 32:62:65:61:65:33 (oui Unknown) ^^^^^= ^^^^^^^^^^^^^^^^^^^^^^^^^ Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Hostname Option 12, length 5: "test1" Parameter-Request Option 55, length 13: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Option 119, Hostname Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Rou= te NTP END Option 255, length 0 PAD Option 0, length 0, occurs 34 [root@ovirt-node-03 ~]# brctl showmacs 207-net port no mac addr is local? ageing timer 1 00:15:17:7b:e9:da yes 0.00 1 00:15:17:7b:e9:da yes 0.00 3 00:1a:4a:16:01:56 no 0.11 2 00:1a:4a:16:01:57 no 0.13 << Proxmox VM's et= h0 MAC learned 1 00:24:50:dd:a2:05 no 1.05 1 18:03:73:e3:be:5a no 198.87 1 18:03:73:e3:ca:24 no 60.01 1 18:03:73:e3:cb:5b no 68.26 1 18:03:73:e3:cd:b8 no 41.39 1 18:03:73:e3:d4:26 no 57.25 1 18:03:73:e3:d5:3d no 133.53 1 18:03:73:e4:23:08 no 34.28 1 18:03:73:e4:26:2f no 20.10 1 18:03:73:e4:2b:4c no 22.49 1 18:03:73:e4:6c:19 no 14.87 1 18:03:73:e4:7e:0a no 54.46 1 18:03:73:e8:16:e0 no 28.71 1 34:17:eb:9b:f8:ea no 22.49 1 44:d3:ca:7e:3c:ff no 0.60 1 78:2b:cb:3b:ca:b9 no 217.66 1 78:2b:cb:92:cb:cb no 194.18 1 78:2b:cb:93:08:a8 no 102.49 1 b8:ca:3a:7a:70:63 no 4.19 1 f8:bc:12:69:bb:a3 no 110.52 3 fe:1a:4a:16:01:56 yes 0.00 <<< veth connectio= n to Proxmox VM (veth0) 3 fe:1a:4a:16:01:56 yes 0.00 2 fe:1a:4a:16:01:57 yes 0.00 2 fe:1a:4a:16:01:57 yes 0.00 (notice no other entries for port 3 - should be learning MAC 32:62:65:61:65= :33 from incoming traffic on vnet0) =3D=3D=3D=3D=3D --_000_F3282EEAFF180F43BAF1AD0A7C34739D3DA20Enjmailneclabscom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> Hi all,<o:p></o:p> <o:p> </o:p> Have an interesting problem – I am running a V= M in oVirt that is running Proxmox VE 4.1 OS, which I have spun up a contai= ner on.  The container is set for DHCP, and I have verified that it is= sending Discover packets as normal, and that these packets are making it out of the Proxmox VM to the oVirt bridge (whi= ch is attached to a VLAN sub-interface of a bond interface.) However, these= packets do NOT make it past the oVirt bridge. The interesting thing is tha= t the Proxmox VM (as well as any other VM I spin up on oVirt) works fine with DHCP. (I also have other oVir= t VMs instantiated which are using LXD to spin up containers, and I have th= e same problem with those as well.) I checked a bunch of stuff, and the onl= y clue I could find is that it seems that the oVirt bridge is not learning the MAC for the container on the VM,= even though it does learn the VM’s MAC, but I can capture DHCP traff= ic coming from the container off the ‘vnet0’ interface which is= joined to that bridge...<o:p></o:p> <o:p> </o:p> Info:<o:p></o:p> <o:p> </o:p> =3D=3D=3D=3D=3D off Proxmox VM =3D=3D=3D=3D=3D<o:p><= /o:p> <o:p> </o:p> Container's MAC address: 32:62:65:61:65:33<o:p></o:p= > <o:p> </o:p> root@proxmox-02:~# ip link sh<o:p></o:p> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc = noqueue state UNKNOWN mode DEFAULT group default<o:p></o:p>     link/loopback 00:00:00:00:00:00 b= rd 00:00:00:00:00:00<o:p></o:p> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu= 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qle= n 1000<o:p></o:p>     link/ether 00:1a:4a:16:01:57 brd = ff:ff:ff:ff:ff:ff<o:p></o:p> 3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mt= u 1500 qdisc noqueue state UP mode DEFAULT group default<o:p></o:p>     link/ether 00:1a:4a:16:01:57 brd = ff:ff:ff:ff:ff:ff<o:p></o:p> 7: veth100i0@if6: <BROADCAST,MULTICAST,UP,LOWER_U= P> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group de= fault qlen 1000<o:p></o:p>     link/ether fe:50:4f:3c:bd:b8 brd = ff:ff:ff:ff:ff:ff link-netnsid 0   <<< veth connection t= o container<o:p></o:p> <o:p> </o:p> root@proxmox-02:~# brctl showmacs vmbr0<o:p></o:p></= p> port no mac addr      =           is local? &nbsp= ;     ageing timer<o:p></o:p>   1     00:12:3f:24:a4:54&n= bsp;      no      &n= bsp;        112.88<o:p></o:p>   1     00:1a:4a:16:01:56&n= bsp;      no      &n= bsp;          0.02<o:p></o:p><= /p>   1     00:1a:4a:16:01:57&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   1     00:1a:4a:16:01:57&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   1     00:24:50:dd:a2:05&n= bsp;      no      &n= bsp;          1.37<o:p></o:p><= /p>   1     18:03:73:e3:be:5a&n= bsp;      no      &n= bsp;         21.04<o:p></o:p>   1     18:03:73:e3:ca:24&n= bsp;      no       &= nbsp;         4.23<o:p></o:p><= /p>   1     18:03:73:e3:cb:5b&n= bsp;      no      &n= bsp;         48.41<o:p></o:p>   1     18:03:73:e3:cc:e5&n= bsp;      no      &n= bsp;         91.93<o:p></o:p>   1     18:03:73:e3:cd:b8&n= bsp;      no      &n= bsp;        151.04<o:p></o:p>   1     18:03:73:e3:ce:43&n= bsp;      no      &n= bsp;          0.80<o:p></o:p><= /p>   1     18:03:73:e3:d0:a4&n= bsp;      no      &n= bsp;        290.74<o:p></o:p>   1     18:03:73:e3:d4:26&n= bsp;      no      &n= bsp;         34.06<o:p></o:p>   1     18:03:73:e3:d5:3d&n= bsp;      no      &n= bsp;          6.36<o:p></o:p><= /p>   1     18:03:73:e4:23:08&n= bsp;      no      &n= bsp;         88.76<o:p></o:p>   1     18:03:73:e4:25:92&n= bsp;      no      &n= bsp;        111.86<o:p></o:p>   1     18:03:73:e4:26:2f&n= bsp;      no      &n= bsp;          9.54<o:p></o:p><= /p>   1     18:03:73:e4:2b:4c&n= bsp;      no      &n= bsp;        114.86<o:p></o:p>   1     18:03:73:e4:31:15&n= bsp;      no      &n= bsp;        263.91<o:p></o:p>   1     18:03:73:e4:6c:19&n= bsp;      no      &n= bsp;          6.36<o:p></o:p><= /p>   1     18:03:73:e4:7e:0a&n= bsp;      no      &n= bsp;        103.06<o:p></o:p>   1     18:03:73:e8:16:e0&n= bsp;      no      &n= bsp;         23.21<o:p></o:p>   2     32:62:65:61:65:33&n= bsp;      no      &n= bsp;          5.08  = <<< container’s MAC learned on Proxmox bridge<o:p></o:p></p= >   1     34:17:eb:9b:e0:29&n= bsp;      no      &n= bsp;        265.22<o:p></o:p>   1     34:17:eb:9b:f8:ea&n= bsp;      no      &n= bsp;        114.86<o:p></o:p>   1     44:d3:ca:7e:3c:ff&n= bsp;      no      &n= bsp;          0.00<o:p></o:p><= /p>   1     78:2b:cb:3b:ca:b9&n= bsp;      no      &n= bsp;        284.70<o:p></o:p>   1     78:2b:cb:92:cb:cb&n= bsp;      no      &n= bsp;        279.70<o:p></o:p>   1     78:2b:cb:93:08:a8&n= bsp;      no      &n= bsp;        287.05<o:p></o:p>   1     b8:ca:3a:7a:70:63&n= bsp;      no      &n= bsp;          4.83<o:p></o:p><= /p>   1     f8:bc:12:69:bb:a3&n= bsp;      no      &n= bsp;        121.82<o:p></o:p>   2     fe:50:4f:3c:bd:b8&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   2     fe:50:4f:3c:bd:b8&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p> <o:p> </o:p> =3D=3D=3D=3D=3D off oVirt node that has Proxmox VM = =3D=3D=3D=3D<o:p></o:p> <o:p> </o:p> (relevant lines from ‘ip link show’)<o:p= ></o:p> 2: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP= > mtu 1500 qdisc noqueue state UP mode DEFAULT<o:p></o:p> 3: enp4s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_= UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 10= 00<o:p></o:p> 4: enp4s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_= UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 10= 00<o:p></o:p> 8: bond0.169@bond0: <BROADCAST,MULTICAST,UP,LOWER= _UP> mtu 1500 qdisc noqueue master 169-net state UP mode DEFAULT<o:p></o= :p> 10: bond0.180@bond0: <BROADCAST,MULTICAST,UP,LOWE= R_UP> mtu 1500 qdisc noqueue master 180-net state UP mode DEFAULT<o:p></= o:p> 12: bond0.207@bond0: <BROADCAST,MULTICAST,UP,LOWE= R_UP> mtu 1500 qdisc noqueue master 207-net state UP mode DEFAULT<o:p></= o:p> 13: 207-net: <BROADCAST,MULTICAST,UP,LOWER_UP>= mtu 1500 qdisc noqueue state UP mode DEFAULT<o:p></o:p> 30: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> m= tu 1500 qdisc pfifo_fast master 207-net state UNKNOWN mode DEFAULT qlen 500= <<< veth connection to Proxmox VM<o:p></o:p> 31: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> m= tu 1500 qdisc pfifo_fast master 207-net state UNKNOWN mode DEFAULT qlen 500= <o:p></o:p> <o:p> </o:p> [root@ovirt-node-03 ~]# brctl show<o:p></o:p> bridge name     bridge id &= nbsp;            &nb= sp;STP enabled     interfaces<o:p></o:p> 169-net       &nb= sp; 8000.0015177be9da       no  &nb= sp;           bond0.169<o= :p></o:p> 180-net       &nb= sp; 8000.0015177be9da       no  &nb= sp;           bond0.180<o= :p></o:p> 207-net       &nb= sp; 8000.0015177be9da       no  &nb= sp;           bond0.207<o= :p></o:p>         &nbs= p;             =             &nb= sp;            =          vnet0<o:p></o:p>         &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;         vnet1<o:p></o:p> ;vdsmdummy;     8000.00000000000= 0       no<o:p></o:p> ovirtmgmt       8000.0= 0218535086a       no    &= nbsp;         enp12s0f0<o:p></o:p><= /p> <o:p> </o:p> <o:p> </o:p> [root@ovirt-node-03 ~]# tcpdump -i vnet0 -vvv -s 150= 0 '(port 67 or port 68)'<o:p></o:p> tcpdump: WARNING: vnet0: no IPv4 address assigned<o:= p></o:p> tcpdump: listening on vnet0, link-type EN10MB (Ether= net), capture size 1500 bytes<o:p></o:p> 12:52:07.628571 IP (tos 0x10, ttl 128, id 0, offset = 0, flags [none], proto UDP (17), length 328)<o:p></o:p>     0.0.0.0.bootpc > 255.255.255.2= 55.bootps: [udp sum ok] BOOTP/DHCP, Request from 32:62:65:61:65:33 (oui Unk= nown), length 300, xid 0x9efc4849, secs 94, Flags [none] (0x0000)<o:p></o:p= >         &nbs= p; Client-Ethernet-Address 32:62:65:61:65:33 (oui Unknown)  &nbsp= ;  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<o:p></o:p>         &nbs= p; Vendor-rfc1048 Extensions<o:p></o:p>         &nbs= p;   Magic Cookie 0x63825363<o:p></o:p>         &nbs= p;   DHCP-Message Option 53, length 1: Discover<o:p></o:p>         &nbs= p;   Hostname Option 12, length 5: "test1"<o:p></o:p></= p>          &nb= sp;  Parameter-Request Option 55, length 13:<o:p></o:p>         &nbs= p;     Subnet-Mask, BR, Time-Zone, Default-Gateway<o:p>= </o:p>         &nbs= p;     Domain-Name, Domain-Name-Server, Option 119, Hos= tname<o:p></o:p>         &nbs= p;     Netbios-Name-Server, Netbios-Scope, MTU, Classle= ss-Static-Route<o:p></o:p>          &nb= sp;    NTP<o:p></o:p>         &nbs= p;   END Option 255, length 0<o:p></o:p>         &nbs= p;   PAD Option 0, length 0, occurs 34<o:p></o:p> <o:p> </o:p> <o:p> </o:p> [root@ovirt-node-03 ~]# brctl showmacs 207-net<o:p><= /o:p> port no mac addr      =           is local? &nbsp= ;     ageing timer<o:p></o:p>   1     00:15:17:7b:e9:da&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   1     00:15:17:7b:e9:da&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   3     00:1a:4a:16:01:56&n= bsp;      no      &n= bsp;          0.11 <o:p> </o:p>   2     00:1a:4a:16:01= :57       no     &nb= sp;           0.13  = << Proxmox VM's eth0 MAC learned<o:p></o:p>   1     00:24:50:dd:a2:05&n= bsp;      no      &n= bsp;          1.05<o:p></o:p><= /p>   1     18:03:73:e3:be:5a&n= bsp;      no      &n= bsp;        198.87<o:p></o:p>   1     18:03:73:e3:ca:24&n= bsp;      no      &n= bsp;         60.01<o:p></o:p>   1     18:03:73:e3:cb:5b&n= bsp;      no      &n= bsp;         68.26<o:p></o:p>   1     18:03:73:e3:cd:b8&n= bsp;      no      &n= bsp;         41.39<o:p></o:p>   1     18:03:73:e3:d4:26&n= bsp;      no      &n= bsp;         57.25<o:p></o:p>   1     18:03:73:e3:d5:3d&n= bsp;      no      &n= bsp;        133.53<o:p></o:p>   1     18:03:73:e4:23:08&n= bsp;      no      &n= bsp;         34.28<o:p></o:p>   1     18:03:73:e4:26:2f&n= bsp;      no      &n= bsp;         20.10<o:p></o:p>   1     18:03:73:e4:2b:4c&n= bsp;      no      &n= bsp;         22.49<o:p></o:p>   1     18:03:73:e4:6c:19&n= bsp;      no      &n= bsp;         14.87<o:p></o:p>   1     18:03:73:e4:7e:0a&n= bsp;      no      &n= bsp;         54.46<o:p></o:p>   1     18:03:73:e8:16:e0&n= bsp;      no       &= nbsp;        28.71<o:p></o:p>   1     34:17:eb:9b:f8:ea&n= bsp;      no      &n= bsp;         22.49<o:p></o:p>   1     44:d3:ca:7e:3c:ff&n= bsp;      no      &n= bsp;          0.60<o:p></o:p><= /p>   1     78:2b:cb:3b:ca:b9&n= bsp;      no      &n= bsp;        217.66<o:p></o:p>   1     78:2b:cb:92:cb:cb&n= bsp;      no      &n= bsp;        194.18<o:p></o:p>   1     78:2b:cb:93:08:a8&n= bsp;      no      &n= bsp;        102.49<o:p></o:p>   1     b8:ca:3a:7a:70:63&n= bsp;      no      &n= bsp;          4.19<o:p></o:p><= /p>   1     f8:bc:12:69:bb:a3&n= bsp;      no      &n= bsp;        110.52<o:p></o:p>   3     fe:1a:4a:16:01:56&n= bsp;      yes      &= nbsp;         0.00  <<&l= t; veth connection to Proxmox VM (veth0)<o:p></o:p>   3     fe:1a:4a:16:01:56&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   2     fe:1a:4a:16:01:57&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p>   2     fe:1a:4a:16:01:57&n= bsp;      yes      &= nbsp;         0.00<o:p></o:p> (notice no other entries for port 3 – should b= e learning MAC 32:62:65:61:65:33 from incoming traffic on vnet0)<o:p></o:p>= <o:p> </o:p> =3D=3D=3D=3D=3D<o:p></o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html> --_000_F3282EEAFF180F43BAF1AD0A7C34739D3DA20Enjmailneclabscom_--

1 0

a new CLI for oVirt
by Fabrice Bacchella 06 May '16

06 May '16

--Apple-Mail=_62AEA0E7-D58F-45F5-A309-BE84C8F41136 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii To try to learn the python SDK, and help the automation of my setup, I = wrote a CLI to oVirt. It tries to hide some of the complexity, so some simple python script = like : dc =3D context.datacenter(name=3D"dc1") if dc is not None: dc.delete(force=3DTrue) context.datacenter().create(name=3D"dc1", local=3DFalse, = storage_format=3D"v3", mac_pool_name=3D"MoreMac") cluster =3D context.cluster(name=3D"cl1") if cluster is not None: cluster.delete(force=3DTrue) context.cluster().create(name=3D"cl1", cpu_type=3D"Intel Haswell-noTSX = Family", dc_name=3D"en02", memory_policy=3D{'guaranteed': True, = 'overcommit': 100, 'transparent_hugepages': False}, ballooning_enabled=3DTrue) can be used. It avoid the use of params.Something. It can also be used to do action in shell like : ./ovcmd -c ovirt.ini host -n host1 bond -i eth0 -i eth1 -n ovirtmgmt -o = mode 4 -o miimon 100 -o xmit_hash_policy 2+3 -D -m 9000 or ./ovcmd -c ovirt.ini host -n host1 export nics Complex commands can take template as an argument : ./ovcmd -d -c ovirt.ini vm create -T vm1.yaml -V cores 2 -V memory 4G -n = vm1 It's of course on github : https://github.com/fbacchella/ovirtcmd = <https://github.com/fbacchella/ovirtcmd> It's still a work in progress, only the very basic commands are = implemented, I will add other as requested, it should be easy to do so.= --Apple-Mail=_62AEA0E7-D58F-45F5-A309-BE84C8F41136 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space;" class=3D"">To try to learn the = python SDK, and help the automation of my setup, I wrote a CLI to = oVirt. It tries to hide some of the = complexity, so some simple python script like : dc =3D = context.datacenter(name=3D"dc1") if dc is = not None:     dc.delete(force=3DTrue) context.datacenter().create(name=3D"dc1", local=3DFalse, storage_format=3D"v3", mac_poo= l_name=3D"MoreMac") cluster =3D = context.cluster(name=3D"cl1") if cluster is = not None:     cluster.delete(force=3DTrue)<br= class=3D"">context.cluster().create(name=3D"cl1", cpu_type=3D"Intel Haswell-noTSX = Family", dc_name=3D"en02",       =                   =  memory_policy=3D{'guaranteed': True, 'overcommit': 10= 0, 'transparent_hugepages': False},   =                     =    ballooning_enabled=3DTrue) <div class=3D"">can be used. It avoid the use of = params.Something.</div><div class=3D""> </div><div = class=3D"">It can also be used to do action in shell like :</div><div = class=3D""> </div><div class=3D""><div style=3D"margin: = 0px; font-family: Menlo;" class=3D"">./ovcmd -c ovirt.ini host -n host1 = bond -i eth0 -i eth1 -n ovirtmgmt -o mode 4 -o miimon 100 -o = xmit_hash_policy 2+3 -D -m 9000</div></div><div style=3D"margin: 0px;" = class=3D""> </div><div style=3D"margin: 0px;" = class=3D"">or</div><div style=3D"margin: 0px;" class=3D""> </div><div style=3D"margin: 0px; font-family: Menlo;" = class=3D"">./ovcmd -c ovirt.ini host -n host1 export nics</div><div = style=3D"margin: 0px; font-family: Menlo;" class=3D""> </div><div style=3D"margin: 0px;" class=3D"">Complex commands = can take template as an argument :</div><div style=3D"margin: 0px;" = class=3D""> </div><div style=3D"margin: 0px;" = class=3D""><div style=3D"margin: 0px; font-family: Menlo;" = class=3D"">./ovcmd -d -c ovirt.ini vm create -T vm1.yaml -V = cores 2 -V memory 4G -n vm1</div><div style=3D"margin: 0px;" = class=3D""> </div><div style=3D"margin: 0px;" = class=3D"">It's of course on github :</div><div style=3D"margin: 0px;" = class=3D""><a href=3D"https://github.com/fbacchella/ovirtcmd" = class=3D"">https://github.com/fbacchella/ovirtcmd</a></div><div = style=3D"margin: 0px;" class=3D""> </div><div = style=3D"margin: 0px;" class=3D"">It's still a work in progress, only = the very basic commands are implemented, I will add other as requested, = it should be easy to do so.</div></div></body></html>= --Apple-Mail=_62AEA0E7-D58F-45F5-A309-BE84C8F41136--

1 0

Restart VMs after failure
by Chris Adams 06 May '16

06 May '16

One of my oVirt clusters, running 3.6.5, lost power last night (power failure plus bad UPS batteries - batteries on order!). When power came back, the storage and nodes came back, and then the hosted engine started, but nothing else happened (no other VMs started). I expected that VMs that were running when the power failed would have been restarted once the engine came back up. Is there a way to make that happen? -- Chris Adams <cma(a)cmadams.net>

2 2

Need help in starting a vm using vdsClient
by knarra 06 May '16

06 May '16

Hi All, I want to write a script to poweroff vms and start vms in a loop for my testing. I found the command to poweroff the vms by looking at the vdsClient -h, but can some one help me how to start the powered off vm using vdsClient command ?? Thanks kasturi.

2 2

Re: [ovirt-users] Hosted engine on iscsi storage
by Simone Tiraboschi 05 May '16

05 May '16

On Thu, May 5, 2016 at 2:35 PM, Darran Carey <darran.carey(a)pawsey.org.au> wrote: > Hi Simone, > > Please find the log files attached. Thank you very much for taking the time > to look at this problem. > > Regards, > Darran. Indeed VDSM is returning an empty device list: Thread-17518::DEBUG::2016-05-05 16:05:05,409::task::595::Storage.TaskManager.Task::(_updateState) Task=`6e96b9df-b656-45bd-899b-c94ec9be5c52`::moving from state init -> state preparing Thread-17518::INFO::2016-05-05 16:05:05,410::logUtils::48::dispatcher::(wrapper) Run and protect: getDeviceList(storageType=3, guids=(), checkStatus=True, options={}) Thread-17518::DEBUG::2016-05-05 16:05:05,410::misc::750::Storage.SamplingMethod::(__call__) Trying to enter sampling method (storage.sdc.refreshStorage) Thread-17518::DEBUG::2016-05-05 16:05:05,411::misc::753::Storage.SamplingMethod::(__call__) Got in to sampling method Thread-17518::DEBUG::2016-05-05 16:05:05,411::misc::750::Storage.SamplingMethod::(__call__) Trying to enter sampling method (storage.iscsi.rescan) Thread-17518::DEBUG::2016-05-05 16:05:05,411::misc::753::Storage.SamplingMethod::(__call__) Got in to sampling method Thread-17518::DEBUG::2016-05-05 16:05:05,412::iscsi::434::Storage.ISCSI::(rescan) Performing SCSI scan, this will take up to 30 seconds Thread-17518::DEBUG::2016-05-05 16:05:05,413::iscsiadm::97::Storage.Misc.excCmd::(_runCmd) /usr/bin/taskset --cpu-list 0-7 /usr/bin/sudo -n /sbin/iscsiadm -m session -R (cwd None) Thread-17518::DEBUG::2016-05-05 16:05:05,463::misc::760::Storage.SamplingMethod::(__call__) Returning last result Thread-17518::DEBUG::2016-05-05 16:05:05,464::misc::750::Storage.SamplingMethod::(__call__) Trying to enter sampling method (storage.hba.rescan) Thread-17518::DEBUG::2016-05-05 16:05:05,464::misc::753::Storage.SamplingMethod::(__call__) Got in to sampling method Thread-17518::DEBUG::2016-05-05 16:05:05,464::hba::56::Storage.HBA::(rescan) Starting scan Thread-17518::DEBUG::2016-05-05 16:05:05,661::hba::62::Storage.HBA::(rescan) Scan finished Thread-17518::DEBUG::2016-05-05 16:05:05,662::misc::760::Storage.SamplingMethod::(__call__) Returning last result Thread-17518::DEBUG::2016-05-05 16:05:05,662::multipath::77::Storage.Misc.excCmd::(rescan) /usr/bin/taskset --cpu-list 0-7 /usr/bin/sudo -n /usr/sbin/multipath (cwd None) Thread-17518::DEBUG::2016-05-05 16:05:05,747::multipath::77::Storage.Misc.excCmd::(rescan) SUCCESS: <err> = ''; <rc> = 0 Thread-17518::DEBUG::2016-05-05 16:05:05,748::utils::671::root::(execCmd) /usr/bin/taskset --cpu-list 0-7 /sbin/udevadm settle --timeout=5 (cwd None) Thread-17518::DEBUG::2016-05-05 16:05:05,768::utils::689::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 Thread-17518::DEBUG::2016-05-05 16:05:05,771::lvm::497::Storage.OperationMutex::(_invalidateAllPvs) Operation 'lvm invalidate operation' got the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,772::lvm::499::Storage.OperationMutex::(_invalidateAllPvs) Operation 'lvm invalidate operation' released the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,772::lvm::508::Storage.OperationMutex::(_invalidateAllVgs) Operation 'lvm invalidate operation' got the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,773::lvm::510::Storage.OperationMutex::(_invalidateAllVgs) Operation 'lvm invalidate operation' released the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,773::lvm::528::Storage.OperationMutex::(_invalidateAllLvs) Operation 'lvm invalidate operation' got the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,774::lvm::530::Storage.OperationMutex::(_invalidateAllLvs) Operation 'lvm invalidate operation' released the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,774::misc::760::Storage.SamplingMethod::(__call__) Returning last result Thread-17518::DEBUG::2016-05-05 16:05:05,775::lvm::319::Storage.OperationMutex::(_reloadpvs) Operation 'lvm reload operation' got the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:05,777::lvm::290::Storage.Misc.excCmd::(cmd) /usr/bin/taskset --cpu-list 0-7 /usr/bin/sudo -n /usr/sbin/lvm pvs --config ' devices { preferred_names = ["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ '\''r|.*|'\'' ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } ' --noheadings --units b --nosuffix --separator '|' --ignoreskippedcluster -o uuid,name,size,vg_name,vg_uuid,pe_start,pe_count,pe_alloc_count,mda_count,dev_size (cwd None) Thread-17518::DEBUG::2016-05-05 16:05:05,987::lvm::290::Storage.Misc.excCmd::(cmd) SUCCESS: <err> = ' WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!\n'; <rc> = 0 Thread-17518::DEBUG::2016-05-05 16:05:05,987::lvm::347::Storage.OperationMutex::(_reloadpvs) Operation 'lvm reload operation' released the operation mutex Thread-17518::DEBUG::2016-05-05 16:05:06,003::lvm::290::Storage.Misc.excCmd::(cmd) /usr/bin/taskset --cpu-list 0-7 /usr/bin/sudo -n /usr/sbin/lvm pvcreate --config ' devices { preferred_names = ["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ '\''r|.*|'\'' ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } ' --test --metadatasize 128m --metadatacopies 2 --metadataignore y (cwd None) Thread-17518::DEBUG::2016-05-05 16:05:06,054::lvm::290::Storage.Misc.excCmd::(cmd) FAILED: <err> = " WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!\n TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.\n Please enter a physical volume path.\n Run `pvcreate --help' for more information.\n"; <rc> = 3 Thread-17518::DEBUG::2016-05-05 16:05:06,056::lvm::864::Storage.LVM::(testPVCreate) rc: 3, out: [], err: [' WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!', ' TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.', ' Please enter a physical volume path.', " Run `pvcreate --help' for more information."], unusedDevs: set([]), usedDevs: set([]) Thread-17518::INFO::2016-05-05 16:05:06,056::logUtils::51::dispatcher::(wrapper) Run and protect: getDeviceList, Return response: {'devList': []} Thread-17518::DEBUG::2016-05-05 16:05:06,057::task::1191::Storage.TaskManager.Task::(prepare) Task=`6e96b9df-b656-45bd-899b-c94ec9be5c52`::finished: {'devList': []} Thread-17518::DEBUG::2016-05-05 16:05:06,057::task::595::Storage.TaskManager.Task::(_updateState) Task=`6e96b9df-b656-45bd-899b-c94ec9be5c52`::moving from state preparing -> state finished You can check the initiator name used by VDSM with vdsClient -s 0 getVdsCaps | grep ISCSIInitiatorName Can you please check if you correctly configured ACLs for that initiator? > On 2016-05-05 17:06, Simone Tiraboschi wrote: >> >> On Thu, May 5, 2016 at 10:22 AM, Darran Carey >> <darran.carey(a)pawsey.org.au> wrote: >>> >>> Hi All, >>> >>> I am trying to install the hosted engine on an iscsi target but get the >>> following error: >>> >>> [root@virt-host01 ~]# hosted-engine --deploy >>> ... >>> --== STORAGE CONFIGURATION ==-- >>> >>> During customization use CTRL-D to abort. >>> Please specify the storage you would like to use (glusterfs, >>> iscsi, fc, nfs3, nfs4)[nfs3]: iscsi >>> Please specify the iSCSI portal IP address: 10.43.0.100 >>> Please specify the iSCSI portal port [3260]: >>> Please specify the iSCSI portal user: >>> Please specify the target name >>> >>> (iqn.2001-05.com.equallogic:0-8a0906-8bb896109-6060000000b57145-iscsi-vol-01) >>> >>> [iqn.2001-05.com.equallogic:0-8a0906-8bb896109-6060000000b57145-iscsi-vol-01]: >>> [ INFO ] Discovering iSCSI node >>> [ INFO ] Connecting to the storage server >>> [ INFO ] Discovering iSCSI node >>> [ INFO ] Connecting to the storage server >>> [ ERROR ] Failed to execute stage 'Environment customization': Unable to >>> retrieve the list of LUN(s) please check the SELinux log and settings on >>> your iscsi target >>> >>> >>> The relevant excerpt from the log file is: >>> >>> 2016-05-05 16:05:09 DEBUG otopi.context context._executeMethod:156 method >>> exception >>> Traceback (most recent call last): >>> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in >>> _executeMethod >>> method['method']() >>> File >>> >>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", >>> line 591, in _customization >>> lunGUID = self._customize_lun(self.domainType, target) >>> File >>> >>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", >>> line 209, in _customize_lun >>> iqn=target, >>> File >>> >>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", >>> line 374, in _iscsi_get_lun_list >>> raise RuntimeError("Unable to retrieve the list of LUN(s) please " >>> RuntimeError: Unable to retrieve the list of LUN(s) please check the >>> SELinux >>> log and settings on your iscsi target >>> 2016-05-05 16:05:09 ERROR otopi.context context._executeMethod:165 Failed >>> to >>> execute stage 'Environment customization': Unable to retrieve the list of >>> LUN(s) please check the SELinux log and settings on your iscsi target >> >> >> Can you please attach the whole hosted-engine-setup log file and vdsm >> logs? >> >>> This is on CentOS 7 with ovirt 3.6. >>> selinux is disabled. >>> >>> I can mount the iscsi target fine using iscsiadm or the Dell Equallogic >>> Host >>> Integration Toolkit commands. >>> >>> I think the first problem is the call to self.cli.getDeviceList in >>> blockd.py >>> is returning an empty list, but I don't know what that function is >>> actually >>> doing. >>> >>> Has anyone experienced similar behaviour or has any suggestions as to >>> what I >>> should check next? >>> >>> Thanks, >>> Darran. >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users

2 2

node unresponsive after reboot
by Cam Mac 05 May '16

05 May '16

Hi, I have a two node + engine ovirt setup, and I was having problems doing a live migration between nodes. I looked in the vdsm logs and noticed selinux errors, so I checked the selinux config, and both the ovirt-engine host and one of the nodes had selinux disabled. So I thought I would enable it on these two hosts, as it is officially supported anyway. I started with the node, and put it into maintenance mode, which interestingly, migrated the VMs off to the other node without issue. After modifying the selinux config, I then rebooted that node, which came back up. I then tried to activate the node but it fails and marks it as unresponsive. ----------8<---------- 2016-04-28 16:34:31,326 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [29acb18b] Connecting to kvm-ldn-02/172.16.23.12 2016-04-28 16:34:31,327 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-32) [ac322cb] Command 'GetCapabilitiesVDSCommand(HostName = kvm-ldn-02, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='b12c0b80-d64d-42fd-8a55-94f92b9ca3aa', vds='Host[kvm-ldn-02,b12c0b80-d64d-42fd-8a55-94f92b9ca3aa]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed 2016-04-28 16:34:31,327 ERROR [org.ovirt.engine.core.vdsbroker.HostMonitoring] (DefaultQuartzScheduler_Worker-32) [ac322cb] Failure to refresh Vds runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed 2016-04-28 16:34:31,327 ERROR [org.ovirt.engine.core.vdsbroker.HostMonitoring] (DefaultQuartzScheduler_Worker-32) [ac322cb] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:157) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:120) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:467) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:652) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.HostMonitoring.refreshVdsRunTimeInfo(HostMonitoring.java:119) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.HostMonitoring.refresh(HostMonitoring.java:84) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.onTimer(VdsManager.java:227) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source) [:1.8.0_71] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_71] at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_71] at org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:81) [scheduler.jar:] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:52) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:] Caused by: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed at org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient.connect(ReactorClient.java:157) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.getClient(JsonRpcClient.java:114) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.vdsm.jsonrpc.client.JsonRpcClient.call(JsonRpcClient.java:73) [vdsm-jsonrpc-java-client.jar:] at org.ovirt.engine.core.vdsbroker.jsonrpc.FutureMap.<init>(FutureMap.java:68) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.jsonrpc.JsonRpcVdsServer.getCapabilities(JsonRpcVdsServer.java:268) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand.executeVdsBrokerCommand(GetCapabilitiesVDSCommand.java:15) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110) [vdsbroker.jar:] ... 14 more ----------8<---------- Any ideas? Thanks for any help, Cam

3 5

Prepare for version 4 of oVirt API
by Juan Hernández 05 May '16

05 May '16

Hello all, For those of you that use oVirt API, I wanted to inform you that version 4 of oVirt will by default use a new version of the API, incompatible with the previous one. The previous version will still be supported, but only for clients that explicitly send the "Version: 3" header, as described here: https://github.com/oVirt/ovirt-engine/tree/master/backend/manager/modules/r… If you are aware of any piece of software that uses the oVirt API, please let me know, so that we can inform the authors. Thanks in advance, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

3 3

Stale VM template
by Bhaskarakiran 05 May '16

05 May '16

Hi, I was trying to make a template of RHEL7.2 VM from GUI (hosted engine) and the status shows "Image Locked" for a very long time now. Tried restarting ovirt-engine and didn't help. Can someone let me know how do i cancel that operation. Thanks, Bhaskarkairan.

2 2

Hosted engine on iscsi storage
by Darran Carey 05 May '16

05 May '16

Hi All, I am trying to install the hosted engine on an iscsi target but get the following error: [root@virt-host01 ~]# hosted-engine --deploy ... --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: iscsi Please specify the iSCSI portal IP address: 10.43.0.100 Please specify the iSCSI portal port [3260]: Please specify the iSCSI portal user: Please specify the target name (iqn.2001-05.com.equallogic:0-8a0906-8bb896109-6060000000b57145-iscsi-vol-01) [iqn.2001-05.com.equallogic:0-8a0906-8bb896109-6060000000b57145-iscsi-vol-01]: [ INFO ] Discovering iSCSI node [ INFO ] Connecting to the storage server [ INFO ] Discovering iSCSI node [ INFO ] Connecting to the storage server [ ERROR ] Failed to execute stage 'Environment customization': Unable to retrieve the list of LUN(s) please check the SELinux log and settings on your iscsi target The relevant excerpt from the log file is: 2016-05-05 16:05:09 DEBUG otopi.context context._executeMethod:156 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", line 591, in _customization lunGUID = self._customize_lun(self.domainType, target) File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", line 209, in _customize_lun iqn=target, File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/blockd.py", line 374, in _iscsi_get_lun_list raise RuntimeError("Unable to retrieve the list of LUN(s) please " RuntimeError: Unable to retrieve the list of LUN(s) please check the SELinux log and settings on your iscsi target 2016-05-05 16:05:09 ERROR otopi.context context._executeMethod:165 Failed to execute stage 'Environment customization': Unable to retrieve the list of LUN(s) please check the SELinux log and settings on your iscsi target This is on CentOS 7 with ovirt 3.6. selinux is disabled. I can mount the iscsi target fine using iscsiadm or the Dell Equallogic Host Integration Toolkit commands. I think the first problem is the call to self.cli.getDeviceList in blockd.py is returning an empty list, but I don't know what that function is actually doing. Has anyone experienced similar behaviour or has any suggestions as to what I should check next? Thanks, Darran.

2 1

[hosted-engine] engine VM doesn't respawn when its host was killed (poweroff)
by Wee Sritippho 04 May '16

04 May '16

Hi, From the hosted-engine FAQ, the engine VM should be up and running in about 5 minutes after its host was forced poweroff. However, after updated oVirt 3.6.4 to 3.6.5, the engine VM won't restart automatically even after 10+ minutes (I already made sure that global maintenance mode is set to none). I initially thought its a time sync issue, so I installed and enabled ntp on the hosts and engine. However, the issue still persists. ###Versions: [root@host01 ~]# rpm -qa | grep ovirt libgovirt-0.3.3-1.el7_2.1.x86_64 ovirt-vmconsole-1.0.0-1.el7.centos.noarch ovirt-vmconsole-host-1.0.0-1.el7.centos.noarch ovirt-hosted-engine-ha-1.3.5.3-1.el7.centos.noarch ovirt-host-deploy-1.4.1-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.5.0-1.el7.centos.noarch ovirt-hosted-engine-setup-1.3.5.0-1.el7.centos.noarch ovirt-release36-007-1.noarch ovirt-setup-lib-1.0.1-1.el7.centos.noarch [root@host01 ~]# rpm -qa | grep vdsm vdsm-infra-4.17.26-0.el7.centos.noarch vdsm-jsonrpc-4.17.26-0.el7.centos.noarch vdsm-gluster-4.17.26-0.el7.centos.noarch vdsm-python-4.17.26-0.el7.centos.noarch vdsm-yajsonrpc-4.17.26-0.el7.centos.noarch vdsm-4.17.26-0.el7.centos.noarch vdsm-cli-4.17.26-0.el7.centos.noarch vdsm-xmlrpc-4.17.26-0.el7.centos.noarch vdsm-hook-vmfex-dev-4.17.26-0.el7.centos.noarch ###Log files: https://app.box.com/s/fkurmwagogwkv5smkwwq7i4ztmwf9q9r ###After host02 was killed: [root@host03 wees]# hosted-engine --vm-status --== Host 1 status ==-- Status up-to-date : True Hostname : host01.ovirt.forest.go.th Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 396766e0 Host timestamp : 4391 --== Host 2 status ==-- Status up-to-date : True Hostname : host02.ovirt.forest.go.th Host ID : 2 Engine status : {"health": "good", "vm": "up", "detail": "up"} Score : 0 stopped : True Local maintenance : False crc32 : 3a345b65 Host timestamp : 1458 --== Host 3 status ==-- Status up-to-date : True Hostname : host03.ovirt.forest.go.th Host ID : 3 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 4c34b0ed Host timestamp : 11958 ###After host02 was killed for a while: [root@host03 wees]# hosted-engine --vm-status --== Host 1 status ==-- Status up-to-date : False Hostname : host01.ovirt.forest.go.th Host ID : 1 Engine status : unknown stale-data Score : 3400 stopped : False Local maintenance : False crc32 : 72e4e418 Host timestamp : 4415 --== Host 2 status ==-- Status up-to-date : False Hostname : host02.ovirt.forest.go.th Host ID : 2 Engine status : unknown stale-data Score : 0 stopped : True Local maintenance : False crc32 : 3a345b65 Host timestamp : 1458 --== Host 3 status ==-- Status up-to-date : False Hostname : host03.ovirt.forest.go.th Host ID : 3 Engine status : unknown stale-data Score : 3400 stopped : False Local maintenance : False crc32 : 4c34b0ed Host timestamp : 11958 ###After host02 was up again completely: [root@host03 wees]# hosted-engine --vm-status --== Host 1 status ==-- Status up-to-date : True Hostname : host01.ovirt.forest.go.th Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 0 stopped : False Local maintenance : False crc32 : f5728fca Host timestamp : 5555 --== Host 2 status ==-- Status up-to-date : True Hostname : host02.ovirt.forest.go.th Host ID : 2 Engine status : {"health": "good", "vm": "up", "detail": "up"} Score : 3400 stopped : False Local maintenance : False crc32 : e5284763 Host timestamp : 715 --== Host 3 status ==-- Status up-to-date : True Hostname : host03.ovirt.forest.go.th Host ID : 3 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : bc10c7fc Host timestamp : 13119 -- Wee

3 6