- Users - oVirt List Archives

Gluster deployment - Arbiter volume - different disk size - volumes sizes
by florentl 12 Sep '18

12 Sep '18

Hello, I have one more question for the gluster deployment. I have three servers with different disk sizes : - server1 : 3 x SSD configured in raid 5 mode for a total capacity of 900 GB - server2 : 6 x SSD configurerd in raid 6 mode for a total capacity of 2,2 TB - server3 : same as server2 (2,2TB) Because my server1 has less capacity than the others I will use it as an arbiter volume (during the deployment I will declare it as the last host : host3). Is-it correct ? So I will create 4 volumes : - engine : 50 GB type replicated without arbiter - data : ?? - vmstore : ??? - iso : 15 GB replicated with arbiter volume Can someone tell me what are the differences between data and vmstore volume ? In the earlier version there was only information about data volume and export volume. I found nothing about vmstore volume. If the wmstore is, as its name suggests, the place where all vm files will be stored including vm disks images, I think I have to set most of the capacity for this volume. So at the end my 4 volumes will be : - engine : 50 GB type replicated without arbiter - data : 500 TB replicated with arbiter volume - vmstore : 1,5 TB replicated with arbiter volume - iso : 15 GB replicated with arbiter volume What do you think of this ? Thanks, Florent

4 3

vm with disks on multiple glusterfs domains fails if a gluster host goes down
by g.vasilopoulos＠uoc.gr 12 Sep '18

12 Sep '18

It seems that a vm with 3 disks boot in domain engine another disk in domain vol1 and a third in domain v3 became non responsive when one gluster host went down. To explain a bit the situation I have 3 glusterfs hosts with 3 volumes hosts are g1,g2,g3 each have 3 bricks g1 has vol1,vol2 and vol3 arbiter g2 has vol1, vol2arbiter and vol3 g3 has vol1arb vol2 and vol3 libgfapi is enabled . I put a host in maintenance to update the bios and the vm who had disks in two domain became unresponsive.. is this normal? qemu logs showing that it tries Domain configuration shows host1 as primary for vol1 and host2 as primary for vol3 with the other two as backup-volfile servers.. it seems it always try to connect to the server that is down and not to one of the alternative hosts... is this libgapi/libvirt problem ? Here are some libvirt logs showing what it tries to do.. [2018-09-10 19:43:42.876114] T [socket.c:3133:socket_connect] 0-vol1-client-2: connecting 0x55ed673525c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:42.876124] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol1-client-2: option remote-port missing in volume vol1-client-2. Defaulting to 24007 [2018-09-10 19:43:42.878566] D [socket.c:3051:socket_fix_ssl_opts] 0-vol1-client-2: disabling SSL for portmapper connection [2018-09-10 19:43:42.878770] T [socket.c:834:__socket_nodelay] 0-vol1-client-2: NODELAY enabled for socket 30 [2018-09-10 19:43:42.878780] T [socket.c:920:__socket_keepalive] 0-vol1-client-2: Keep-alive enabled for socket: 30, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:42.878830] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol3-client-1: attempting reconnect [2018-09-10 19:43:42.878846] T [socket.c:3133:socket_connect] 0-vol3-client-1: connecting 0x55ed673546c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:42.878856] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol3-client-1: option remote-port missing in volume vol3-client-1. Defaulting to 24007 [2018-09-10 19:43:42.881229] D [socket.c:3051:socket_fix_ssl_opts] 0-vol3-client-1: disabling SSL for portmapper connection [2018-09-10 19:43:42.881255] T [socket.c:834:__socket_nodelay] 0-vol3-client-1: NODELAY enabled for socket 38 [2018-09-10 19:43:42.881264] T [socket.c:920:__socket_keepalive] 0-vol3-client-1: Keep-alive enabled for socket: 38, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:45.569298] T [socket.c:724:__socket_disconnect] 0-vol3-client-1: disconnecting 0x55ed673546c0, state=2 gen=0 sock=38 [2018-09-10 19:43:45.569308] T [socket.c:724:__socket_disconnect] 0-vol1-client-2: disconnecting 0x55ed673525c0, state=2 gen=0 sock=30 [2018-09-10 19:43:45.570000] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-t ransport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/s ocket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol3-client-1: tearing down socket connection [2018-09-10 19:43:45.570020] D [socket.c:686:__socket_shutdown] 0-vol3-client-1: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:45.570038] D [socket.c:733:__socket_disconnect] 0-vol3-client-1: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:45.570043] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:45.570907] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-t ransport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/s ocket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol1-client-2: tearing down socket connection [2018-09-10 19:43:45.570928] D [socket.c:686:__socket_shutdown] 0-vol1-client-2: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:45.570936] D [socket.c:733:__socket_disconnect] 0-vol1-client-2: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:45.570940] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:45.570960] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrp c.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_no tify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:45.571098] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrp c.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_no tify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:45.878885] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol1-client-2: attempting reconnect [2018-09-10 19:43:45.881546] T [socket.c:834:__socket_nodelay] 0-vol1-client-2: NODELAY enabled for socket 38 [2018-09-10 19:43:45.881555] T [socket.c:920:__socket_keepalive] 0-vol1-client-2: Keep-alive enabled for socket: 38, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:45.883839] D [socket.c:3051:socket_fix_ssl_opts] 0-vol3-client-1: disabling SSL for portmapper connection [2018-09-10 19:43:45.883878] T [socket.c:834:__socket_nodelay] 0-vol3-client-1: NODELAY enabled for socket 30 [2018-09-10 19:43:45.883886] T [socket.c:920:__socket_keepalive] 0-vol3-client-1: Keep-alive enabled for socket: 30, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:48.575316] T [socket.c:724:__socket_disconnect] 0-vol3-client-1: disconnecting 0x55ed673546c0, state=2 gen=0 sock=30 [2018-09-10 19:43:48.575329] T [socket.c:724:__socket_disconnect] 0-vol1-client-2: disconnecting 0x55ed673525c0, state=2 gen=0 sock=38 [2018-09-10 19:43:48.576022] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol3-client-1: tearing down socket connection [2018-09-10 19:43:48.576045] D [socket.c:686:__socket_shutdown] 0-vol3-client-1: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:48.576054] D [socket.c:733:__socket_disconnect] 0-vol3-client-1: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:48.576059] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:48.576079] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol1-client-2: tearing down socket connection [2018-09-10 19:43:48.576099] D [socket.c:686:__socket_shutdown] 0-vol1-client-2: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:48.576106] D [socket.c:733:__socket_disconnect] 0-vol1-client-2: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:48.576111] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:48.576879] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrpc.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:48.576958] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrpc.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:48.881651] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol1-client-2: attempting reconnect [2018-09-10 19:43:48.881667] T [socket.c:3133:socket_connect] 0-vol1-client-2: connecting 0x55ed673525c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:48.881689] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol1-client-2: option remote-port missing in volume vol1-client-2. Defaulting to 24007 [2018-09-10 19:43:48.884056] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol3-client-1: attempting reconnect [2018-09-10 19:43:48.884072] T [socket.c:3133:socket_connect] 0-vol3-client-1: connecting 0x55ed673546c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:48.884084] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol3-client-1: option remote-port missing in volume vol3-client-1. Defaulting to 24007 [2018-09-10 19:43:48.884190] D [socket.c:3051:socket_fix_ssl_opts] 0-vol1-client-2: disabling SSL for portmapper connection [2018-09-10 19:43:48.886524] T [socket.c:834:__socket_nodelay] 0-vol3-client-1: NODELAY enabled for socket 30 [2018-09-10 19:43:48.886532] T [socket.c:920:__socket_keepalive] 0-vol3-client-1: Keep-alive enabled for socket: 30, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:51.581293] T [socket.c:724:__socket_disconnect] 0-vol3-client-1: disconnecting 0x55ed673546c0, state=2 gen=0 sock=30 [2018-09-10 19:43:51.581293] T [socket.c:724:__socket_disconnect] 0-vol1-client-2: disconnecting 0x55ed673525c0, state=2 gen=0 sock=38 [2018-09-10 19:43:51.582009] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol1-client-2: tearing down socket connection [2018-09-10 19:43:51.582030] D [socket.c:686:__socket_shutdown] 0-vol1-client-2: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:51.582036] D [socket.c:733:__socket_disconnect] 0-vol1-client-2: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:51.582040] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:51.582084] T [socket.c:728:__socket_disconnect] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x4ea0)[0x7fdda7bbfea0] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x530a)[0x7fdda7bc030a] (--> /usr/lib64/glusterfs/3.12.13/rpc-transport/socket.so(+0x9a08)[0x7fdda7bc4a08] (--> /lib64/libglusterfs.so.0(+0x883c4)[0x7fddbae093c4] ))))) 0-vol3-client-1: tearing down socket connection [2018-09-10 19:43:51.582105] D [socket.c:686:__socket_shutdown] 0-vol3-client-1: shutdown() returned -1. Transport endpoint is not connected [2018-09-10 19:43:51.582111] D [socket.c:733:__socket_disconnect] 0-vol3-client-1: __socket_teardown_connection () failed: Transport endpoint is not connected [2018-09-10 19:43:51.582116] D [socket.c:2474:socket_event_handler] 0-transport: EPOLLERR - disconnecting now [2018-09-10 19:43:51.582812] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrpc.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:51.582865] D [rpc-clnt-ping.c:99:rpc_clnt_remove_ping_timer_locked] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fddbadade9b] (--> /lib64/libgfrpc.so.0(rpc_clnt_remove_ping_timer_locked+0x8b)[0x7fddbab7828b] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x5f)[0x7fddbab7460f] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x2a0)[0x7fddbab75130] (--> /lib64/libgfrpc.so.0(rpc_transport_notify+0x23)[0x7fddbab70ea3] ))))) 0-: 10.xxx.xxx.130:24007: ping timer event already removed [2018-09-10 19:43:51.884349] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol1-client-2: attempting reconnect [2018-09-10 19:43:51.884367] T [socket.c:3133:socket_connect] 0-vol1-client-2: connecting 0x55ed673525c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:51.884376] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol1-client-2: option remote-port missing in volume vol1-client-2. Defaulting to 24007 [2018-09-10 19:43:51.886644] T [rpc-clnt.c:406:rpc_clnt_reconnect] 0-vol3-client-1: attempting reconnect [2018-09-10 19:43:51.886659] T [socket.c:3133:socket_connect] 0-vol3-client-1: connecting 0x55ed673546c0, state=2 gen=0 sock=-1 [2018-09-10 19:43:51.886669] T [name.c:243:af_inet_client_get_remote_sockaddr] 0-vol3-client-1: option remote-port missing in volume vol3-client-1. Defaulting to 24007 [2018-09-10 19:43:51.887251] D [socket.c:3051:socket_fix_ssl_opts] 0-vol1-client-2: disabling SSL for portmapper connection [2018-09-10 19:43:51.887281] T [socket.c:834:__socket_nodelay] 0-vol1-client-2: NODELAY enabled for socket 38 [2018-09-10 19:43:51.887290] T [socket.c:920:__socket_keepalive] 0-vol1-client-2: Keep-alive enabled for socket: 38, (idle: 20, interval: 2, max-probes: 9, timeout: 0) [2018-09-10 19:43:51.889141] D [socket.c:3051:socket_fix_ssl_opts] 0-vol3-client-1: disabling SSL for portmapper connection :

