- Users - oVirt List Archives

Restart VMs after failure
by Chris Adams 06 May '16

06 May '16

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

2 2

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

06 May '16

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

2 2

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

05 May '16

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

2 2

node unresponsive after reboot
by Cam Mac 05 May '16

05 May '16

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

3 5

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

05 May '16

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

3 3

Stale VM template
by Bhaskarakiran 05 May '16

05 May '16

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

2 2

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

05 May '16

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

2 1

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

04 May '16

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

3 6

cloned vm template id
by Dobó László 04 May '16

04 May '16

Hello, How can i get back the original template id after vm is cloned with python sdk? print api.vms.get(id=vm_id).template.id result: 00000000-0000-0000-0000-000000000000 (blank template) However under vm general tab on web ui, the tamplate name is showing correctli. regards, enax

3 10

Open in Full Screen
by Colin Coe 04 May '16

04 May '16

Hi all Is there a setting for globally turning on the console option of "Open in Full Screen"? Also, can the "Connect Automatically" be permanently and globally disabled? We're on RHEV 3.5.7 Thanks CC

3 3