- Users - oVirt List Archives

Problem connect console spice vm
by Marcelo Leandro 23 Aug '16

23 Aug '16

Hello, I have a problem while connect on the console the vms, it's possible access the console if my computer is in same network of storage. is it normal? Thanks.

1 1

Windows 2012 R2 on Xeon E5320
by Niksa Baldun 23 Aug '16

23 Aug '16

Hello, I am trying to install Windows Server 2012 R2 in oVirt 4.0 on Xeon E5320, which is recognized as Intel Conroe, When creating a new VM, I am getting the message "The guest OS doesn't support the following CPUs: opteron_g1, conroe". There is not much information on the net, but I did find one post which said that this type of processor is missing "CX16" feature and that KVM can succesfully boot Win 2012 R2 with "-cpu 'Conroe',+cx16" option. Is there a way to accomplish this in oVirt? I can see "Custom CPU type" field in VM properties, but I can't find any documentation on how to use it. Thanks, Nikša

1 0

ovirt becomes unusable if master storage domain lost
by Bill Bill 23 Aug '16

23 Aug '16

--_000_SN2PR0801MB075254207EBE2ACA9D19B68AA6EB0SN2PR0801MB0752_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpIZWxsbywNCg0KSW4gdGVzdGluZyBmYXVsdCB0b2xlcmFuY2UvcmVjb3ZlcnkgcHJvY2VkdXJl cyBpZiB0aGUgbWFzdGVyIHN0b3JhZ2UgZG9tYWluIGlzIGxvc3QvcmVtb3ZlZCwgb3ZpcnQgYmVj b21lcyBwcmV0dHkgbXVjaCB1bnVzYWJsZS4gWW91IGNhbm5vdCBhZGQgbmV3IHN0b3JhZ2UgYXMg b1ZpcnQgd2lsbCBub3QgbW91bnQgaXQsIGV2ZW4gaWYgeW91IGNhbiBtb3VudCBpdCBtYW51YWxs eSB0byB0aGUgaG9zdC4gSWYgeW91IGZvcmNlIHJlbW92ZSB0aGUgb2xkIGZhaWxlZCBzdG9yYWdl IGRvbWFpbiB2aWEgdGhlIGVuZ2luZSBkYXRhYmFzZSwgeW914oCZcmUgZXNzZW50aWFsbHkgc2Ny ZXdlZCBzaW5jZSBpdCB3aWxsIGZhaWwgdG8gbW91bnQgQU5ZIG5ldyBzdG9yYWdlLg0KDQpJcyB0 aGVyZSBzb21lIHdvcmthcm91bmQgZm9yIHRoaXMgc28gdGhhdCBpZiB0aGUgb3JpZ2luYWwgbWFz dGVyIHN0b3JhZ2UgZG9tYWluIGJlY29tZXMgZGFtYWdlZCwgZmFpbHMsIGdvZXMgb2ZmbGluZSBl dGMgdGhhdCBvVmlydCBpcyBub3Qgc28gZGVwZW5kZW50IG9uIHRoaXMgT1IgYW5vdGhlciBzdG9y YWdlIGNhbiBjb250aW51ZSB0byBiZSBhZGRlZD8NCg0KUmlnaHQgbm93LCBJIGhhdmUgYW4gb1Zp cnQgZGF0YWNlbnRlciB3aXRoIG11bHRpcGxlIG5ldHdvcmtzLCByZWR1bmRhbnQgbmlj4oCZcyBl dGMgdGhhdCB0aGF0IGlzIGdvaW5nIHRvIGhhdmUgdG8gYmUgY29tcGxldGVseSByZW1vdmVkLCBy ZWNvbmZpZ3VyZWQgYW5kIHRoZW4gc2V0IHVwIGZyb20gc2NyYXRjaCBhZ2FpbiBlc3NlbnRpYWxs eSBkdWUgdG8gdGhlIG1hc3RlciBzdG9yYWdlIGRvbWFpbiBpc3N1ZS4NCg0K --_000_SN2PR0801MB075254207EBE2ACA9D19B68AA6EB0SN2PR0801MB0752_ Content-Type: text/html; charset="utf-8" Content-ID: <48A4EB3E01EE3349B07BE460817B0174(a)sct-15-1-485-2-msonline-outlook-1173a.templateTenant> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQouTXNv Q2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2Vj dGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEu MGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls ZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0iIzk1NEY3 MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86 cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IZWxsbyw8L3A+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt YWwiPkluIHRlc3RpbmcgZmF1bHQgdG9sZXJhbmNlL3JlY292ZXJ5IHByb2NlZHVyZXMgaWYgdGhl IG1hc3RlciBzdG9yYWdlIGRvbWFpbiBpcyBsb3N0L3JlbW92ZWQsIG92aXJ0IGJlY29tZXMgcHJl dHR5IG11Y2ggdW51c2FibGUuIFlvdSBjYW5ub3QgYWRkIG5ldyBzdG9yYWdlIGFzIG9WaXJ0IHdp bGwgbm90IG1vdW50IGl0LCBldmVuIGlmIHlvdSBjYW4gbW91bnQgaXQgbWFudWFsbHkgdG8gdGhl IGhvc3QuIElmIHlvdQ0KIGZvcmNlIHJlbW92ZSB0aGUgb2xkIGZhaWxlZCBzdG9yYWdlIGRvbWFp biB2aWEgdGhlIGVuZ2luZSBkYXRhYmFzZSwgeW914oCZcmUgZXNzZW50aWFsbHkgc2NyZXdlZCBz aW5jZSBpdCB3aWxsIGZhaWwgdG8gbW91bnQgQU5ZIG5ldyBzdG9yYWdlLjwvcD4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+ SXMgdGhlcmUgc29tZSB3b3JrYXJvdW5kIGZvciB0aGlzIHNvIHRoYXQgaWYgdGhlIG9yaWdpbmFs IG1hc3RlciBzdG9yYWdlIGRvbWFpbiBiZWNvbWVzIGRhbWFnZWQsIGZhaWxzLCBnb2VzIG9mZmxp bmUgZXRjIHRoYXQgb1ZpcnQgaXMgbm90IHNvIGRlcGVuZGVudCBvbiB0aGlzIE9SIGFub3RoZXIg c3RvcmFnZSBjYW4gY29udGludWUgdG8gYmUgYWRkZWQ/PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SaWdodCBub3cs IEkgaGF2ZSBhbiBvVmlydCBkYXRhY2VudGVyIHdpdGggbXVsdGlwbGUgbmV0d29ya3MsIHJlZHVu ZGFudCBuaWPigJlzIGV0YyB0aGF0IHRoYXQgaXMgZ29pbmcgdG8gaGF2ZSB0byBiZSBjb21wbGV0 ZWx5IHJlbW92ZWQsIHJlY29uZmlndXJlZCBhbmQgdGhlbiBzZXQgdXAgZnJvbSBzY3JhdGNoIGFn YWluIGVzc2VudGlhbGx5IGR1ZSB0byB0aGUgbWFzdGVyIHN0b3JhZ2UgZG9tYWluIGlzc3VlLjwv cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2Zv bnQtZmFtaWx5OiZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyxzZXJpZiI+PG86cD4mbmJzcDs8 L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_SN2PR0801MB075254207EBE2ACA9D19B68AA6EB0SN2PR0801MB0752_--