2 4

Install failing at DNS resolution check (closing up).
by Kristian Petersen 12 Sep '18

12 Sep '18

I am trying to set up a small oVirt 4.2 cluster on CentOS with 2 hosts to do some testing with. I got the everything set up to the point where I am running the hosted-engine --deploy, but it fails with an error saying it was unable to resolve some host name or IP address (but it isn't very clear what one). I have tested on the same machine its ability resolve the hosts in the cluster both forward and reverse and they work fine with nslookup. That includes the DNS entry for the hosted-engine. I tried putting them all into the /etc/hosts files of each computer but it still fails at the same step. Thge log file it refers to does not seem very helpful. Maybe I'm just not sure what to look for. -- Kristian Petersen System Administrator BYU Dept. of Chemistry and Biochemistry

2 1

Question on gluster sharding maturity/stability
by Brian Sipos 12 Sep '18

12 Sep '18

I'm currently running oVirt 4.1 (with gluster 3.8.15) and as this is a cluster which has been upgraded from (I believe) oVirt 3.5 originally, the storage volumes use old "Optimize for Virt Store" configuration of not enabling sharding. I see now that the oVirt 4.1 "optimize" configuration does enable sharding, but I am a bit wary after seeing some horror stories from about a year ago about corruptions and data loss caused by sharding in earlier gluster versions. Is the gluster associated with oVirt 4.1 now at a stable point that I can and should trust sharding? I plan on doing some simple experimenting first, but I see a great benefit to balancing distributed-replicated volumes and for healing times and I would like to take advantage of these benefits now. Since the ovirt engine is now 'recommending' the use of sharding for disk store volumes, this leads me to believe that it is trusted by the oVirt crew. Does this seem accurate?

1 0

Info about procedure to shutdown hosted engine VM
by Gianluca Cecchi 12 Sep '18

12 Sep '18

Hello, I'm writing a workflow regarding operations to do in case of planned maintenance where one has to stop all hypervisors and so also hosted engine vm. At the moment I have imagined: - shutdown all VMs but Hosted Engine - put into maintenance and then shutdown all the hosts where Engine is not running, one by one - put environment in global maintenance Now the next step would be to shutdown Hosted Engine VM. As my workflow is for users not necessarily expert with Linux I was thinking what would be an alternate method in respect of direct connect via ssh as root user and run "shutdown -h now" on engine Is there anything I can do from gui of web admin portal or cockpit of the host where it is running? Can I for example select to shutdown engine vm from web admin UI with a certain delay in time so that I disconnect and wait? Or anything I can do from cockpit of the host? Of course I'm searching for a supported flow. Thanks in advance, Gianluca

2 5

Re: Failed to synchronize networks of Provider ovirt-provider-ovn
by Mail SET Inc. Group 12 Sep '18

12 Sep '18

Yes, i use same manual to change WebUI SSL. ovirt-ca-file= is a same SSL file which use WebUI. Yes, i restart ovirt-provider-ovn, i restart engine, i restart all what i can restart. Nothing... > 12 сент. 2018 г., в 16:11, Dominik Holler <dholler(a)redhat.com> написал(а): > > On Wed, 12 Sep 2018 14:23:54 +0300 > "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: > >> Ok! > > Not exactly, please use users(a)ovirt.org for such questions. > Other should benefit from this questions, too. > Please write the next mail to users(a)ovirt.org and keep me in CC. > >> What i did: >> >> 1) install oVirt «from box» (4.2.5.2-1.el7); >> 2) generate own ssl for my engine using my FreeIPA CA, Install it and > > What means "Install it"? You can use the doc from the following link > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > > Ensure that ovirt-ca-file= in > /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf > points to the correct file and ovirt-provider-ovn is restarted. > >> get tis issue; >> >> >> [root@engine ~]# tail -n 50 /var/log/ovirt-provider-ovn.log >> 2018-09-12 14:10:23,828 root [SSL: CERTIFICATE_VERIFY_FAILED] >> certificate verify failed (_ssl.c:579) Traceback (most recent call >> last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", >> line 133, in _handle_request method, path_parts, content >> File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", >> line 175, in handle_request return >> self.call_response_handler(handler, content, parameters) File >> "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in >> call_response_handler return response_handler(content, parameters) >> File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py", >> line 62, in post_tokens user_password=user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in >> create_token return auth.core.plugin.create_token(user_at_domain, >> user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line >> 48, in create_token timeout=self._timeout()) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75, >> in create_token username, password, engine_url, ca_file, timeout) >> File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line >> 91, in _get_sso_token timeout=timeout File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54, >> in wrapper response = func(*args, **kwargs) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47, >> in wrapper raise BadGateway(e) BadGateway: [SSL: >> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579) >> >> >> [root@engine ~]# tail -n 20 /var/log/ovirt-engine/engine.log >> 2018-09-12 14:10:23,773+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:10:23,778+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:10:23,836+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:10:23,837+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:14:12,477+03 INFO >> [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default >> task-6) [] User admin@internal successfully logged in with scopes: >> ovirt-app-admin ovirt-app-api ovirt-app-portal >> ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all >> ovirt-ext=token-info:authz-search >> ovirt-ext=token-info:public-authz-search >> ovirt-ext=token-info:validate ovirt-ext=token:password-access >> 2018-09-12 14:14:12,587+03 INFO >> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default >> task-6) [1bf1b763] Running command: CreateUserSessionCommand >> internal: false. 2018-09-12 14:14:12,628+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [1bf1b763] EVENT_ID: USER_VDC_LOGIN(30), User >> admin@internal-authz connecting from '10.0.3.61' using session >> 's8jAm7BUJGlicthm6yZBA3CUM8QpRdtwFaK3M/IppfhB3fHFB9gmNf0cAlbl1xIhcJ2WX+ww7e71Ri+MxJSsIg==' >> logged in. 2018-09-12 14:14:30,972+03 INFO >> [org.ovirt.engine.core.bll.provider.ImportProviderCertificateCommand] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] Running >> command: ImportProviderCertificateCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:30,982+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] EVENT_ID: >> PROVIDER_CERTIFICATE_IMPORTED(213), Certificate for provider >> ovirt-provider-ovn was imported. (User: admin@internal-authz) >> 2018-09-12 14:14:31,006+03 INFO >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Running >> command: TestProviderConnectivityCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:31,058+03 ERROR >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Command >> 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'default' is using 0 threads out of 1, 5 threads waiting for >> tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engine' is using 0 threads out of 500, 16 threads waiting for >> tasks and 0 tasks in queue. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineScheduled' is using 0 threads out of 100, 100 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineThreadMonitoring' is using 1 threads out of 1, 0 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'hostUpdatesChecker' is using 0 threads out of 5, 2 threads >> waiting for tasks. 2018-09-12 14:15:23,843+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:15:23,849+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:15:23,900+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:23,901+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' >> >> >> [root@engine ~]# >> cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf # >> This file is automatically generated by engine-setup. Please do not >> edit manually [OVN REMOTE] ovn-remote=ssl:127.0.0.1:6641 >> [SSL] >> https-enabled=true >> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >> [OVIRT] >> ovirt-sso-client-secret=Ms7Gw9qNT6IkXu7oA54tDmxaZDIukABV >> ovirt-host=https://engine.set.local:443 >> ovirt-sso-client-id=ovirt-provider-ovn >> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem >> [PROVIDER] >> provider-host=engine.set.local >> >> >>> 12 сент. 2018 г., в 13:59, Dominik Holler <dholler(a)redhat.com> >>> написал(а): >>> >>> On Wed, 12 Sep 2018 13:04:53 +0300 >>> "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: >>> >>>> Hello Dominik! >>>> I have a same issue with OVN provider and SSL >>>> https://www.mail-archive.com/users@ovirt.org/msg47020.html >>>> <https://www.mail-archive.com/users@ovirt.org/msg47020.html> But >>>> certificate changes not helps to resolve it. Maybe you can help me >>>> with this? >>> >>> Sure. Can you please share the relevant lines of >>> ovirt-provider-ovn.log and engine.log, and the information if you >>> are using the certificates generated by engine-setup with >>> users(a)ovirt.org ? Thanks, >>> Dominik

1 0

Guest OS Windows 2016 Server (standard and/or datacenter edition)
by luigirm14＠yahoo.it 12 Sep '18

12 Sep '18

Hi, is there a road map for os guest windows server 2016? Regards

2 1

icons for custom defined OS
by Matthias Leopold 12 Sep '18

12 Sep '18

Hi, I defined additional operating systems in my oVirt 4.2.6 installation according to https://www.ovirt.org/develop/release-management/features/virt/os-info/. Now i want to have custom default icons for use in VM portal for these new OS definitions. How can i do this? I only found a way to change the icon as individual VM portal user, this is nice, but not exactly what i want. thx matthias

1 1

Admin Portal
by mattias.kihl＠gmail.com 12 Sep '18

12 Sep '18

The redirection URI for client is not registered How to add a new host where i can use the adminportal. I found this. > Create a new conf file /etc/ovirt-engine/engine.conf.d/99-sso.conf and add: > SSO_CALLBACK_PREFIX_CHECK=false > > then > systemctl restart ovirt-engine > > This will turn off the additional security check for the callback prefix. But i want to keep the security and learn howto do it correct. Thanks

1 0

upload ISO from webui failed,"Paused by System"
by henaumars＠sina.com 12 Sep '18

12 Sep '18

Hi, I can't upload iso image from webui,always got "Paused by System" system info: engine:4.2.6.4-1.el7 vdsm:4.20.35-1.el7 imageio-proxy:1.4.4-0.el7 imageio-daemon:1.4.4-0.el7 operation: 1、download and install ca to the browser 2、select iso file to upload 3、click test ，alert to installl ca 4、install ca again（optional） 5、upload 6、wait and got "Paused by System" log： engine： 2018-09-11 11:13:22,273+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-61) [02c871da-a599-4201-9dd5-92a468dee952] START, HSMClearTaskVDSCommand(HostName = 21, HSMTaskGuidBaseVDSCommandParameters:{hostId='68f27646-da12-480b-9887-42ada2911132', taskId='90541bd1-65e7-4185-a051-3d8d9c1e3a5f'}), log id: 3ff168d7 2018-09-11 11:13:22,278+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-61) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, HSMClearTaskVDSCommand, log id: 3ff168d7 2018-09-11 11:13:22,278+08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-61) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, SPMClearTaskVDSCommand, log id: 43d30861 2018-09-11 11:13:22,280+08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-61) [02c871da-a599-4201-9dd5-92a468dee952] BaseAsyncTask::removeTaskFromDB: Removed task '90541bd1-65e7-4185-a051-3d8d9c1e3a5f' from DataBase 2018-09-11 11:13:22,280+08 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-61) [02c871da-a599-4201-9dd5-92a468dee952] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '4ff92f68-8353-40ac-a7c5-f0efbd054841' 2018-09-11 11:13:26,098+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-8) [352651c9-ddde-4e1e-b95c-05ad967ed0b1] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:28,836+08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Command 'AddDisk' id: '4b72410d-e5a0-4c43-b7db-a5324a32d012' child commands '[4ff92f68-8353-40ac-a7c5-f0efbd054841]' executions were completed, status 'SUCCEEDED' 2018-09-11 11:13:28,836+08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Command 'AddDisk' id: '4b72410d-e5a0-4c43-b7db-a5324a32d012' Updating status to 'SUCCEEDED', The command end method logic will be executed by one of its parent commands. 2018-09-11 11:13:28,862+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Successfully added Upload disk 'oVirt-toolsSetup-4.2-1.el7.centos.iso' (disk id: '97179509-65eb-4b45-ad8e-ce112cfd016a', image id: '6ca217cc-015e-4d00-872a-faf60a8954ac') for image transfer command '4cdff02c-7fe4-4000-9c92-8ef613597d13' 2018-09-11 11:13:28,892+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] START, PrepareImageVDSCommand(HostName = 21, PrepareImageVDSCommandParameters:{hostId='68f27646-da12-480b-9887-42ada2911132'}), log id: 19407261 2018-09-11 11:13:28,901+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 19407261 2018-09-11 11:13:28,901+08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeLegalityVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] START, SetVolumeLegalityVDSCommand( SetVolumeLegalityVDSCommandParameters:{storagePoolId='ab65cc43-3c9e-4c02-ba75-ccd9fa8691b1', ignoreFailoverLimit='false', storageDomainId='ffc618b9-fd75-4ca2-ace4-15a1b7b58ecf', imageGroupId='97179509-65eb-4b45-ad8e-ce112cfd016a', imageId='6ca217cc-015e-4d00-872a-faf60a8954ac'}), log id: 5068b962 2018-09-11 11:13:28,914+08 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeLegalityVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, SetVolumeLegalityVDSCommand, log id: 5068b962 2018-09-11 11:13:28,915+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] START, AddImageTicketVDSCommand(HostName = 21, AddImageTicketVDSCommandParameters:{hostId='68f27646-da12-480b-9887-42ada2911132', ticketId='3564a630-be37-407f-802d-ce38a01cc104', timeout='300', operations='[write]', size='382971904', url='file:///rhev/data-center/mnt/_data/ffc618b9-fd75-4ca2-ace4-15a1b7b58ecf/images/97179509-65eb-4b45-ad8e-ce112cfd016a/6ca217cc-015e-4d00-872a-faf60a8954ac', filename='null', sparse='true'}), log id: 64950261 2018-09-11 11:13:28,920+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, AddImageTicketVDSCommand, return: StatusOnlyReturn [status=Status [code=0, message=Done]], log id: 64950261 2018-09-11 11:13:28,920+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Started transfer session with ticket id 3564a630-be37-407f-802d-ce38a01cc104, timeout 300 seconds 2018-09-11 11:13:28,920+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Adding image ticket to ovirt-imageio-proxy, id 3564a630-be37-407f-802d-ce38a01cc104 2018-09-11 11:13:28,934+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Updating image transfer 4cdff02c-7fe4-4000-9c92-8ef613597d13 (image 97179509-65eb-4b45-ad8e-ce112cfd016a) phase to Transferring 2018-09-11 11:13:28,935+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [02c871da-a599-4201-9dd5-92a468dee952] Returning from proceedCommandExecution after starting transfer session for image transfer command '4cdff02c-7fe4-4000-9c92-8ef613597d13' 2018-09-11 11:13:29,948+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-56) [02c871da-a599-4201-9dd5-92a468dee952] START, GetImageTicketVDSCommand(HostName = 21, GetImageTicketVDSCommandParameters:{hostId='68f27646-da12-480b-9887-42ada2911132', ticketId='3564a630-be37-407f-802d-ce38a01cc104', timeout='null'}), log id: 1b9af167 2018-09-11 11:13:29,952+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-56) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, GetImageTicketVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.ImageTicketInformation@558504b3, log id: 1b9af167 2018-09-11 11:13:30,111+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [c1647c4b-63fe-4ca7-b4a1-adb77c85e076] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:42,126+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [32ab474a-5bd4-4026-b653-67b2a6d776b9] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:44,039+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [02c871da-a599-4201-9dd5-92a468dee952] START, GetImageTicketVDSCommand(HostName = 21, GetImageTicketVDSCommandParameters:{hostId='68f27646-da12-480b-9887-42ada2911132', ticketId='3564a630-be37-407f-802d-ce38a01cc104', timeout='null'}), log id: 66ab6e50 2018-09-11 11:13:44,044+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetImageTicketVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [02c871da-a599-4201-9dd5-92a468dee952] FINISH, GetImageTicketVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.ImageTicketInformation@558504c1, log id: 66ab6e50 2018-09-11 11:13:46,135+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [1e65c0eb-95b0-4152-9887-5fa9521bb0a9] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:48,327+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [4ad6f0ea-2ae5-4067-b1c2-c0503b2e3676] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:48,328+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-6) [4ad6f0ea-2ae5-4067-b1c2-c0503b2e3676] Updating image transfer 4cdff02c-7fe4-4000-9c92-8ef613597d13 (image 97179509-65eb-4b45-ad8e-ce112cfd016a) phase to Paused by System (message: 'Sent 0MB') 2018-09-11 11:13:48,335+08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-6) [4ad6f0ea-2ae5-4067-b1c2-c0503b2e3676] EVENT_ID: UPLOAD_IMAGE_NETWORK_ERROR(1,062), Unable to upload image to disk 97179509-65eb-4b45-ad8e-ce112cfd016a due to a network error. Make sure ovirt-imageio-proxy service is installed and configured, and ovirt-engine's certificate is registered as a valid CA in the browser. The certificate can be fetched from https://<engine_url>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA 2018-09-11 11:13:50,220+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [2a9835b2-a08d-4efd-9fa0-208d14dd4bdc] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER 2018-09-11 11:13:54,080+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-60) [02c871da-a599-4201-9dd5-92a468dee952] Transfer was paused by system. Upload disk 'oVirt-toolsSetup-4.2-1.el7.centos.iso' (disk id: '97179509-65eb-4b45-ad8e-ce112cfd016a', image id: '6ca217cc-015e-4d00-872a-faf60a8954ac') 2018-09-11 11:13:54,196+08 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [3742a3f4-4352-46c4-8480-0035e8d7a5fb] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_DISK with role type USER imageio-proxy： (Thread-4 ) INFO 2018-09-11 11:12:32,476 auth:201:auth2:(delete_ticket) Deleting ticket u'9a8117e4-2ba0-40c3-ae3d-aadc43b7857d' (Thread-5 ) INFO 2018-09-11 11:13:28,929 auth:187:auth2:(add_signed_ticket) Adding new ticket: <Ticket id=u'3564a630-be37-407f-802d-ce38a01cc104', url=u'https://172.22.224.21:54322' timeout=35999.070008039474 at 0x7fa30cdd6b50> imageio-daemon： 2018-09-11 11:13:28,402 INFO (Thread-12) [tickets] [local] ADD ticket={u'uuid': u'3564a630-be37-407f-802d-ce38a01cc104', u'ops': [u'write'], u'url': u'file:///rhev/data-center/mnt/_data/ffc618b9-fd75-4ca2-ace4-15a1b7b58ecf/images/97179509-65eb-4b45-ad8e-ce112cfd016a/6ca217cc-015e-4d00-872a-faf60a8954ac', u'sparse': True, u'timeout': 300, u'size': 382971904} I‘ve been stucked for days and need to get help！

2 1

Ovirt and gluster deployment - host name
by florentl 11 Sep '18

11 Sep '18

Hello, I want to deploy ovirt (hosted engine) and gluster on three servers. I have thought about a configuration but I'm not sure that it's the most suitable one. All the servers have 2 ten gigabit Ethernet nic. I read that, am besten, I must dedicate one nic for the storage and another one for the system. So I will have two netnork address space : - for the system : 192.168.176.0/24 with a gateway configured - for the storage : 10.255.255.0/24 without a gateway Inside my hosts file on all the server I will have : 192.168.176.1 server1 192.168.176.2 server2 192.168.176.3 server3 10.255.255.1 gluster1 10.255.255.2 gluster2 10.255.255.3 gluster2 When I start the gluster deployment I will use gluster1, gluster2 and gluster3 name. And after the gluster deployment during the hyperconverged setup I will use server1, server2 and server3 name. May I have your opinion about this deployment ? Thanks in advance for the help. Florent LORNE

3 2

Ovirt Single Node Hyperconverged
by Keith Winn 11 Sep '18

11 Sep '18

Hi, I am looking at using Ovirt on a single machine. I used to use the all-in-one setup a while ago. I have only two vms and setting up two servers and a storage is out of my budget right now. The all in one solution sounds good, but I have some questions concerning the gdeploy config file. I am new to gluster and am unsure what I need. The server is ibm system x3550 m3 with two 1TB drives setup as a mirror. For these, what do I put if the disks are already setup as raid through the raid controller? Jbod [disktype] @RAIDTYPE@ #Possible values raid6, raid10, raid5, jbod [diskcount] @NUMBER_OF_DATA_DISKS@ #Ignored in case of jbod [stripesize] @STRIPE_SIZE@ #256 in case of jbod My second question is where do I get the Device name in the following: [script1] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d @DEVICE@ Is this the dev/sda on the disk or some other name. I was planning on using ovirt node as a staring point as that seems easier. Thanks in advance for the help.

3 3

LDAP authentication does not work after engine upgrade to ovirt 4.6
by Michael Watters 11 Sep '18

11 Sep '18

I've just upgraded our ovirt engine server to ovirt 4.6 and it appears that LDAP logins no longer work. When I attempt to log in using an AD account the following errors are shown in the engine log. 2018-09-11 10:03:44,610-04 ERROR [org.ovirt.engine.core.sso.servlets.InteractiveAuthServlet] (default task-10) [] Internal Server Error: Cannot locate principal 'username(a)example.com' 2018-09-11 10:03:44,610-04 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-10) [] Cannot locate principal 'username(a)example.com' 2018-09-11 10:03:44,645-04 ERROR [org.ovirt.engine.core.aaa.servlet.SsoPostLoginServlet] (default task-10) [] server_error: Cannot locate principal 'username(a)example.com' I have not changed any LDAP settings and ldapsearch is able to find this object without any issues. Does anybody have any idea what would cause this?

1 1

Managing multiple oVirt installs?
by femi adegoke 11 Sep '18

11 Sep '18

Let's say you have multiple oVirt installs. How can they all be "managed" by using a single engine web UI (so I don't have to login 5 different times)?

