- Users - oVirt List Archives

self-hosted ovirt-engine down
by siovelrm＠gmail.com 16 Mar '19

16 Mar '19

Hi, I have a big problem with ovirt. I use version 4.2.7 with self-hosted. The problem is that when I try to raise the vm of the ovirt-engine with the command: hosted-engine --vm-start, it appears in the output "VM exists and is down, cleaning up and restarting" when running: hosted-engine --vm-status appears --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : node1.softel.cu Host ID : 1 Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down_unexpected", "detail": "Down"} Score : 0 stopped : False Local maintenance : False crc32 : 02c3b5a4 local_conf_timestamp : 49529 Host timestamp : 49529 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=49529 (Sat Mar 16 02:39:10 2019) host-id=1 score=0 vm_conf_refresh_time=49529 (Sat Mar 16 02:39:11 2019) conf_on_shared_storage=True maintenance=False state=EngineUnexpectedlyDown stopped=False timeout=Thu Jan 1 08:49:39 1970 in /var/log/messages Mar 16 02:35:34 node1 vdsm[26151]: WARN Attempting to remove a non existing network: ovirtmgmt/0c3e1c08-3928-47f1-96a8-c6a8d0dc3241 Mar 16 02:35:34 node1 vdsm[26151]: WARN Attempting to remove a non existing net user: ovirtmgmt/0c3e1c08-3928-47f1-96a8-c6a8d0dc3241 Mar 16 02:35:34 node1 vdsm[26151]: WARN Attempting to remove a non existing network: ovirtmgmt/0c3e1c08-3928-47f1-96a8-c6a8d0dc3241 Mar 16 02:35:34 node1 vdsm[26151]: WARN Attempting to remove a non existing net user: ovirtmgmt/0c3e1c08-3928-47f1-96a8-c6a8d0dc3241 Mar 16 02:35:34 node1 vdsm[26151]: WARN File: /var/lib/libvirt/qemu/channels/0c3e1c08-3928-47f1-96a8-c6a8d0dc3241.org.qemu.guest_agent.0 already removed Please help!!

2 1

Self Hosted Engine failed during setup using oVirt Node 4.3
by Jagi Sarcilla 16 Mar '19

16 Mar '19

