- Devel - oVirt List Archives

New dependency for development environment
by Ondra Machacek 09 Jan '20

09 Jan '20

Hello, we are going to merge a series of patches to master branch, which integrates ansible-runner with oVirt engine. When the patches will be merged you will need to install new package called ansible-runner- service-dev, and follow instructions so your dev-env will keep working smoothly(all relevant info will be also in README.adoc): 1) sudo dnf update ovirt-release-master 2) sudo dnf install -y ansible-runner-service-dev 3) Edit `/etc/ansible-runner-service/config.yaml` file as follows: --- playbooks_root_dir: '$PREFIX/share/ovirt-engine/ansible-runner-service-project' ssh_private_key: '$PREFIX/etc/pki/ovirt-engine/keys/engine_id_rsa' port: 50001 target_user: root Where `$PREFIX` is the prefix of your development environment prefix, which you've specified during the compilation of the engine. 4) Restart and enable ansible-runner-service: # systemctl restart ansible-runner-service # systemctl enable ansible-runner-service That's it, your dev-env should start using the ansible-runner-service for host-deployment etc. Please note that only Fedora 30/31 and Centos7 was packaged, and are natively supported! Thanks, Ondra

9 24

Failed to install ovirt-imageio-proxy for fc30
by Shani Leviim 08 Jan '20

08 Jan '20

Hi All, I ran into a dependencies issue while trying to install imageio over fc30. I currently have a ovirt-imageio-common-1.6.2-0.202001051603.git77cf282.fc30.x86_64 but when I'm trying to install ovirt-imageio-proxy, I'm getting the following error: Error: Problem: conflicting requests - nothing provides ovirt-imageio-common = 1.5.0 needed by ovirt-imageio-proxy-1.5.0-0.201812112104.gitf7d8234.fc30.noarch I've also noticed that the available version in the repository for fc30 is ovirt-imageio-proxy-1.5.0 [1] While version 1.6.2 is available for rhel7 [2]. Please assist. [1] https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc30/noarch/ovirt… [2] https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ovirt-… *Regards,* *Shani Leviim*

2 2

ovirt-engine has been tagged (ovirt-engine-4.3.8.2)
by Tal Nisan 07 Jan '20

07 Jan '20

1 0

OST is failing - Last successful run was Dec-13-2019
by Amit Bawer 06 Jan '20

06 Jan '20

Seems we have NFS permissions issue for el8 vdsm in some of the runs. Example from https://jenkins.ovirt.org/view/Amit/job/ovirt-system-tests_manual/6302/arti… : 2020-01-03 12:07:34,169-0500 INFO (MainThread) [vds] (PID: 1264) I am the actual vdsm 4.40.0.1458.git1fca84350 lago-basic-suite-master-host-1 (4.18.0-80.11.2.el8_0.x86_64) (vdsmd:152)... 2020-01-03 12:50:29,662-0500 ERROR (check/loop) [storage.Monitor] Error checking path /rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported/b92b26cf-fac4-4ccf-ba31-f6fb4184e302/dom_md/metadata (monitor:501) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/monitor.py", line 499, in _pathChecked delay = result.delay() File "/usr/lib/python3.6/site-packages/vdsm/storage/check.py", line 391, in delay raise exception.MiscFileReadException(self.path, self.rc, self.err) vdsm.storage.exception.MiscFileReadException: Internal file read failure: ('/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported/b92b26cf-fac4-4ccf-ba31-f6fb4184e302/dom_md/metadata', 1, bytearray(b"/usr/bin/dd: failed to open \'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_exported/b92b26cf-fac4-4ccf-ba31-f6fb4184e302/dom_md/metadata\': Operation not permitted\n")) 2020-01-03 12:50:30,112-0500 DEBUG (jsonrpc/7) [jsonrpc.JsonRpcServer] Calling 'StoragePool.disconnect' in bridge with {'storagepoolID': 'c90b137f-6e1f-4b9a-9612-da58910a2439', 'hostID': 2, 'scsiKey': 'c90b137f-6e1f-4b9a-9612-da58910a2439'} (__init__:329) 2020-01-03 12:50:30,114-0500 INFO (jsonrpc/7) [vdsm.api] START disconnectStoragePool(spUUID='c90b137f-6e1f-4b9a-9612-da58910a2439', hostID=2, remove=False, options=None) from=::ffff:192.168.201.4,38786, flow_id=8d05a1, task_id=95573498-d1c7-41ad-ad33-28f2192b2b60 (api:48) Probably need to set NFS server export options as in https://bugzilla.redhat.com/show_bug.cgi?id=1776843#c7

2 2

Unexpected exception when trying to add a storage domain
by Dana Elfassy 05 Jan '20

05 Jan '20