8 16

Re: Engine Setup Error
by Sakhi Hadebe 11 Sep '18

11 Sep '18

HI, I re-installed the cluster and got the hosted engine deployed succesfully. Thank you for your assistance On Thu, Sep 6, 2018 at 1:54 PM, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi Simone, > > Yes the ownership of /var/log/ovirt-imageio-daemon is vdsm:kvm, 755. > > Below is the version of the ovirt packages currently installed on my oVirt > Nodes: > > ovirt-vmconsole-1.0.5-4.el7.centos.noarch > ovirt-provider-ovn-driver-1.2.14-1.el7.noarch > ovirt-release-host-node-4.2.6-1.el7.noarch > ovirt-hosted-engine-setup-2.2.26-1.el7.noarch > ovirt-node-ng-nodectl-4.2.0-0.20180903.0.el7.noarch > ovirt-release42-4.2.6-1.el7.noarch > ovirt-imageio-common-1.4.4-0.el7.x86_64 > python-ovirt-engine-sdk4-4.2.8-2.el7.x86_64 > *ovirt-imageio-daemon-1.4.4-0.el7.noarch* > *ovirt-hosted-engine-ha-2.2.16-1.el7.noarch* > ovirt-host-4.2.3-1.el7.x86_64 > ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch > ovirt-host-deploy-1.7.4-1.el7.noarch > cockpit-machines-ovirt-172-2.el7.centos.noarch > ovirt-host-dependencies-4.2.3-1.el7.x86_64 > ovirt-engine-appliance-4.2-20180903.1.el7.noarch > ovirt-setup-lib-1.1.5-1.el7.noarch > cockpit-ovirt-dashboard-0.11.33-1.el7.noarch > ovirt-vmconsole-host-1.0.5-4.el7.centos.noarch > ovirt-node-ng-image-update-placeholder-4.2.6-1.el7.noarch > > I updated ovirt packages. and the ovirt-imageio-daemon is now running. > > ovirt-ha-agent is failing: *Failed to start monitor agents. *The engine > was successfully deployed but can't access it as the ovirt-ha-agent is not > running with the error below and log files attached: > > [root@goku ovirt-hosted-engine-ha]# journalctl -xe -u ovirt-ha-agent > Sep 06 13:50:36 goku systemd[1]: ovirt-ha-agent.service holdoff time over, > scheduling restart. > Sep 06 13:50:36 goku systemd[1]: Started oVirt Hosted Engine High > Availability Monitoring Agent. > -- Subject: Unit ovirt-ha-agent.service has finished start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ovirt-ha-agent.service has finished starting up. > -- > -- The start-up result is done. > Sep 06 13:50:36 goku systemd[1]: Starting oVirt Hosted Engine High > Availability Monitoring Agent... > -- Subject: Unit ovirt-ha-agent.service has begun start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit ovirt-ha-agent.service has begun starting up. > Sep 06 13:50:37 goku ovirt-ha-agent[50395]: ovirt-ha-agent > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngi > Sep 06 13:50:37 goku ovirt-ha-agent[50395]: ovirt-ha-agent > ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceb > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agen > return action(he) > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agen > return > he.start_monitoring() > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agen > self._initialize_broker() > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agen > m.get('options', {})) > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/ > .format(type, options, e)) > RequestError: Failed to start > monitor ping, options {'addr': '192.16 > Sep 06 13:50:37 goku ovirt-ha-agent[50395]: ovirt-ha-agent > ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying > Sep 06 13:50:37 goku systemd[1]: ovirt-ha-agent.service: main process > exited, code=exited, status=157/n/a > Sep 06 13:50:37 goku systemd[1]: Unit ovirt-ha-agent.service entered > failed state. > Sep 06 13:50:37 goku systemd[1]: ovirt-ha-agent.service failed. > lines 3528-3559/3559 (END) > > > > On Wed, Sep 5, 2018 at 1:53 PM, Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >> Can you please check if on your host you have >> /var/log/ovirt-imageio-daemon and its ownership and permissions (it should >> be vdsm:kvm,700)? >> Can you please report which version of ovirt-imageio-daemon you are >> using? >> We had a bug there but it has been fixed long time ago. >> >> >> On Wed, Sep 5, 2018 at 12:04 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: >> >>> Sorry, I mistakenly send the email: >>> >>> Below is the output of: >>> [root@glustermount ~]# systemctl status ovirt-imageio-daemon.service -l >>> ● ovirt-imageio-daemon.service - oVirt ImageIO Daemon >>> Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; >>> disabled; vendor preset: disabled) >>> Active: failed (Result: start-limit) since Tue 2018-09-04 16:55:16 >>> SAST; 19h ago >>> Condition: start condition failed at Wed 2018-09-05 11:56:46 SAST; 2min >>> 9s ago >>> ConditionPathExists=/etc/pki/vdsm/certs/vdsmcert.pem was not >>> met >>> Process: 11345 ExecStart=/usr/bin/ovirt-imageio-daemon (code=exited, >>> status=1/FAILURE) >>> Main PID: 11345 (code=exited, status=1/FAILURE) >>> >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>> ImageIO Daemon. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>> ovirt-imageio-daemon.service entered failed state. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service failed. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service holdoff time over, scheduling restart. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: start request repeated too >>> quickly for ovirt-imageio-daemon.service >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>> ImageIO Daemon. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>> ovirt-imageio-daemon.service entered failed state. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service failed. >>> [root@glustermount ~]# journalctl -xe -u ovirt-imageio-daemon.service >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: File >>> "/usr/lib64/python2.7/logging/handlers.py", >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: >>> BaseRotatingHandler.__init__(self, filename, mode >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: File >>> "/usr/lib64/python2.7/logging/handlers.py", >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: >>> logging.FileHandler.__init__(self, filename, mode >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: File >>> "/usr/lib64/python2.7/logging/__init__.py", >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: >>> StreamHandler.__init__(self, self._open()) >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: File >>> "/usr/lib64/python2.7/logging/__init__.py", >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: stream = >>> open(self.baseFilename, self.mode) >>> Sep 04 16:55:16 glustermount.goku ovirt-imageio-daemon[11345]: IOError: >>> [Errno 2] No such file or directory: '/v >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service: main process exited, code=exited, st >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>> ImageIO Daemon. >>> -- Subject: Unit ovirt-imageio-daemon.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-imageio-daemon.service has failed. >>> -- >>> -- The result is failed. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>> ovirt-imageio-daemon.service entered failed state. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service failed. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service holdoff time over, scheduling restart >>> Sep 04 16:55:16 glustermount.goku systemd[1]: start request repeated too >>> quickly for ovirt-imageio-daemon.servic >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>> ImageIO Daemon. >>> -- Subject: Unit ovirt-imageio-daemon.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-imageio-daemon.service has failed. >>> -- >>> -- The result is failed. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>> ovirt-imageio-daemon.service entered failed state. >>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>> ovirt-imageio-daemon.service failed. >>> >>> >>> On Wed, Sep 5, 2018 at 12:01 PM, Sakhi Hadebe <sakhi(a)sanren.ac.za> >>> wrote: >>> >>>> # systemctl status ovirt-imageio-daemon.service >>>> ● ovirt-imageio-daemon.service - oVirt ImageIO Daemon >>>> Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; >>>> disabled; vendor preset: disabled) >>>> Active: failed (Result: start-limit) since Tue 2018-09-04 16:55:16 >>>> SAST; 19h ago >>>> Condition: start condition failed at Wed 2018-09-05 11:56:46 SAST; 1min >>>> 58s ago >>>> ConditionPathExists=/etc/pki/vdsm/certs/vdsmcert.pem was >>>> not met >>>> Process: 11345 ExecStart=/usr/bin/ovirt-imageio-daemon (code=exited, >>>> status=1/FAILURE) >>>> Main PID: 11345 (code=exited, status=1/FAILURE) >>>> >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>>> ImageIO Daemon. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>>> ovirt-imageio-daemon.service entered failed state. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service failed. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service holdoff time over, scheduling ...art. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: start request repeated >>>> too quickly for ovirt-imageio-daemon...vice >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>>> ImageIO Daemon. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>>> ovirt-imageio-daemon.service entered failed state. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service failed. >>>> Hint: Some lines were ellipsized, use -l to show in full. >>>> [root@glustermount ~]# systemctl status ovirt-imageio-daemon.service -l >>>> ● ovirt-imageio-daemon.service - oVirt ImageIO Daemon >>>> Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; >>>> disabled; vendor preset: disabled) >>>> Active: failed (Result: start-limit) since Tue 2018-09-04 16:55:16 >>>> SAST; 19h ago >>>> Condition: start condition failed at Wed 2018-09-05 11:56:46 SAST; 2min >>>> 9s ago >>>> ConditionPathExists=/etc/pki/vdsm/certs/vdsmcert.pem was >>>> not met >>>> Process: 11345 ExecStart=/usr/bin/ovirt-imageio-daemon (code=exited, >>>> status=1/FAILURE) >>>> Main PID: 11345 (code=exited, status=1/FAILURE) >>>> >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>>> ImageIO Daemon. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>>> ovirt-imageio-daemon.service entered failed state. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service failed. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service holdoff time over, scheduling restart. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: start request repeated >>>> too quickly for ovirt-imageio-daemon.service >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Failed to start oVirt >>>> ImageIO Daemon. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: Unit >>>> ovirt-imageio-daemon.service entered failed state. >>>> Sep 04 16:55:16 glustermount.goku systemd[1]: >>>> ovirt-imageio-daemon.service failed. >>>> >>>> Output of: >>>> >>>> On Wed, Sep 5, 2018 at 11:35 AM, Simone Tiraboschi <stirabos(a)redhat.com >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Wed, Sep 5, 2018 at 11:10 AM Sakhi Hadebe <sakhi(a)sanren.ac.za> >>>>> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> The host deploy logs are showing the below errors: >>>>>> >>>>>> [root@garlic engine-logs-2018-09-05T08:48:22Z]# cat >>>>>> /var/log/ovirt-hosted-engine-setup/engine-logs-2018-09-05T08 >>>>>> \:34\:55Z/ovirt-engine/host-deploy/ovirt-host-deploy-20180 >>>>>> 905103605-garlic.sanren.ac.za-543b536b.log | grep -i error >>>>>> 2018-09-05 10:35:46,909+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/error=bool:'False' >>>>>> 2018-09-05 10:35:47,116 [ERROR] __main__.py:8011:MainThread >>>>>> @identity.py:145 - Reload of consumer identity cert >>>>>> /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such >>>>>> file or directory: '/etc/pki/consumer/key.pem' >>>>>> 2018-09-05 10:35:47,383+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/error=bool:'False' >>>>>> 2018-09-05 10:35:47,593 [ERROR] __main__.py:8011:MainThread >>>>>> @identity.py:145 - Reload of consumer identity cert >>>>>> /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such >>>>>> file or directory: '/etc/pki/consumer/key.pem' >>>>>> 2018-09-05 10:35:48,245+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/error=bool:'False' >>>>>> Job for ovirt-imageio-daemon.service failed because the control >>>>>> process exited with error code. See "systemctl status >>>>>> ovirt-imageio-daemon.service" and "journalctl -xe" for details. >>>>>> RuntimeError: Failed to start service 'ovirt-imageio-daemon' >>>>>> 2018-09-05 10:36:05,098+0200 ERROR otopi.context >>>>>> context._executeMethod:152 Failed to execute stage 'Closing up': Failed to >>>>>> start service 'ovirt-imageio-daemon' >>>>>> 2018-09-05 10:36:05,099+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/error=bool:'True' >>>>>> 2018-09-05 10:36:05,099+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/exceptionInfo=list:'[(<type >>>>>> 'exceptions.RuntimeError'>, RuntimeError("Failed to start service >>>>>> 'ovirt-imageio-daemon'",), <traceback object at 0x7f4de25ff320>)]' >>>>>> 2018-09-05 10:36:05,106+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/error=bool:'True' >>>>>> 2018-09-05 10:36:05,106+0200 DEBUG otopi.context >>>>>> context.dumpEnvironment:869 ENV BASE/exceptionInfo=list:'[(<type >>>>>> 'exceptions.RuntimeError'>, RuntimeError("Failed to start service >>>>>> 'ovirt-imageio-daemon'",), <traceback object at 0x7f4de25ff320>)]' >>>>>> >>>>>> I coudn't find anything helpful from the internet. >>>>>> >>>>> >>>>> something relevant int he output of >>>>> systemctl status ovirt-imageio-daemon.service >>>>> and >>>>> journalctl -xe -u ovirt-imageio-daemon.service >>>>> ? >>>>> >>>>> >>>>> >>>>>> >>>>>> On Tue, Sep 4, 2018 at 6:46 PM, Simone Tiraboschi < >>>>>> stirabos(a)redhat.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Sep 4, 2018 at 6:07 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Sahina, >>>>>>>> >>>>>>>> I am sorry I can't reproduce the error nor access the logs since I >>>>>>>> did a fresh installed pn nodes. However now I can't even react that far >>>>>>>> because the engine deployment fails to start the host up: >>>>>>>> >>>>>>>> >>>>>>>> [ INFO ] TASK [Wait for the host to be up] >>>>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": >>>>>>>> {"ovirt_hosts": [{"address": "goku.sanren.ac.za", >>>>>>>> "affinity_labels": [], "auto_numa_status": "unknown", "certificate": >>>>>>>> {"organization": "sanren.ac.za", "subject": "O=sanren.ac.za,CN= >>>>>>>> goku.sanren.ac.za"}, "cluster": {"href": >>>>>>>> "/ovirt-engine/api/clusters/1ca368cc-b052-11e8-b7de-00163e008187", >>>>>>>> "id": "1ca368cc-b052-11e8-b7de-00163e008187"}, "comment": "", >>>>>>>> "cpu": {"speed": 0.0, "topology": {}}, "device_passthrough": {"enabled": >>>>>>>> false}, "devices": [], "external_network_provider_configurations": >>>>>>>> [], "external_status": "ok", "hardware_information": >>>>>>>> {"supported_rng_sources": []}, "hooks": [], "href": >>>>>>>> "/ovirt-engine/api/hosts/1c575995-70b1-43f7-b348-4a9788e070cd", >>>>>>>> "id": "1c575995-70b1-43f7-b348-4a9788e070cd", "katello_errata": >>>>>>>> [], "kdump_status": "unknown", "ksm": {"enabled": false}, >>>>>>>> "max_scheduling_memory": 0, "memory": 0, "name": "goku.sanren.ac.za", >>>>>>>> "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": >>>>>>>> false, "os": {"custom_kernel_cmdline": ""}, "permissions": [], "port": >>>>>>>> 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, >>>>>>>> "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", >>>>>>>> "se_linux": {}, "spm": {"priority": 5, "status": "none"}, "ssh": >>>>>>>> {"fingerprint": "SHA256:B3/PDH551EFid93fm6PoRryi6/cXuVE8yNgiiiROh84", >>>>>>>> "port": 22}, "statistics": [], "status": "install_failed", >>>>>>>> "storage_connection_extensions": [], "summary": {"total": 0}, >>>>>>>> "tags": [], "transparent_huge_pages": {"enabled": false}, "type": >>>>>>>> "ovirt_node", "unmanaged_networks": [], "update_available": false}]}, >>>>>>>> "attempts": 120, "changed": false} >>>>>>>> >>>>>>>> "status": "install_failed" >>>>>>> >>>>>>> You have to check host-deploy logs to get a details error message. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Please help. >>>>>>>> >>>>>>>> On Mon, Sep 3, 2018 at 1:34 PM, Sahina Bose <sabose(a)redhat.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Aug 29, 2018 at 8:39 PM, Sakhi Hadebe <sakhi(a)sanren.ac.za> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I am sorry to bother you again. >>>>>>>>>> >>>>>>>>>> I am trying to deploy an oVirt engine for oVirtNode-4.2.5.1. I >>>>>>>>>> get the same error I encountered before: >>>>>>>>>> >>>>>>>>>> [ INFO ] TASK [Add glusterfs storage domain] >>>>>>>>>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail >>>>>>>>>> is "[Problem while trying to mount target]". HTTP response code >>>>>>>>>> is 400. >>>>>>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, >>>>>>>>>> "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Problem >>>>>>>>>> while trying to mount target]\". HTTP response code is 400."} >>>>>>>>>> Please specify the storage you would like to use >>>>>>>>>> (glusterfs, iscsi, fc, nfs)[nfs]: >>>>>>>>>> >>>>>>>>>> The glusterd daemon is running. >>>>>>>>>> >>>>>>>>> >>>>>>>>> mounting 172.16.4.18:/engine at /rhev/data-center/mnt/glusterS >>>>>>>>> D/172.16.4.18:_engine (mount:204) >>>>>>>>> 2018-08-29 16:47:28,846+0200 ERROR (jsonrpc/3) [storage.HSM] Could >>>>>>>>> not connect to storageServer (hsm:2398) >>>>>>>>> >>>>>>>>> Can you try to see if you are able to mount 172.16.4.18:/engine >>>>>>>>> on the server you're deploying Hosted Engine using "mount -t glusterfs >>>>>>>>> 172.16.4.18:/engine /mnt/test" >>>>>>>>> >>>>>>>>> >>>>>>>>>> During the deployment of the engine it sets the engine entry in >>>>>>>>>> the /etc/hosts file with the IP Address of 192.168.124.* which it gets form >>>>>>>>>> the virbr0 bridge interface. I stopped the bridge and deleted it, but still >>>>>>>>>> giving the same error. Not sure what causes it to use that interface. >>>>>>>>>> Please help! >>>>>>>>>> >>>>>>>>>> But I give the engine an IP of 192.168.1.10 same subnet as my >>>>>>>>>> gateway and my ovirtmgmt bridge. Attached is the ifconfig output of my >>>>>>>>>> Node, engine.log and vdsm.log. >>>>>>>>>> >>>>>>>>>> Your assistance is always appreciated >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jul 11, 2018 at 11:47 AM, Sahina Bose <sabose(a)redhat.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Is glusterd running on the server: goku.sanren.** >>>>>>>>>>> There's an error >>>>>>>>>>> Failed to get volume info: Command execution failed >>>>>>>>>>> error: Connection failed. Please check if gluster daemon is >>>>>>>>>>> operational >>>>>>>>>>> >>>>>>>>>>> Please check the volume status using "gluster volume status >>>>>>>>>>> engine" >>>>>>>>>>> >>>>>>>>>>> and if all looks ok, attach the mount logs from >>>>>>>>>>> /var/log/glusterfs >>>>>>>>>>> >>>>>>>>>>> On Wed, Jul 11, 2018 at 1:57 PM, Sakhi Hadebe < >>>>>>>>>>> sakhi(a)sanren.ac.za> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I have managed to fix the error by enabling the DMA >>>>>>>>>>>> Virtualisation in BIOS. I am now hit with a new error: It's failing to add >>>>>>>>>>>> a glusterfs storage domain: >>>>>>>>>>>> >>>>>>>>>>>> [ INFO ] TASK [Add glusterfs storage domain] >>>>>>>>>>>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault >>>>>>>>>>>> detail is "[Problem while trying to mount target]". HTTP response code is >>>>>>>>>>>> 400. >>>>>>>>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, >>>>>>>>>>>> "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Problem >>>>>>>>>>>> while trying to mount target]\". HTTP response code is 400."} >>>>>>>>>>>> Please specify the storage you would like to use >>>>>>>>>>>> (glusterfs, iscsi, fc, nfs)[nfs]: >>>>>>>>>>>> >>>>>>>>>>>> Attached are vdsm and engine log files. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Jul 11, 2018 at 9:57 AM, Sakhi Hadebe < >>>>>>>>>>>> sakhi(a)sanren.ac.za> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Jul 11, 2018 at 9:33 AM, Sakhi Hadebe < >>>>>>>>>>>>> sakhi(a)sanren.ac.za> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Below are the versions of packages installed. Please find the >>>>>>>>>>>>>> logs attached. >>>>>>>>>>>>>> Qemu: >>>>>>>>>>>>>> ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch >>>>>>>>>>>>>> libvirt-daemon-driver-qemu-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> qemu-img-ev-2.10.0-21.el7_5.4.1.x86_64 >>>>>>>>>>>>>> qemu-kvm-ev-2.10.0-21.el7_5.4.1.x86_64 >>>>>>>>>>>>>> qemu-kvm-common-ev-2.10.0-21.el7_5.4.1.x86_64 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Libvirt installed packages: >>>>>>>>>>>>>> libvirt-daemon-driver-storage-disk-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-config-nwfilter-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-iscsi-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-network-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-libs-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-secret-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-core-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-qemu-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-python-3.9.0-1.el7.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-nodedev-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-rbd-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-scsi-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-config-network-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-client-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-kvm-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-logical-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-interface-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-lock-sanlock-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-storage-mpath-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-lxc-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> libvirt-daemon-driver-nwfilter-3.9.0-14.el7_5.6.x86_64 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Virt-manager: >>>>>>>>>>>>>> virt-manager-common-1.4.3-3.el7.noarch >>>>>>>>>>>>>> >>>>>>>>>>>>>> oVirt: >>>>>>>>>>>>>> [root@localhost network-scripts]# rpm -qa | grep ovirt >>>>>>>>>>>>>> ovirt-setup-lib-1.1.4-1.el7.centos.noarch >>>>>>>>>>>>>> cockpit-ovirt-dashboard-0.11.28-1.el7.noarch >>>>>>>>>>>>>> ovirt-imageio-common-1.3.1.2-0.el7.centos.noarch >>>>>>>>>>>>>> ovirt-vmconsole-host-1.0.5-4.el7.centos.noarch >>>>>>>>>>>>>> ovirt-host-dependencies-4.2.3-1.el7.x86_64 >>>>>>>>>>>>>> ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch >>>>>>>>>>>>>> ovirt-imageio-daemon-1.3.1.2-0.el7.centos.noarch >>>>>>>>>>>>>> ovirt-host-4.2.3-1.el7.x86_64 >>>>>>>>>>>>>> python-ovirt-engine-sdk4-4.2.7-2.el7.x86_64 >>>>>>>>>>>>>> ovirt-host-deploy-1.7.4-1.el7.noarch >>>>>>>>>>>>>> cockpit-machines-ovirt-169-1.el7.noarch >>>>>>>>>>>>>> ovirt-hosted-engine-ha-2.2.14-1.el7.noarch >>>>>>>>>>>>>> ovirt-vmconsole-1.0.5-4.el7.centos.noarch >>>>>>>>>>>>>> ovirt-provider-ovn-driver-1.2.11-1.el7.noarch >>>>>>>>>>>>>> ovirt-engine-appliance-4.2-20180626.1.el7.noarch >>>>>>>>>>>>>> ovirt-release42-4.2.4-1.el7.noarch >>>>>>>>>>>>>> ovirt-hosted-engine-setup-2.2.22.1-1.el7.noarch >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Jul 11, 2018 at 6:48 AM, Yedidyah Bar David < >>>>>>>>>>>>>> didi(a)redhat.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Jul 10, 2018 at 11:32 PM, Sakhi Hadebe < >>>>>>>>>>>>>>> sakhi(a)sanren.ac.za> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I did not select any CPU architecture. It doenst gove me >>>>>>>>>>>>>>>> the option to select one. It only states the number of virtual CPUs and the >>>>>>>>>>>>>>>> memory for the engine VM. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Looking at the documentation of installing >>>>>>>>>>>>>>>> ovirt-release36.rpm....it does allow you to select te CPU, but not when >>>>>>>>>>>>>>>> installing ovirt-release42.rpm >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tuesday, July 10, 2018, Alastair Neil < >>>>>>>>>>>>>>>> ajneil.tech(a)gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> what did you select as your CPU architecture when you >>>>>>>>>>>>>>>>> created the cluster? It looks like the VM is trying to use a CPU type of >>>>>>>>>>>>>>>>> "Custom", how many nodes in your cluster? I suggest you specify the lowest >>>>>>>>>>>>>>>>> common denominator of CPU architecture (e.g. Sandybridge) of the nodes as >>>>>>>>>>>>>>>>> the CPU architecture of the cluster.. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, 10 Jul 2018 at 12:01, Sakhi Hadebe < >>>>>>>>>>>>>>>>> sakhi(a)sanren.ac.za> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have just re-installed centOS 7 in 3 servers and have >>>>>>>>>>>>>>>>>> configured gluster volumes following this documentation: >>>>>>>>>>>>>>>>>> https://www.ovirt.org/blog/201 >>>>>>>>>>>>>>>>>> 6/03/up-and-running-with-ovirt-3-6/, But I have >>>>>>>>>>>>>>>>>> installed >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> package. >>>>>>>>>>>>>>>>>> Hosted-engine --deploy is failing with this error: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> "rhel7", "--virt-type", "kvm", "--memory", "16384", >>>>>>>>>>>>>>>>>> "--vcpus", "4", "--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio", >>>>>>>>>>>>>>>>>> "--disk", "/var/tmp/localvm0nnJH9/images >>>>>>>>>>>>>>>>>> /eacac30d-0304-4c77-8753-6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a", >>>>>>>>>>>>>>>>>> "--import", "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom", >>>>>>>>>>>>>>>>>> "--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video", >>>>>>>>>>>>>>>>>> "vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon", >>>>>>>>>>>>>>>>>> "none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"], >>>>>>>>>>>>>>>>>> "delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg": >>>>>>>>>>>>>>>>>> "non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552", >>>>>>>>>>>>>>>>>> "stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64 >>>>>>>>>>>>>>>>>> kvm domain on x86_64 host is not supported by hypervisor\nDomain >>>>>>>>>>>>>>>>>> installation does not appear to have been successful.\nIf it was, you can >>>>>>>>>>>>>>>>>> restart your domain by running:\n virsh --connect qemu:///system start >>>>>>>>>>>>>>>>>> HostedEngineLocal\notherwise, please restart your installation.", >>>>>>>>>>>>>>>>>> "stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for >>>>>>>>>>>>>>>>>> x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain >>>>>>>>>>>>>>>>>> installation does not appear to have been successful.", "If it was, you can >>>>>>>>>>>>>>>>>> restart your domain by running:", " virsh --connect qemu:///system start >>>>>>>>>>>>>>>>>> HostedEngineLocal", "otherwise, please restart your installation."], >>>>>>>>>>>>>>>>>> "stdout": "\nStarting install...", "stdout_lines": ["", "Starting >>>>>>>>>>>>>>>>>> install..."]} >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This seems to be in the phase where we create a local vm for >>>>>>>>>>>>>>> the engine. We do this with plain virt-install, nothing fancy. Searching >>>>>>>>>>>>>>> the net for "unsupported configuration: CPU mode 'custom'" finds other >>>>>>>>>>>>>>> relevant reports, you might want to check them. You can see the command in >>>>>>>>>>>>>>> bootstrap_local_vm.yml . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please check/share versions of relevant packages (libvirt*, >>>>>>>>>>>>>>> qemu*, etc) and relevant logs (libvirt). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Also updating the subject line and adding Simone. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Didi >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> Sakhi Hadebe >>>>>>>>>>>>>> >>>>>>>>>>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>>>>>>>>>> >>>>>>>>>>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>>>>>>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>>>>>>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>>>>>>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> Sakhi Hadebe >>>>>>>>>>>>> >>>>>>>>>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>>>>>>>>> >>>>>>>>>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>>>>>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>>>>>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>>>>>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Regards, >>>>>>>>>>>> Sakhi Hadebe >>>>>>>>>>>> >>>>>>>>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>>>>>>>> >>>>>>>>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>>>>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>>>>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>>>>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>>>>>> oVirt Code of Conduct: https://www.ovirt.org/communit >>>>>>>>>>>> y/about/community-guidelines/ >>>>>>>>>>>> List Archives: https://lists.ovirt.org/archiv >>>>>>>>>>>> es/list/users(a)ovirt.org/message/YHKUKW22QLRVS56XZBXEWOGORFWF >>>>>>>>>>>> EGIA/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Sakhi Hadebe >>>>>>>>>> >>>>>>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>>>>>> >>>>>>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> Sakhi Hadebe >>>>>>>> >>>>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>>>> >>>>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>> oVirt Code of Conduct: https://www.ovirt.org/communit >>>>>>>> y/about/community-guidelines/ >>>>>>>> List Archives: https://lists.ovirt.org/archiv >>>>>>>> es/list/users(a)ovirt.org/message/DS7O33ZSGV5ZAHXKA3KT2ABYW3VJJWXQ/ >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Sakhi Hadebe >>>>>> >>>>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>>>> >>>>>> Tel: +27 12 841 2308 <+27128414213> >>>>>> Fax: +27 12 841 4223 <+27128414223> >>>>>> Cell: +27 71 331 9622 <+27823034657> >>>>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>>>> >>>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Sakhi Hadebe >>>> >>>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>>> >>>> Tel: +27 12 841 2308 <+27128414213> >>>> Fax: +27 12 841 4223 <+27128414223> >>>> Cell: +27 71 331 9622 <+27823034657> >>>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>>> >>>> >>> >>> >>> -- >>> Regards, >>> Sakhi Hadebe >>> >>> Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR >>> >>> Tel: +27 12 841 2308 <+27128414213> >>> Fax: +27 12 841 4223 <+27128414223> >>> Cell: +27 71 331 9622 <+27823034657> >>> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> >>> >>> > > > -- > Regards, > Sakhi Hadebe > > Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR > > Tel: +27 12 841 2308 <+27128414213> > Fax: +27 12 841 4223 <+27128414223> > Cell: +27 71 331 9622 <+27823034657> > Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> > > -- Regards, Sakhi Hadebe Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR Tel: +27 12 841 2308 <+27128414213> Fax: +27 12 841 4223 <+27128414223> Cell: +27 71 331 9622 <+27823034657> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za>