Hardware Specs Hypervisor: Supermicro A2SDi-16C-HLN4F Intel(R) Atom(TM) CPU C3955 @ 2.10GHz 16cores Samsung NVME 1TB Sandisk SSHD 1TB 256GB RAM 4 x 1G nics Storage: FreeNAS-11.2-RELEASE-U1 - NFS - iSCSI * Issues #1 using iscsi unable to discover the target using cockpit dashboard * Issue #2 using nfs can successfully connect but the host wont come up after shutdown by the installation * Error message: [ INFO ] TASK [oVirt.hosted-engine-setup : Check engine VM health] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.358141", "end": "2019-03-14 06:33:35.499429", "rc": 0, "start": "2019-03-14 06:33:35.141288", "stderr": "", "stderr_lines": [], "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=43479 (Thu Mar 14 06:33:34 2019)\\nhost-id=1\\nscore=0\\nvm_conf_refresh_time=43480 (Thu Mar 14 06:33:34 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineUnexpectedlyDown\\nstopped=False\\ntimeout=Thu Jan 1 07:04:46 1970\\n\", \"hostname\": \"dreamlevel-1.logistics.corp\", \"host-id\": 1, \"engine-status\": {\"reason\": \"bad vm status\", \"health\": \"bad\", \"vm\": \"down_unexpected\", \"detail\": \"Down\"}, \"score\": 0, \"stopped\": false, \"maintenance\": false, \"crc32\": \"de300a81\", \"local_conf_timestamp\": 43480, \"host-ts\": 43479}, \"global_maintenance\": false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=43479 (Thu Mar 14 06:33:34 2019)\\nhost-id=1\\nscore=0\\nvm_conf_refresh_time=43480 (Thu Mar 14 06:33:34 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineUnexpectedlyDown\\nstopped=False\\ntimeout=Thu Jan 1 07:04:46 1970\\n\", \"hostname\": \"dreamlevel-1.logistics.corp\", \"host-id\": 1, \"engine-status\": {\"reason\": \"bad vm status\", \"health\": \"bad\", \"vm\": \"down_unexpected\", \"detail\": \"Down\"}, \"score\": 0, \"stopped\": false, \"maintenance\": false, \"crc32\": \"de300a81\", \"local_conf_timestamp\": 43480, \"host-ts\": 43479}, \"global_maintenance\": false}"]} [ INFO ] TASK [oVirt.hosted-engine-setup : Check VM status at virt level] [ INFO ] TASK [oVirt.hosted-engine-setup : debug] [ INFO ] ok: [localhost] [ INFO ] TASK [oVirt.hosted-engine-setup : Fail if engine VM is not running] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM is not running, please check vdsm logs"} 2019-03-14 06:33:41,168-0400 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Check VM status at virt level', 'ansible_result': u"type: <type 'dict'>\nstr: {'_ansible_parsed': True, 'stderr_lines': [], u'changed': True, u'end': u'2019-03-14 06:33:39.429283', '_ansible_no_log': False, u'stdout': u'', u'cmd': u'virsh -r list | grep HostedEngine | grep running', u'rc': 1, u'stderr': u'', u'delta': u'0:00:00.118398', u'invocation': {u'module_args': {u'crea", 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml'} 2019-03-14 06:33:41,168-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8948c2fd0> kwargs ignore_errors:True 2019-03-14 06:30:45,000-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:30:50,678-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894782490> kwargs 2019-03-14 06:30:56,369-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894675490> kwargs 2019-03-14 06:31:02,059-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8950ff750> kwargs 2019-03-14 06:31:07,738-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:31:13,429-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8947824d0> kwargs 2019-03-14 06:31:19,118-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8947c2390> kwargs 2019-03-14 06:31:24,797-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894750b10> kwargs 2019-03-14 06:31:30,481-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:31:36,174-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894782490> kwargs 2019-03-14 06:31:41,852-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894675490> kwargs 2019-03-14 06:31:47,534-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8947c2390> kwargs 2019-03-14 06:31:53,226-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:31:58,908-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8947824d0> kwargs 2019-03-14 06:32:04,592-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8945f9f10> kwargs 2019-03-14 06:32:10,266-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944fb390> kwargs 2019-03-14 06:32:15,948-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:32:21,630-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894782490> kwargs 2019-03-14 06:32:27,316-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894675490> kwargs 2019-03-14 06:32:33,016-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8945f9f10> kwargs 2019-03-14 06:32:38,702-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:32:44,382-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8947824d0> kwargs 2019-03-14 06:32:50,063-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8950ff750> kwargs 2019-03-14 06:32:55,745-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894750b10> kwargs 2019-03-14 06:33:01,422-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8944dd810> kwargs 2019-03-14 06:33:07,107-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894782490> kwargs 2019-03-14 06:33:12,794-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe894675490> kwargs 2019-03-14 06:33:18,470-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe8950ff750> kwargs Engine VM status: EngineUnexpectedlyDown-EngineDown. * Manually start the Engine VM via virsh: error: Failed to start domain HostedEngine error: the CPU is incompatible with host CPU: Host CPU does not provide required features: pcid

3 10

Broken dependencies in CentOS7 hosts upgrading to 4.2.8 from 4.2.7
by Roberto Nunin 15 Mar '19

15 Mar '19

Hi I have some oVirt clusters, in various config. One cluster based on CentOS7 hosts, another based on ovirt-node-ng. While the second was successfully updated from 4.2.7 to 4.2.8, attempts to update hosts of the first one ends with: Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2) Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3 Installed: libvirt-daemon-kvm-4.5.0-10.el7.x86_64 (@base) libvirt-daemon-kvm = 4.5.0-10.el7 Being a CentOS7 installation and not an ovirt-node-ng, I cannot follow the notice in : https://lists.ovirt.org/archives/list/users@ovirt.org/message/AJUBXAIGXVD5U… The only way to have libvirt-daemon-kvm release 4-5-0.10_6.4 (and not 6.3) is to enable CentOS Updates repo. Looking at host-deploy log looks fine, but It's safe to enable that repo ? There is another, safest method to update these hosts to the latest version of 4.2 ? Thanks in advance -- Roberto Nunin