Hi, When trying to add a storage domain to a 4.4 host I'm getting this error message: Error while executing action New NFS Storage Domain: Unexpected exception The errors from vdsm.log: 2020-01-02 09:38:33,578-0500 ERROR (jsonrpc/0) [storage.initSANLock] Cannot initialize SANLock for domain 6ca1e203-5595-47e5-94b8-82a7e69d99a9 (clusterlock:259) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 250, in initSANLock lockspace_name, idsPath, align=alignment, sector=block_size) sanlock.SanlockException: (-202, 'Sanlock lockspace write failure', 'IO timeout') 2020-01-02 09:38:33,579-0500 INFO (jsonrpc/0) [vdsm.api] FINISH createStorageDomain error=Could not initialize cluster lock: () from=::ffff:192.168.100.1,36452, flow_id=17dc614 e, task_id=05c2107a-4d59-48d0-a2f7-0938f051c9ab (api:52) 2020-01-02 09:38:33,582-0500 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='05c2107a-4d59-48d0-a2f7-0938f051c9ab') Unexpected error (task:874) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 250, in initSANLock lockspace_name, idsPath, align=alignment, sector=block_size) sanlock.SanlockException: (-202, 'Sanlock lockspace write failure', 'IO timeout') During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 881, in _run return fn(*args, **kargs) File "<decorator-gen-121>", line 2, in createStorageDomain File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2622, in createStorageDomain max_hosts=max_hosts) File "/usr/lib/python3.6/site-packages/vdsm/storage/nfsSD.py", line 120, in create fsd.initSPMlease() File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 974, in initSPMlease return self._manifest.initDomainLock() File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 620, in initDomainLock self._domainLock.initLock(self.getDomainLease()) File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 308, in initLock block_size=self._block_size) File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 260, in initSANLock raise se.ClusterLockInitError() vdsm.storage.exception.ClusterLockInitError: Could not initialize cluster lock: () 2020-01-02 09:38:33,583-0500 INFO (jsonrpc/0) [storage.TaskManager.Task] (Task='05c2107a-4d59-48d0-a2f7-0938f051c9ab') aborting: Task is aborted: 'value=Could not initialize cluster lock: () abortedcode=701' (task:1184) 2020-01-02 09:38:33,584-0500 ERROR (jsonrpc/0) [storage.Dispatcher] FINISH createStorageDomain error=Could not initialize cluster lock: () (dispatcher:83) 2020-01-02 09:38:33,584-0500 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call StorageDomain.create failed (error 701) in 18.70 seconds (__init__:312) 2020-01-02 09:38:33,730-0500 INFO (jsonrpc/2) [vdsm.api] START disconnectStorageServer(domType=1, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'protocol_version': 'auto', 'port': '', 'iqn': '', 'connection': 'vserver-spider.eng.lab.tlv.redhat.com:/pub/delfassy/nfs1', 'ipv6_enabled': 'false', 'id': 'bf075967-060b-4e60-9b0b-bb170fe073f9', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:192.168.100.1,36452, flow_id=f4f79738-b361-4688-95c5-3454f52b505d, task_id=dd7266ed-69ec-4e5b-9216-850d9db8ea3b (api:48) Can someone help me with it? Thanks, Dana

2 4

Who's the owner of "vdsm_hooks/checkimages/before_vm_start.py"?
by Pavel Bar 03 Jan '20

03 Jan '20

Hi, Can someone please point me to a relevant person? It looks like there is a potential issue with "*getImageSize()*" function there: *'image_bytes' might be referenced before assignment*. There is also a suspicion that this code is not used at all, so instead of fixing it might be a good idea to just delete it. See the code below: def getImageSize(disk_image, driver_type): ''' Obtain qcow2 image size in GiBs ''' if driver_type == 'block': dev_buffer = ' ' * 8 with open(disk_image) as device: dev_buffer = fcntl.ioctl(device.fileno(), BLKGETSIZE64, dev_buffer) image_bytes = struct.unpack(FORMAT, dev_buffer)[0] elif driver_type == 'file': image_bytes = os.stat(disk_image).st_size return float(image_bytes / GIB) Thank you in advance! Pavel

2 1

OST Fails for missing glusterfs mirrors at host-deploy
by Amit Bawer 02 Jan '20

02 Jan '20