1 0

add gluster cluster to deployed cluster
by p.staniforth＠leedsbeckett.ac.uk 11 Sep '18

11 Sep '18

Hello People, I have a 3 node cluster this just has virt service deployed, how would I add gluster service to this. We have installed 2 extra disks in each node and they are running oVirt Node 4.2.5.1 After we have a gluster service running how easy would it be to migrate an existing engine to Self Hosted Engine? Thanks, Paul S.

2 2

Clean stuck VM from ovirt dashboard
by Alex K 10 Sep '18

10 Sep '18

Hi all, I have a failed clone of a VM which led to the clone being listed as a VM with state "Image locked", as if the clone is still continuing. No tasks are being shown and for sure the clone is not continuing. Also there are not disk images listed for this VM instance at the disks tab. How can i remove this fake VM from the GUI. There might be some steps I can do in the engine DB to make the engine forget about this VM. I a running ovirt 4.1.9. (I know not the latest, though this will be for some time until we prepare to move to 4.2.X) Thanx, Alex

2 2

hosted-engine --check-liveliness returns "Hosted Engine is not up!" for host other cluster
by omprakashp＠cdac.in 10 Sep '18

10 Sep '18

Hi , I am just getting started with Ovirt. I have setup 3 Ovirt-Nodes(all on physical host) and deployed self hosted engine with iscsi storage on one of the host. On engine ui, i have create two Clusters(C1, C2) and Engine is running in C1. While executing "hosted-engine --check-liveliness" on hosts in C2 cluster, it says "Hosted Engine is not up!". Is this an issue? Or this means i have to deploy hosted engine in C2 cluster too.