1 0

Discard a snapshot
by Mitja Mihelič 15 Mar '19

15 Mar '19

Hi! We have run into a problem migrating a VM's disk. While doing a live disk migration it all went well until "Removing Snapshot Auto-generated for Live Storage Migration". The operation started and got stuck in the "Preparing to merge" stage. The task was visible as an async task for a couple of days, then dissapeared. The snapshot named "Auto-generated for Live Storage Migration" still exists. If we try to start the VM it produces the following error: VM VM_NAME_HERE is down with error. Exit message: Bad volume specification {u'index': 0, u'domainID': u'47ee9bde-4f18-43c2-9383-0d30a27d1ae7', 'reqsize': '0', u'format': u'cow', u'bootOrder': u'1', u'address': {u'function': u'0x0', u'bus': u'0x00', u'domain': u'0x0000', u'type': u'pci', u'slot': u'0x05'}, u'volumeID': u'3b0184b7-5c5d-4669-8b3a-04880883118a', 'apparentsize': '19193135104', u'imageID': u'35599677-250a-4586-9db1-4df8f3291164', u'discard': False, u'specParams': {}, u'readonly': u'false', u'iface': u'virtio', u'optional': u'false', u'deviceId': u'35599677-250a-4586-9db1-4df8f3291164', 'truesize': '19193135104', u'poolID': u'35628205-9fa3-41de-b914-84f9adb633e4', u'device': u'disk', u'shared': u'false', u'propagateErrors': u'off', u'type': u'disk'}. From what I understand the data access path is snapshot->"disk before snapshot". And since the snapshot is corrupted it cannot be accessed and the whole VM start process fails. I believe that the disk before the snapshot was made is still intact. How can we discard the whole snapshot so that are left only with the state before the snapshot was made? We can afford to lose the data in the snapshot. Best regards, Mitja

1 0

oVirt 4.3.1 - Remove VM greyed out
by Strahil Nikolov 15 Mar '19

15 Mar '19

Hi Community, I have the following problem.A VM was created based on template and after poweroff/shutdown it cannot be removed - the button is greyed-out. Anyone who got such an issue ?Any hint where to look for ? Best Regards,Strahil Nikolov

1 1

Migrating VMs from ovirt-4.1.1 to ovirt-4.2.8
by Wood Peter 15 Mar '19

15 Mar '19

Hi, I need to migrate a few dozen VMs from ovirt-4.1.1 to ovirt-4.2.8. I did a few following this procedure: VMs export -> Detach Export domain -> Attach Export to new ovirt -> Import VMs Importing from VMware is one step only process. All I have to do is select VMware for Source in the Import page and then import the VMs I need. I feel like I'm missing something. Is there a way to import VMs from another ovirt deployment similar to import from VMware i.e. without going through Export storage domain? Thank you, -- Peter

2 1

hosted-engine --deploy fails on iSCSI while trying to connect to retrieved ipv6 address, even while forcing ipv4 with --4
by Guillaume Pavese 15 Mar '19

15 Mar '19