2 1

hosted-engine deploy error terminal state
by Maxence Sartiaux 23 Aug '16

23 Aug '16

Hello, I try to deploy a hosted-engine (4.0.2) on my cluster from a existing engine, Everything works fine until i start the last step, my engine is up, cluster state ok, hosts state up ect ... When it come to the last step "Continue setup - oVirt-Engine installation is ready and ovirt-engine service is up" It get stuck on "Connecting to the Engine" and finally crash with [ ERROR ] Failed to execute stage 'Closing up': [-32605] No response for JSON-RPC Host.getCapabilities request. [ INFO ] Stage: Clean up [ ERROR ] Failed to execute stage 'Clean up': [-32605] No response for JSON-RPC Host.stopMonitoringDomain request. [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20160816155211.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy Log file is located at /var/log/ovirt-hosted-engine- setup/ovirt-hosted-engine-setup-20160816144914-xykpcl.log Exception in thread Client hypervisor1:54321: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/yajsonrpc/betterAsyncore.py", line 216, in process_requests count=1, File "/usr/lib64/python2.7/asyncore.py", line 220, in loop poll_fun(timeout, map) File "/usr/lib64/python2.7/asyncore.py", line 201, in poll2 readwrite(obj, flags) TypeError: 'NoneType' object is not callable hosted-engine-deploy and engine log are in attachements

2 2

(no subject)
by Matt . 22 Aug '16

22 Aug '16

I have one host which has been newly deployed having issues with: [root@host-01 ~]# tail -f /var/log/ovirt-hosted-engine-ha/agent.log MainThread::INFO::2016-08-23 02:39:16,799::hosted_engine::860::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-08-23 02:39:21,834::hosted_engine::860::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-08-23 02:39:26,894::hosted_engine::860::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-08-23 02:39:31,931::hosted_engine::860::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING Now I tried to cleant he metadata, force it, whatever I tried, I get this: [root@host-01 ~]# hosted-engine --clean-metadata --force-cleanup /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/vds_client.py:25: DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli from vdsm import vdscli INFO:ovirt_hosted_engine_ha.agent.agent.Agent:ovirt-hosted-engine-ha agent 2.0.2 started INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Found certificate common name: host-01.my.domain INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Initializing VDSM /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Connecting the storage INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting storage server /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting storage server /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Refreshing the storage domain /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Preparing images INFO:ovirt_hosted_engine_ha.lib.image.Image:Preparing images /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Reloading vm.conf from the shared storage domain INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config:Trying to get a fresher copy of vm configuration from the OVF_STORE /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore:Found OVF_STORE: imgUUID:8bf93e0a-7665-49b1-b183-29d3ecee2fab, volUUID:63ea7e1b-491f-484f-87e3-d0c1c5de8b9b /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore:Found OVF_STORE: imgUUID:774d6560-62ec-452a-9397-efeb9acff78c, volUUID:9cc05166-af8d-4c9c-bc30-60c324fd3799 /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) /usr/lib/python2.7/site-packages/yajsonrpc/stomp.py:352: DeprecationWarning: Dispatcher.pending is deprecated. Use Dispatcher.socket.pending instead. pending = getattr(dispatcher, 'pending', lambda: 0) INFO:ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore:Extracting Engine VM OVF from the OVF_STORE INFO:ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore:OVF_STORE volume path: /rhev/data-center/mnt/flr-01.my.domain:_vol_vol0_oVIRT__HE/4093ad17-bef5-4e4b-9a16-259a98e20321/images/774d6560-62ec-452a-9397-efeb9acff78c/9cc05166-af8d-4c9c-bc30-60c324fd3799 INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config:Found an OVF for HE VM, trying to convert INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config:Got vm.conf from OVF_STORE INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:VDSM domain monitor status: PENDING What I also have seen is that when you run --host-id on a different host it says it cannot do a thing as that host already holds another lock on a file for that host you run it on. Anyone a clue what happens here ? It can access the hosted engine storage, so I wonder why this one doesn't want to do it's thing as it cannot for becoming a HA node it seems. Ideas are welcome. Thanks! Matt

1 0

Hosted Engine 3.6 Questions
by C Williams 22 Aug '16

22 Aug '16

Hello, We have an installation with 2 filers on CentOS 7.2 with the hosted engine appliance. We use iscsi for our backend storage. We have some issues We had to dedicate an entire dedicated storage domain for the sole use of the Hosted Engine appliance. Is this required ? Or can the Hosted Engine appliance co-exist on another storage domain with VMs ? I have not been able to migrate the Hosted Engine VM to other storage. Because of this limitation and to be efficient with our storage use, we asked our storage admin to make a small iscsi LUN 20GB for the storage domain for the appliance. However, we are constantly getting errors regarding low disk space for this domain even though it has only the 10GB appliance. Could this size problem be related to my problems with importing VMWare VMs into our larger (Multi TB) storage using the Import tool in 3.6. Thank You

3 3

Dedicated NICs for gluster network
by Nicolas Ecarnot 22 Aug '16

22 Aug '16

Hello, [Here : oVirt 3.5.3, 3 x CentOS 7.0 hosts with replica-3 gluster SD on the hosts]. On the switchs, I have created a dedicated VLAN to isolate the glusterFS traffic, but I'm not using it yet. I was thinking of creating a dedicated IP for each node's gluster NIC, and a DNS record by the way ("my_nodes_name_GL"), but I fear using this hostname or this ip in oVirt GUI host network interface tab, leading oVirt think this is a different host. Not being sure this fear is clearly described, let's say : - On each node, I create a second ip+(dns record in the soa) used by gluster, plugged on the correct VLAN - in oVirt gui, in the host network setting tab, the interface will be seen, with its ip, but reverse-dns-related to a different hostname. Here, I fear oVirt might check this reverse DNS and declare this NIC belongs to another host. I would also prefer not use a reverse pointing to the name of the host management ip, as this is evil and I'm a good guy. On your side, how do you cope with a dedicated storage network in case of storage+compute mixed hosts? -- Nicolas ECARNOT

5 11

Suddenly all VM's down including HostedEngine & NFSshares (except HE) unmounted
by Matt . 21 Aug '16

21 Aug '16

HI All, I'm trying to tackle an issues on 4.0.2 that sunddenly all VM's including the HostedEngine are just down at once. I have also seen that all NFS shares are unmounted except the HostedEngine Storage, which is on the same NFS device as well. I have checked the logs, nothing strange to see there, but as I run a vrrp setup and do some tests also I wonder if there is a duplicate IP brought up, could this make happen the whole system to go down and the Engine or VDSM unmounts the NFS shares ? My switches don't complain. It's strange that the HE share is only available after it happens. If so, this would be quite fragile and we should tackle where it goes wrong. Anyone seen this bahaviour ? Thanks, Matt

2 4

Cannot resolve prinicpal 'user@corp.domain.com' after attaching AD to ovirt-engine
by Danny Rehelis 21 Aug '16

21 Aug '16

Hi, After successfully attaching ovirt-engine 4.0.2.6-1.el7 to corporate AD, I'm unable to login using just 'user'. When typing 'user(a)domain.com' it works. Is this behavior by design? Cheers,

2 1

3.6 : VLAN / non VLAN
by Alexis HAUSER 21 Aug '16

21 Aug '16

hi, I'd like to know what happens when you create a new network, tagged with VLAN for example 25 and using em2 : - the packets outgoing from em2.25 are tagged, right ? - the packets outgoing from em2 are tagged or not ? - the result is packets inside ovirt are tagged, but when you go out of it and reach something from em2, are the packets still tagged ?

3 2