2 1

Moving all disks to new storage domain
by Simon Vincent 10 Sep '18

10 Sep '18

I need to decommission an old SAN so I have connected a new one into ovirt as a new storage domain. I would like to use a python script to move all disks/snapshots/everything over to the new storage domain but I am having some problems. I am trying to search for all VMs using a particular storage domain but this is not working how I would like. The code I am using is: vms = vms_service.list(search='Storage=team-data') However this is returning VMs which are using storage domains 'team-data' and 'team-data2'. Is this a bug or is there another way to return vms from just 'team-data'? My script so far is: connection = sdk.Connection( url=ovaddress, username=username, password=password, insecure=True ) system_service = connection.system_service() vms_service = system_service.vms_service() disks_service = connection.system_service().disks_service() vms = vms_service.list(search='Storage=team-data') sds_service = connection.system_service().storage_domains_service() dest_sd = sds_service.list(search='name=team-data2') if len(dest_sd)!=1: exit() dest_sd=dest_sd[0] for vm in vms: print (vm.name) vm_service = vms_service.vm_service(vm.id) disk_attachments = vm_service.disk_attachments_service().list() for disk_attachment in disk_attachments: disk = connection.follow_link(disk_attachment.disk) print (" disk: " + disk.name) disk_service = disks_service.disk_service(disk.id) disk_service.move(storage_domain=dest_sd) while True: print("Waiting for movement to complete ...") time.sleep(10) disk = disk_service.get() if disk.status == types.DiskStatus.OK: break connection.close()