I try to deploy hosted-engine 4.3.2-rc2 on iSCSI I put a ipv4 portal address and targets get discovered. However they are are returned by the Synology hosts with both ipv4 and ipv6 adresses. LUN discovery then fails while attempting to connect to ipv6 address I tried hosted-engine --deploy --4 to force ipv4 but that fails too. Please specify the storage you would like: iscsi Please specify the iSCSI portal IP address: 10.199.9.16 Please specify the iSCSI portal port [3260]: Please specify the iSCSI discover user: Please specify the iSCSI discover password: Please specify the iSCSI portal login user: Please specify the iSCSI portal login password: [ INFO ] Discovering iSCSI targets [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Prepare iSCSI parameters] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : iSCSI discover with REST API] [ INFO ] ok: [localhost] The following targets have been found: [1] iqn.2000-01.com.synology:SVC-STO-FR-301.Target-1.2dfed4a32a TPGT: 1, portals: 10.199.9.16:3260 fe80::211:32ff:fe6d:6ddb:3260 [2] iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a TPGT: 1, portals: 10.199.9.16:3260 fe80::211:32ff:fe6d:6ddb:3260 in Host's logs : mars 15 09:32:25 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]:conn 0 login rejected: initiator error (02/00) mars 15 09:32:25 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: Connection1:0 to [target: iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a, portal: 10.199.9.16,3260] through [iface: default] is shutdown. mars 15 09:32:27 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) ... mars 15 09:33:21 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) mars 15 09:33:24 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) mars 15 09:33:27 vs-inf-int-kvm-fr-304-210.hostics.fr vdsm[26174]: WARN Worker blocked: <Worker name=jsonrpc/1 running <Task <JsonRpcTask {'params': {u'connectionParams': [{u'port': u'3260', u'connection': u'fe80::211:32ff:fe6d:6ddb', u'iqn': u'iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'true', u'password': '********', u'id': u'00000000-0000-0000-0000-000000000000'}], u'storagepoolID': u'00000000-0000-0000-0000-000000000000', u'domainType': 3}, 'jsonrpc': '2.0', 'method': u'StoragePool.connectStorageServer', 'id': u'31411035-df1d-4b61-ac37-2a138dbdbb00'} at 0x7fcb904ef390> timeout=60, duration=60.00 at 0x7fcb904ef410> task#=10 at 0x7fcb905977d0>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 195, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 262, in __call__ self._handler(self._ctx, self._req) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 305, in _serveRequest response = self._handle_request(req, ctx) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1095, in connectStorageServer connectionParams) File: "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 74, in wrapper result = ctask.prepare(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper return m(self, *a, **kw) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1179, in prepare result = self._run(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File: "<string>", line 2, in connectStorageServer File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2411, in connectStorageServer conObj.connect() File: "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 488, in connect iscsi.addIscsiNode(self._iface, self._target, self._cred) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsi.py", line 217, in addIscsiNode iscsiadm.node_login(iface.name, target.address, target.iqn) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsiadm.py", line 327, in node_login portal, "-l"]) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsiadm.py", line 122, in _runCmd return misc.execCmd(cmd, printable=printCmd, sudo=True, sync=sync) File: "/usr/lib/python2.7/site-packages/vdsm/common/commands.py", line 213, in execCmd (out, err) = p.communicate(data) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 924, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1706, in _communicate orig_timeout) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1779, in _communicate_with_poll ready = poller.poll(self._remaining_time(endtime)) mars 15 09:33:27 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Centos7.5 virtual machine installation is slow
by xilazz＠126.com 15 Mar '19

15 Mar '19

Software version 4.3.1.1-1. The virtual machine performed post-installation setup tasks for a long time during the process of creating Centos7.5 system.I don't know if any of you have.

1 0

upgrading failed from 4.2 to 4.3
by Abhishek Sahni 15 Mar '19

15 Mar '19

Hello Users, I am trying to upgrade ovirt-engine running on bare metal, following below guide, https://ovirt.org/release/4.3.0/ and it is getting failed every time with the below errors, engine-setup ============================ [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode. In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data. [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup detected, but Global Maintenance is not set. [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190314171026-wicgh1.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190314171042-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed =================================== I was using hosted engine on nodes earlier but later remove the nodes and using ovirt egine on seperate bare-metal. Any pointers? -- ABHISHEK SAHNI Mob : +91-990-701-5143

2 2

Check in API if host is in state "reconfiguring networks"
by Eduardo Mayoral 14 Mar '19

14 Mar '19

Hi, I am writing some provisioning scripts using the python API in which I add a number of hosts to an ovirt engine. To minimize the time the script takes, I would like to call host_service.setup_network() and host_service.commit_net_config() for each host with async=True and then get into a loop checking every few seconds for the status of the hosts until all of them have finished (so I can go on with another task such as configuring storage). I was able to do something similar for the install phase checking if host.status equals HostStatus.MAINTENANCE , but I cannot find in the documentation how to check when a host is in status "reconfiguring network". The web interface shows this, so surely there must be a way, but I have not managed to find it in the API documentation. Could somebody help? Thanks in advance! -- Eduardo Mayoral Jimeno Systems engineer, platform department. Arsys Internet. emayoral(a)arsys.es - +34 941 620 105 - ext 2153

1 0