Snippet From: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6293/console 23:31:25 + cd /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master 23:31:25 + lago ovirt deploy 23:31:26 @ Deploy oVirt environment: 23:31:26 # Deploy environment: 23:31:26 * [Thread-2] Deploy VM lago-basic-suite-master-host-0: 23:31:26 * [Thread-3] Deploy VM lago-basic-suite-master-host-1: 23:31:26 * [Thread-4] Deploy VM lago-basic-suite-master-engine: 23:32:15 * [Thread-3] Deploy VM lago-basic-suite-master-host-1: Success (in 0:00:49) 23:32:39 STDERR 23:32:39 + yum -y install ovirt-host 23:32:39 Error: Error downloading packages: 23:32:39 Cannot download glusterfs-6.6-1.el8.x86_64.rpm: All mirrors were tried 23:32:39 23:32:39 - STDERR 23:32:39 + yum -y install ovirt-host 23:32:39 Error: Error downloading packages: 23:32:39 Cannot download glusterfs-6.6-1.el8.x86_64.rpm: All mirrors were tried 23:32:39 23:32:39 * [Thread-2] Deploy VM lago-basic-suite-master-host-0: ERROR (in 0:01:13) 23:38:05 * [Thread-4] Deploy VM lago-basic-suite-master-engine: ERROR (in 0:06:39) 23:38:05 # Deploy environment: ERROR (in 0:06:39) 23:38:06 @ Deploy oVirt environment: ERROR (in 0:06:39) 23:38:06 Error occured, aborting 23:38:06 Traceback (most recent call last): 23:38:06 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run 23:38:06 self.cli_plugins[args.ovirtverb].do_run(args) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run 23:38:06 self._do_run(**vars(args)) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 573, in wrapper 23:38:06 return func(*args, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 584, in wrapper 23:38:06 return func(*args, prefix=prefix, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 181, in do_deploy 23:38:06 prefix.deploy() 23:38:06 File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, in wrapper 23:38:06 return func(*args, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 127, in wrapper 23:38:06 return func(*args, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/ovirtlago/prefix.py", line 284, in deploy 23:38:06 return super(OvirtPrefix, self).deploy() 23:38:06 File "/usr/lib/python2.7/site-packages/lago/sdk_utils.py", line 50, in wrapped 23:38:06 return func(*args, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, in wrapper 23:38:06 return func(*args, **kwargs) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1671, in deploy 23:38:06 self.virt_env.get_vms().values() 23:38:06 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 104, in invoke_in_parallel 23:38:06 return vt.join_all() 23:38:06 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 23:38:06 queue.put({'return': func()}) 23:38:06 File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1662, in _deploy_host 23:38:06 host.name(), 23:38:06 LagoDeployError: /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master/default/scripts/_home_jenkins_agent_workspace_ovirt-system-tests_manual_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_1st_host_el7.sh failed with status 1 on lago-basic-suite-master-host-0 23:38:06 + res=1 23:38:06 + cd - 23:38:06 /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests 23:38:06 + return 1 23:38:06 + env_collect /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy 23:38:06 + local tests_out_dir=/home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy 23:38:06 + [[ -e /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master ]] 23:38:06 + mkdir -p /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master 23:38:06 + cd /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/deployment-basic-suite-master/current 23:38:06 + lago collect --output /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy 23:38:08 @ Collect artifacts: 23:38:08 # [Thread-1] lago-basic-suite-master-host-0: 23:38:08 # [Thread-2] lago-basic-suite-master-host-1: 23:38:08 # [Thread-3] lago-basic-suite-master-engine: 23:38:10 # [Thread-1] lago-basic-suite-master-host-0: Success (in 0:00:02) 23:38:10 # [Thread-2] lago-basic-suite-master-host-1: Success (in 0:00:02) 23:38:16 # [Thread-3] lago-basic-suite-master-engine: Success (in 0:00:07) 23:38:16 @ Collect artifacts: Success (in 0:00:07) 23:38:16 + cp -a logs /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests/test_logs/basic-suite-master/post-000_deploy/lago_logs 23:38:16 + cd - 23:38:16 /home/jenkins/agent/workspace/ovirt-system-tests_manual/ovirt-system-tests 23:38:16 + echo '@@@ ERROR: Failed in deploy stage' 23:38:16 @@@ ERROR: Failed in deploy stage

2 1

Tracking ovirt integration with gluster 7
by Strahil 30 Dec '19

30 Dec '19

Hello Dev List, Is there a bugzilla entry for tracking the progress of oVirt integration with Gluster v7 ? I have met some issues that I would be happy to share . Currently , I'm running oVirt 4.3 with Gluster 7.0 . Best Regards, Strahil Nikolov

1 0

Re: [ovirt-users] [ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by Strahil 25 Dec '19

25 Dec '19

Hi, If the VMs are starting properly and they don't use cloudinit - then the issue is not oVirt specific, but guest specific (Linux/Windows depending on guest OS). So your should check: 1. Does your host have any Netwprks out of sync (Host's network tab) If yes - put the server into maintenance and fix the issue (host's network tab) 2. Check each VM's configuration if it is defined to use CloudInit -> if yes, verify that cloudinit's service is running on the guest 3. Verify each problematic guest's network settings. If needed, set a static IP and try to ping another IP from the same subnet/Vlan . Best Regards, Strahil NikolovOn Dec 25, 2019 11:41, lifuqiong(a)sunyainfo.com wrote: >> >> >>> Dear All: >>> My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. >>> One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) >>> >>> the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 >>> by ovirt rest api. But the ip was changed to templated ip when the accident happened. >>> >>> the vm's os is centos. >>> >>> Hope get help from you soon, Thank you. >>> >>> Mark >>> Sincerely.

1 0

[ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by lifuqiong＠sunyainfo.com 25 Dec '19

25 Dec '19

Dear All: My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 by ovirt rest api. But the ip was changed to templated ip when the accident happened. the vm's os is centos. Hope get help from you soon, Thank you. Mark Sincerely.

1 0