1 0

supermicro hardware infrastructure
by l.savarese＠storelink.it 10 Sep '18

10 Sep '18

Hello everybody I would to install oVirt 4.2.6 on the below hardware infrastructure: 2 server SUPERMICRO TWINSERVER (2029TP-HC0R) with one Adapter 2-port 10G SFP+ installed on each node (AOC-MTGN-I2SM-O) 1 Storage QSAN XS1200 Series connected via iSCSI 10G to servers Are you aware of any hardware incompatibilities? Do you have any advice? Best regards Luigi

1 0

oVirt + Gluster geo-replication
by femi adegoke 07 Sep '18

07 Sep '18

Hi Sahina, https://ovirt.org/develop/release-management/features/gluster/gluster-geo-r… Unfortunately, there isn't info on how to set this up. Can you share with us any tips or info needed to do geo-rep between 2 sites? I also read an article that says geo-rep between 3 sites is possible? Thanks, Femi

2 2

oVirt 4.2 Limits
by Markus Frei 07 Sep '18

07 Sep '18

Is there any reference stating what oVirt 4.2 is really capable of? - Maximum number of vCPU per VM - Maximum amount of RAM per VM - Maximum number of Disks per VM - Maximum amount of Disk Capacity per VM - Maximum number of Virtual Networks - Maximum number of Virtual Networks per VM ...

2 1

ovirt4 api create snapshot
by David David 07 Sep '18

07 Sep '18

hi i have a vm with 3 disks and i want to take a snapshot with only two disks how to do a multiple disk snapshot in the code below? snap = snaps_service.add( snapshot=types.Snapshot( description=snap_description, persist_memorystate=False, disk_attachments=[ types.DiskAttachment( disk=types.Disk( id=disk_id ) ) ] ), )

2 2

[ANN] oVirt 4.2.6 is now generally available
by Sandro Bonazzola 07 Sep '18

07 Sep '18

The oVirt Project is pleased to announce the general availability of oVirt 4.2.6, as of September 3rd, 2018. This update is the sixth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] - oVirt Windows Guest Tools is available [2] Additional Resources: * Read more about the oVirt 4.2.6 release highlights: http://www.ovirt.org/release/4.2.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.6/ [2] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

5 15

vm operation after host fence
by Kapetanakis Giannis 06 Sep '18

06 Sep '18

Hi, Last night we have an incident of a failed host. Engine issued a fence but did not restart the vms running on that node on other operational hosts. I'd like to know if this is normal or I can tune it somehow. Here are some relevant logs from engine: 2018-09-05 03:00:51,496+03 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-827644) [] Host 'v3' is not responding. It will stay in Connecting state for a grace period of 63 seconds and after that an attempt to fence the host will be issued. 2018-09-05 03:01:11,945+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-57) [] Failed to fetch vms info for host 'v3' - skipping VMs monitoring. 2018-09-05 03:01:48,028+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-827679) [] EVENT_ID: VM_SET_TO_UNKNOWN_STATUS(142), VM vm7 was set to the Unknown status. 2018-09-05 03:02:10,033+03 INFO [org.ovirt.engine.core.bll.pm.StopVdsCommand] (EE-ManagedThreadFactory-engine-Thread-827680) [30369e01] Power-Management: STOP of host 'v3' initiated. 2018-09-05 03:02:55,935+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-827680) [3adcac38] EVENT_ID: VM_WAS_SET_DOWN_DUE_TO_HOST_REBOOT_OR_MANUAL_FENCE(143), Vm vm7 was shut down due to v3 host reboot or manual fence 2018-09-05 03:02:56,018+03 INFO [org.ovirt.engine.core.bll.pm.StopVdsCommand] (EE-ManagedThreadFactory-engine-Thread-827680) [ea0f582] Power-Management: STOP host 'v3' succeeded. 2018-09-05 03:08:20,818+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [326878] EVENT_ID: VDS_DETECTED(13), Status of host v3 was set to Up. 2018-09-05 03:08:23,391+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [] VM '3b1262ef-7fff-40af-b85e-9fd01a4f422b'(vm7) was unexpectedly detected as 'Down' on VDS '4970369d-21c2-467d-9247-c73ca2d71b3e'(v3) (expected on 'null') As you can see, engine does a fence on node v3. vm7 as well as the others running on that node did not re-start. any tips? engine is ovirt-engine-4.2.5.3-1.el7.noarch and host is vdsm-4.20.35-1.el7.x86_64 best regards, Giannis

2 2