November 2020 - Devel - oVirt List Archives

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1818 - Failure!
by Yedidyah Bar David 15 Nov '20

15 Nov '20

On Sat, Nov 14, 2020 at 5:29 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1818/ https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1818… Error Message 'module' object has no attribute 'guest_os_image_name' Stacktrace Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/loader.py", line 418, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/home/jenkins/agent/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 88, in <module> GUEST_IMAGE_NAME = versioning.guest_os_image_name() AttributeError: 'module' object has no attribute 'guest_os_image_name' Seems to be caused by: https://gerrit.ovirt.org/112196 Can you please have a look? Thanks. Best regards, -- Didi

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.3.12)
by Tal Nisan 13 Nov '20

13 Nov '20

2 1

Travis builds
by Vojtech Juranek 11 Nov '20

11 Nov '20

Hi, recently, I noticed Travis builds waits in the queue for a very long time. Looking around I found out Travis probably reduced resources for OSS projects. Also I found out all projects should migrate from travis-ci.org to travis- ci.com by end of December 2020 [1] (see Q. When will the migration from travis-ci.org to travis-ci.com be completed?). Recently they announce new pricing model [2] when OSS projects will get some initial credit and after that either has to pay or ask the support for another credit (see section "Building on a public repositories only" in [2]). Maybe time to migrate away from travis-ci to something else, e.g. GH Actions? Thoughts? Vojta [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

3 4

ovirt-engine has been tagged (ovirt-engine-4.4.4)
by Tal Nisan 11 Nov '20

11 Nov '20

1 0

[ANN] oVirt 4.4.3 is now generally available
by Sandro Bonazzola 10 Nov '20

10 Nov '20

oVirt 4.4.3 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.3 , as of November 10th, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.3 Release? This update is the third in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) Please note that this release introduces cluster compatibility level 4.5 which is supported only with Red Hat Enterprise Linux 8.3 or equivalent. oVirt Node and Appliance have been updated, including: - oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/ - Ansible 2.9.15: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.3 release highlights: https://www.ovirt.org/release/4.4.3/ - 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] https://www.ovirt.org/release/4.4.3/ <https://www.ovirt.org/release/4.4.3/> [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Change compatibility level for data center/cluster during upgrade - what exactly are we changing?
by Patrick Chiang 10 Nov '20

10 Nov '20

Hi all, From the upgrade procedure, when we completed most upgrade tasks, we have to change the compatibility level in cluster and data center, and then restart all guest VM afterwards.It seems no down time expected with these 2 changes from the procedure. I wonder what exactly we are changing (a setting in the database/file??) and most important of all, whether there will be a few seconds down time when we made those changes to "data center"? Because I worried if a data center change could lead to storage domain's down time and eventually force hypervisors, guest VM restart before expected time. (My hosts/guest VM directly use HP 3par's storage as boot disks/data disks...) Hope anyone can share any experience on this. Thank you, Patrick Chiang

2 1

[OST] Network suites fails, 6+ days runtime?
by Nir Soffer 09 Nov '20

09 Nov '20

I have a trivial patch: https://gerrit.ovirt.org/c/112068 This should not have any effect on the network tests, but I ran the tests twice, and the network suite fails in both runs: - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… The first run waited in the queue, 1 day 12 hours then ran for 11 hours. The second run waited in the queue for 2 days 21 hours and then ran for 19 hours. This is a total of 135 hours waiting for test results! Looks like we don't have the resources to test OST patches. The current way testing 8 suites for every patch is not workable. Can someone look at the network suite failure? Should we remove it from the test matrix? Nir

3 4

How to set up a (rh)el8 machine for running OST
by Marcin Sobczyk 09 Nov '20

09 Nov '20

Hi All, there are multiple pieces of information floating around on how to set up a machine for running OST. Some of them outdated (like dealing with el7), some of them more recent, but still a bit messy. Not long ago, in some email conversation, Milan presented an ansible playbook that provided the steps necessary to do that. We've picked up the playbook, tweaked it a bit, made a convenience shell script wrapper that runs it, and pushed that into OST project [1]. This script, along with the playbook, should be our single-source-of-truth, one-stop solution for the job. It's been tested by a couple of persons and proved to be able to set up everything on a bare (rh)el8 machine. If you encounter any problems with the script please either report it on the devel mailing list, directly to me, or simply file a patch. Let's keep it maintained. Regards, Marcin [1] https://gerrit.ovirt.org/#/c/111749/

6 14

virt-sparsify failed (was: [oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 479 - Failure!)
by Yedidyah Bar David 09 Nov '20

09 Nov '20

Hi all, On Mon, Oct 12, 2020 at 5:17 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Above failed with: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… vdsm.log has: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… 2020-10-11 22:05:14,695-0400 INFO (jsonrpc/1) [api.host] FINISH getJobs return={'jobs': {'05eaea44-7e4c-4442-9926-2bcb696520f1': {'id': '05eaea44-7e4c-4442-9926-2bcb696520f1', 'status': 'failed', 'description': 'sparsify_volume', 'job_type': 'storage', 'error': {'code': 100, 'message': 'General Exception: (\'Command [\\\'/usr/bin/virt-sparsify\\\', \\\'--machine-readable\\\', \\\'--in-place\\\', \\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/8b292c13-fd8a-4a7c-903c-5724ec742c10/images/a367c179-2ac9-4930-abeb-848229f81c97/515fcf06-8743-45d1-9af8-61a0c48e8c67\\\'] failed with rc=1 out=b\\\'3/12\\\\n{ "message": "libguestfs error: guestfs_launch failed.\\\\\\\\nThis usually means the libguestfs appliance failed to start or crashed.\\\\\\\\nDo:\\\\\\\\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\\\\\\nand run the command again. For further information, read:\\\\\\\\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\\\\\\nYou can also run \\\\\\\'libguestfs-test-tool\\\\\\\' and post the *complete* output\\\\\\\\ninto a bug report or message to the libguestfs mailing list.", "timestamp": "2020-10-11T22:05:08.397538670-04:00", "type": "error" }\\\\n\\\' err=b"virt-sparsify: error: libguestfs error: guestfs_launch failed.\\\\nThis usually means the libguestfs appliance failed to start or crashed.\\\\nDo:\\\\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\\nand run the command again. For further information, read:\\\\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\\nYou can also run \\\'libguestfs-test-tool\\\' and post the *complete* output\\\\ninto a bug report or message to the libguestfs mailing list.\\\\n\\\\nIf reporting bugs, run virt-sparsify with debugging enabled and include the \\\\ncomplete output:\\\\n\\\\n virt-sparsify -v -x [...]\\\\n"\',)'}}}, 'status': {'code': 0, 'message': 'Done'}} from=::ffff:192.168.201.4,43318, flow_id=365642f4-2fe2-45df-937a-f4ca435eea38 (api:54) 2020-10-11 22:05:14,695-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Return 'Host.getJobs' in bridge with {'05eaea44-7e4c-4442-9926-2bcb696520f1': {'id': '05eaea44-7e4c-4442-9926-2bcb696520f1', 'status': 'failed', 'description': 'sparsify_volume', 'job_type': 'storage', 'error': {'code': 100, 'message': 'General Exception: (\'Command [\\\'/usr/bin/virt-sparsify\\\', \\\'--machine-readable\\\', \\\'--in-place\\\', \\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/8b292c13-fd8a-4a7c-903c-5724ec742c10/images/a367c179-2ac9-4930-abeb-848229f81c97/515fcf06-8743-45d1-9af8-61a0c48e8c67\\\'] failed with rc=1 out=b\\\'3/12\\\\n{ "message": "libguestfs error: guestfs_launch failed.\\\\\\\\nThis usually means the libguestfs appliance failed to start or crashed.\\\\\\\\nDo:\\\\\\\\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\\\\\\nand run the command again. For further information, read:\\\\\\\\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\\\\\\nYou can also run \\\\\\\'libguestfs-test-tool\\\\\\\' and post the *complete* output\\\\\\\\ninto a bug report or message to the libguestfs mailing list.", "timestamp": "2020-10-11T22:05:08.397538670-04:00", "type": "error" }\\\\n\\\' err=b"virt-sparsify: error: libguestfs error: guestfs_launch failed.\\\\nThis usually means the libguestfs appliance failed to start or crashed.\\\\nDo:\\\\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\\nand run the command again. For further information, read:\\\\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\\nYou can also run \\\'libguestfs-test-tool\\\' and post the *complete* output\\\\ninto a bug report or message to the libguestfs mailing list.\\\\n\\\\nIf reporting bugs, run virt-sparsify with debugging enabled and include the \\\\ncomplete output:\\\\n\\\\n virt-sparsify -v -x [...]\\\\n"\',)'}}} (__init__:356) /var/log/messages has: Oct 11 22:04:51 lago-basic-suite-master-host-0 kvm[80601]: 1 guest now active Oct 11 22:05:06 lago-basic-suite-master-host-0 journal[80557]: Domain id=1 name='guestfs-hl0ntvn92rtkk2u0' uuid=05ea5a53-562f-49f8-a8ca-76b45c5325b4 is tainted: custom-argv Oct 11 22:05:06 lago-basic-suite-master-host-0 journal[80557]: Domain id=1 name='guestfs-hl0ntvn92rtkk2u0' uuid=05ea5a53-562f-49f8-a8ca-76b45c5325b4 is tainted: host-cpu Oct 11 22:05:06 lago-basic-suite-master-host-0 kvm[80801]: 2 guests now active Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: internal error: End of file from qemu monitor Oct 11 22:05:08 lago-basic-suite-master-host-0 kvm[80807]: 1 guest now active Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: cannot resolve symlink /tmp/libguestfseTG8xF/console.sock: No such file or directoryKN<F3>L^? Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: cannot resolve symlink /tmp/libguestfseTG8xF/guestfsd.sock: No such file or directoryKN<F3>L^? Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: cannot lookup default selinux label for /tmp/libguestfs1WkcF7/overlay1.qcow2 Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: cannot lookup default selinux label for /var/tmp/.guestfs-36/appliance.d/kernel Oct 11 22:05:08 lago-basic-suite-master-host-0 journal[80557]: cannot lookup default selinux label for /var/tmp/.guestfs-36/appliance.d/initrd Oct 11 22:05:08 lago-basic-suite-master-host-0 vdsm[74096]: ERROR Job '05eaea44-7e4c-4442-9926-2bcb696520f1' failed#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/vdsm/jobs.py", line 159, in run#012 self._run()#012 File "/usr/lib/python3.6/site-packages/vdsm/storage/sdm/api/sparsify_volume.py", line 57, in _run#012 virtsparsify.sparsify_inplace(self._vol_info.path)#012 File "/usr/lib/python3.6/site-packages/vdsm/virtsparsify.py", line 40, in sparsify_inplace#012 commands.run(cmd)#012 File "/usr/lib/python3.6/site-packages/vdsm/common/commands.py", line 101, in run#012 raise cmdutils.Error(args, p.returncode, out, err)#012vdsm.common.cmdutils.Error: Command ['/usr/bin/virt-sparsify', '--machine-readable', '--in-place', '/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/8b292c13-fd8a-4a7c-903c-5724ec742c10/images/a367c179-2ac9-4930-abeb-848229f81c97/515fcf06-8743-45d1-9af8-61a0c48e8c67'] failed with rc=1 out=b'3/12\n{ "message": "libguestfs error: guestfs_launch failed.\\nThis usually means the libguestfs appliance failed to start or crashed.\\nDo:\\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\nand run the command again. For further information, read:\\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\nYou can also run \'libguestfs-test-tool\' and post the *complete* output\\ninto a bug report or message to the libguestfs mailing list.", "timestamp": "2020-10-11T22:05:08.397538670-04:00", "type": "error" }\n' err=b"virt-sparsify: error: libguestfs error: guestfs_launch failed.\nThis usually means the libguestfs appliance failed to start or crashed.\nDo:\n export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\nand run the command again. For further information, read:\n http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\nYou can also run 'libguestfs-test-tool' and post the *complete* output\ninto a bug report or message to the libguestfs mailing list.\n\nIf reporting bugs, run virt-sparsify with debugging enabled and include the \ncomplete output:\n\n virt-sparsify -v -x [...]\n" The next run of the job (480) did finish successfully. No idea if it was already fixed by a patch, or is simply a random/env issue. Is it possible to pass LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 without patching vdsm? Not sure. In any case, if this does not cause too much excess debug logging, perhaps better always pass it, to help retroactively analyze such failures. Or, patch virt-sparsify/libguestfs/whatever to always log at least enough information on failure even without passing these. Best regards, > Build Number: 479 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #479 > [hbraha] network: bond active slave test > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: basic-suite-master.test-scenarios.004_basic_sanity.test_sparsify_disk1 > > Error Message: > AssertionError: False != True after 600 seconds > > Stack Trace: > api_v4 = <ovirtsdk4.Connection object at 0x7fe717c60e50> > > @order_by(_TEST_LIST) > def test_sparsify_disk1(api_v4): > engine = api_v4.system_service() > disk_service = test_utils.get_disk_service(engine, DISK1_NAME) > with test_utils.TestEvent(engine, 1325): # USER_SPARSIFY_IMAGE_START event > disk_service.sparsify() > > with test_utils.TestEvent(engine, 1326): # USER_SPARSIFY_IMAGE_FINISH_SUCCESS > > pass > > ../basic-suite-master/test-scenarios/004_basic_sanity.py:295: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > /usr/lib64/python2.7/contextlib.py:24: in __exit__ > self.gen.next() > ../ost_utils/ost_utils/engine_utils.py:44: in wait_for_event > lambda: > ../ost_utils/ost_utils/assertions.py:97: in assert_true_within_long > assert_equals_within_long(func, True, allowed_exceptions) > ../ost_utils/ost_utils/assertions.py:82: in assert_equals_within_long > func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > func = <function <lambda> at 0x7fe7176dfb18>, value = True, timeout = 600 > allowed_exceptions = [], initial_wait = 0 > error_message = 'False != True after 600 seconds' > > def assert_equals_within( > func, value, timeout, allowed_exceptions=None, initial_wait=10, > error_message=None > ): > allowed_exceptions = allowed_exceptions or [] > with _EggTimer(timeout) as timer: > while not timer.elapsed(): > try: > res = func() > if res == value: > return > except Exception as exc: > if _instance_of_any(exc, allowed_exceptions): > time.sleep(3) > continue > > LOGGER.exception("Unhandled exception in %s", func) > raise > > if initial_wait == 0: > time.sleep(3) > else: > time.sleep(initial_wait) > initial_wait = 0 > try: > if error_message is None: > error_message = '%s != %s after %s seconds' % (res, value, timeout) > > raise AssertionError(error_message) > E AssertionError: False != True after 600 seconds > > ../ost_utils/ost_utils/assertions.py:60: AssertionError_______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/65FECSE7EBWNS… -- Didi

5 14

OST check-patch jobs are stuck on archive artifacts stage
by Amit Bawer 08 Nov '20

08 Nov '20

Hi, Exemplified here, started last night and still hasn't finished archiving: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/13195… Thanks.

2 2

Testing image transfer and backup with OST environment
by Nir Soffer 08 Nov '20

08 Nov '20

I want to share useful info from the OST hackathon we had this week. Image transfer must work with real hostnames to allow server certificate verification. Inside the OST environment, engine and hosts names are resolvable, but on the host (or vm) running OST, the names are not available. This can be fixed by adding the engine and hosts to /etc/hosts like this: $ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.200.2 engine 192.168.200.3 lago-basic-suite-master-host-0 192.168.200.4 lago-basic-suite-master-host-1 It would be if this was automated by OST. You can get the details using: $ cd src/ovirt-system-tests/deployment-xxx $ lago status OST keeps the deployment directory in the source directory. Be careful if you like to "git clean -dxf' since it will delete all the deployment and you will have to kill the vms manually later. The next thing we need is the engine ca cert. It can be fetched like this: $ curl -k 'https://engine/ovirt-engine/services/pki-resource?resource=ca-certificate&f…' > ca.pem I would expect OST to do this and put the file in the deployment directory. To upload or download images, backup vms or use other modern examples from the sdk, you need to have a configuration file like this: $ cat ~/.config/ovirt.conf [engine] engine_url = https://engine username = admin@internal password = 123 cafile = ca.pem With this uploading from the same directory where ca.pem is located will work. If you want it to work from any directory, use absolute path to the file. I created a test image using qemu-img and qemu-io: $ qemu-img create -f qcow2 test.qcow2 1g To write some data to the test image we can use qemu-io. This writes 64k of data (b"\xf0" * 64 * 1024) to offset 1 MiB. $ qemu-io -f qcow2 -c "write -P 240 1m 64k" test.qcow2 Since this image contains only 64k of data, uploading it should be instant. The last part we need is the imageio client package: $ dnf install ovirt-imageio-client To upload the image, we need at least one host up and storage domains created. I did not find a way to prepare OST, so simply run this after run_tests completed. It took about an hour. To upload the image to raw sparse disk we can use: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py -c engine --sd-name nfs --disk-sparse --disk-format raw test.qcow2 [ 0.0 ] Checking image... [ 0.0 ] Image format: qcow2 [ 0.0 ] Disk format: raw [ 0.0 ] Disk content type: data [ 0.0 ] Disk provisioned size: 1073741824 [ 0.0 ] Disk initial size: 1073741824 [ 0.0 ] Disk name: test.raw [ 0.0 ] Disk backup: False [ 0.0 ] Connecting... [ 0.0 ] Creating disk... [ 36.3 ] Disk ID: 26df08cf-3dec-47b9-b776-0e2bc564b6d5 [ 36.3 ] Creating image transfer... [ 38.2 ] Transfer ID: de8cfac9-ead2-4304-b18b-a1779d647716 [ 38.2 ] Transfer host name: lago-basic-suite-master-host-1 [ 38.2 ] Uploading image... [ 100.00% ] 1.00 GiB, 1.79 seconds, 571.50 MiB/s [ 40.0 ] Finalizing image transfer... [ 44.1 ] Upload completed successfully I uploaded this before I added the hosts to /etc/hosts, so the upload was done via the proxy. Yes, it took 36 seconds to create the disk. To download the disk use: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/download_disk.py -c engine 5ac63c72-6296-46b1-a068-b1039c8ecbd1 downlaod.qcow2 [ 0.0 ] Connecting... [ 0.2 ] Creating image transfer... [ 1.6 ] Transfer ID: a99e2a43-8360-4661-81dc-02828a88d586 [ 1.6 ] Transfer host name: lago-basic-suite-master-host-1 [ 1.6 ] Downloading image... [ 100.00% ] 1.00 GiB, 0.32 seconds, 3.10 GiB/s [ 1.9 ] Finalizing image transfer... We can verify the transfers using checksums. Here we create a checksum of the remote disk: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/checksum_disk.py -c engine 26df08cf-3dec-47b9-b776-0e2bc564b6d5 { "algorithm": "blake2b", "block_size": 4194304, "checksum": "a79a1efae73484e0218403e6eb715cdf109c8e99c2200265b779369339cf347b" } And checksum of the downloaded image - they should match: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/checksum_image.py downlaod.qcow2 { "algorithm": "blake2b", "block_size": 4194304, "checksum": "a79a1efae73484e0218403e6eb715cdf109c8e99c2200265b779369339cf347b" } Same upload to iscsi domain, using qcow2 format: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py -c engine --sd-name iscsi --disk-sparse --disk-format qcow2 test.qcow2 [ 0.0 ] Checking image... [ 0.0 ] Image format: qcow2 [ 0.0 ] Disk format: cow [ 0.0 ] Disk content type: data [ 0.0 ] Disk provisioned size: 1073741824 [ 0.0 ] Disk initial size: 458752 [ 0.0 ] Disk name: test.qcow2 [ 0.0 ] Disk backup: False [ 0.0 ] Connecting... [ 0.0 ] Creating disk... [ 27.8 ] Disk ID: e7ef253e-7baa-4d4a-a9b2-1a6b7db13f41 [ 27.8 ] Creating image transfer... [ 30.0 ] Transfer ID: 88328857-ac99-4ee1-9618-6b3cd14a7db8 [ 30.0 ] Transfer host name: lago-basic-suite-master-host-0 [ 30.0 ] Uploading image... [ 100.00% ] 1.00 GiB, 0.31 seconds, 3.28 GiB/s [ 30.3 ] Finalizing image transfer... [ 35.4 ] Upload completed successfully Again, creating the disk is very slow, not sure why. Probably having a storage server on a nested vm is not a good idea. We can compare the checksum with the source image since checksum are computed from the guest content: [nsoffer@ost ~]$ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/checksum_disk.py -c engine e7ef253e-7baa-4d4a-a9b2-1a6b7db13f41 { "algorithm": "blake2b", "block_size": 4194304, "checksum": "a79a1efae73484e0218403e6eb715cdf109c8e99c2200265b779369339cf347b" } Finally, we can try real images using virt-builder: $ virt-builder fedora-32 Will create a new Fedora 32 server image in the current directory. See --help for many useful options to create different format, set root password, or install packages. Uploading this image is much slower: $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py -c engine --sd-name nfs --disk-sparse --disk-format raw fedora-32.img [ 0.0 ] Checking image... [ 0.0 ] Image format: raw [ 0.0 ] Disk format: raw [ 0.0 ] Disk content type: data [ 0.0 ] Disk provisioned size: 6442450944 [ 0.0 ] Disk initial size: 6442450944 [ 0.0 ] Disk name: fedora-32.raw [ 0.0 ] Disk backup: False [ 0.0 ] Connecting... [ 0.0 ] Creating disk... [ 36.8 ] Disk ID: b17126f3-fa03-4c22-8f59-ef599b64a42e [ 36.8 ] Creating image transfer... [ 38.5 ] Transfer ID: fe82fb86-b87a-4e49-b9cd-f1f4334e7852 [ 38.5 ] Transfer host name: lago-basic-suite-master-host-0 [ 38.5 ] Uploading image... [ 100.00% ] 6.00 GiB, 99.71 seconds, 61.62 MiB/s [ 138.2 ] Finalizing image transfer... [ 147.8 ] Upload completed successfully At the current state of OST, we should avoid such long tests. Using backup_vm.py and other examples should work in the same way. I posted this patch to improve nfs performance, please review: https://gerrit.ovirt.org/c/112067/ Nir

4 9

回复:Re: Host's status how to change to UP when I execute Management--> Active command
by 李伏琼 05 Nov '20

05 Nov '20

thanks very much --------------原始邮件-------------- 发件人："Liran Rotenberg "<lrotenbe(a)redhat.com>; 发送时间：2020年11月5日(星期四) 晚上11:52 收件人："lifuqiong(a)sunyainfo.com" <lifuqiong(a)sunyainfo.com>; 抄送："users "<users(a)ovirt.org>;"devel "<devel(a)ovirt.org>; 主题：[ovirt-devel] Re: Host's status how to change to UP when I execute Management--> Active command ----------------------------------- Hi,The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com <lifuqiong(a)sunyainfo.com> wrote: Hi,      I checkout ovirt-engine's code with branch 4.2;  When execute Host's Management --> Active  command,  ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine?  The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() {         final VDS vds = getVds();         try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) {             executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false);             setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded());             if (getSucceeded()) {                 TransactionSupport.executeInNewTransaction(() -> {                     // set network to operational / non-operational                     List<Network> networks = networkDao.getAllForCluster(vds.getClusterId());                     networkClusterHelper.setStatus(vds.getClusterId(), networks);                     return null;                 });                 // Start glusterd service on the node, which would haven been stopped due to maintenance                 if (vds.getClusterSupportsGlusterService()) {                     runVdsCommand(VDSCommandType.ManageGlusterService,                             new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart"));                     // starting vdo service                     GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId());                     switch (isRunning) {                     case DOWN:                         log.info("VDO service is down in host : '{}' with id '{}', starting VDO service",                                 vds.getHostName(),                                 vds.getId());                         startVDOService(vds);                         break;                     case UP:                         log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service",                                 vds.getHostName(),                                 vds.getId());                            break;                     case UNKNOWN:                         log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service",                                 vds.getHostName(),                                 vds.getId());                         break;                     }                 }             }         }     } Your Sincerely Mark Lee _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH3K…

1 0

Re: Host's status how to change to UP when I execute Management--> Active command
by Liran Rotenberg 05 Nov '20

05 Nov '20

Hi, The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com < lifuqiong(a)sunyainfo.com> wrote: > > Hi, > I checkout ovirt-engine's code with branch 4.2; When execute Host's > Management --> Active command, ovirt engine just set vds's status to > "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The > code in ActiveVdsCommand.executeCommand() as follows: > protected void executeCommand() { > > final VDS vds = getVds(); > try (EngineLock monitoringLock = acquireMonitorLock("Activate > host")) { > executionHandler.updateSpecificActionJobCompleted(vds.getId(), > ActionType.MaintenanceVds, false); > > setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); > > if (getSucceeded()) { > TransactionSupport.executeInNewTransaction(() -> { > // set network to operational / non-operational > List<Network> networks = > networkDao.getAllForCluster(vds.getClusterId()); > networkClusterHelper.setStatus(vds.getClusterId(), > networks); > return null; > }); > > // Start glusterd service on the node, which would haven > been stopped due to maintenance > if (vds.getClusterSupportsGlusterService()) { > runVdsCommand(VDSCommandType.ManageGlusterService, > new GlusterServiceVDSParameters(vds.getId(), > Arrays.asList("glusterd"), "restart")); > // starting vdo service > GlusterStatus isRunning = > glusterUtil.isVDORunning(vds.getId()); > switch (isRunning) { > case DOWN: > log.info("VDO service is down in host : '{}' with > id '{}', starting VDO service", > vds.getHostName(), > vds.getId()); > startVDOService(vds); > break; > case UP: > log.info("VDO service is up in host : '{}' with > id '{}', skipping starting of VDO service", > vds.getHostName(), > vds.getId()); > break; > case UNKNOWN: > log.info("VDO service is not installed host : > '{}' with id '{}', ignoring to start VDO service", > vds.getHostName(), > vds.getId()); > break; > } > > } > } > } > } > > > Your Sincerely > Mark Lee > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH3K… >

1 0

Building lago from source
by Nir Soffer 05 Nov '20

05 Nov '20

I'm trying to test with ost: https://github.com/lago-project/lago/pull/815 So clone the project on the ost vm and built rpms: make make rpm The result is: lago-1.0.2-1.el8.noarch.rpm python3-lago-1.0.2-1.el8.noarch.rpm But the lago version installed by setup_for_ost.sh is: $ rpm -q lago lago-1.0.11-1.el8.noarch I tried to install lago from master, and then lago_init fail: $ lago_init /usr/share/ost-images/el8-engine-installed.qcow2 -k /usr/share/ost-images/el8_id_rsa Using images ost-images-el8-host-installed-1-202011021248.x86_64, ost-images-el8-engine-installed-1-202011021248.x86_64 containing ovirt-engine-4.4.4-0.0.master.20201031195930.git8f858d6c01d.el8.noarch vdsm-4.40.35.1-1.el8.x86_64 usage: lago [-h] [-l {info,debug,error,warning}] [--logdepth LOGDEPTH] [--version] [--out-format {default,flat,json,yaml}] [--prefix-path PREFIX_PATH] [--workdir-path WORKDIR_PATH] [--prefix-name PREFIX_NAME] [--ssh-user SSH_USER] [--ssh-password SSH_PASSWORD] [--ssh-tries SSH_TRIES] [--ssh-timeout SSH_TIMEOUT] [--libvirt_url LIBVIRT_URL] [--libvirt-user LIBVIRT_USER] [--libvirt-password LIBVIRT_PASSWORD] [--default_vm_type DEFAULT_VM_TYPE] [--default_vm_provider DEFAULT_VM_PROVIDER] [--default_root_password DEFAULT_ROOT_PASSWORD] [--lease_dir LEASE_DIR] [--reposync-dir REPOSYNC_DIR] [--ignore-warnings] VERB ... lago: error: unrecognized arguments: --ssh-key /home/nsoffer/src/ovirt-system-tests/deployment-basic-suite-master /home/nsoffer/src/ovirt-system-tests/basic-suite-master/LagoInitFile Do we use a customized lago version for ost? Where is the source? Nir

2 1

Host's status how to change to UP when I execute Management--> Active command
by lifuqiong＠sunyainfo.com 05 Nov '20

05 Nov '20

Hi, I checkout ovirt-engine's code with branch 4.2; When execute Host's Management --> Active command, ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() { final VDS vds = getVds(); try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) { executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false); setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); if (getSucceeded()) { TransactionSupport.executeInNewTransaction(() -> { // set network to operational / non-operational List<Network> networks = networkDao.getAllForCluster(vds.getClusterId()); networkClusterHelper.setStatus(vds.getClusterId(), networks); return null; }); // Start glusterd service on the node, which would haven been stopped due to maintenance if (vds.getClusterSupportsGlusterService()) { runVdsCommand(VDSCommandType.ManageGlusterService, new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart")); // starting vdo service GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId()); switch (isRunning) { case DOWN: log.info("VDO service is down in host : '{}' with id '{}', starting VDO service", vds.getHostName(), vds.getId()); startVDOService(vds); break; case UP: log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service", vds.getHostName(), vds.getId()); break; case UNKNOWN: log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service", vds.getHostName(), vds.getId()); break; } } } } } Your Sincerely Mark Lee

1 0

Re: [ovirt-users] Re: Removal of dpdk
by Dominik Holler 04 Nov '20

04 Nov '20

Hi Florian, thanks for your thoughts! On Tue, Nov 3, 2020 at 3:21 PM Florian Schmid via Users <users(a)ovirt.org> wrote: > Hi Ales, > > what do you mean with "not maintained for a long time"? > The oVirt integration of dpdk was not maintained. > DPDK is heavily developed and make the linux network extremely fast. > > I don't think, that SR-IOV can replace it, > The removal of dpdk is about removing the dpdk support from oVirt hosts only. We wonder if there is someone using dpdk to attach oVirt VMs to physical NICs. We are aware that many users use SR-IOV, especially for scenarios of enabling a high count of Ethernet frames for VMs or requiring a low latency, but we are not aware of users using dpdk to connect the oVirt VMs to the physical NICs of the host. > because packets must be still processed by the kernel, which is really > slow and CPU demanding. > In SR-IOV the packets might be processed by the guest kernel, not but the host kernel. oVirt is focused on the host kernel, while the guest OS is managed by the user of oVirt. Did this explanation address your concerns? BR Florian > > ------------------------------ > *Von: *"Ales Musil" <amusil(a)redhat.com> > *An: *"Nir Soffer" <nsoffer(a)redhat.com> > *CC: *"users" <users(a)ovirt.org>, "devel" <devel(a)ovirt.org> > *Gesendet: *Dienstag, 3. November 2020 13:56:12 > *Betreff: *[ovirt-users] Re: Removal of dpdk > > > > On Tue, Nov 3, 2020 at 1:52 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Tue, Nov 3, 2020 at 1:07 PM Ales Musil <amusil(a)redhat.com> wrote: >> >>> Hello, >>> we have decided to remove dpdk in the upcoming version of oVirt namely >>> 4.4.4. Let us know if there are any concerns about this. >>> >> >> Can you give more info why we want to remove this feature, and what is >> the replacement for existing users? >> >> Nir >> > > Sure, > the feature was only experimental and not maintained for a long time. The > replacement is to use SR-IOV > which is supported by oVirt. > > Thanks, > Ales > > > -- > > Ales Musil > > Software Engineer - RHV Network > > Red Hat EMEA <https://www.redhat.com> > > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3FHIRQKEEKLGW… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZCAYTHVZPOZF3… > >

2 1

Libvirt driver iothread property for virtio-scsi disks
by Nir Soffer 04 Nov '20

04 Nov '20

The docs[1] say: - The optional iothread attribute assigns the disk to an IOThread as defined by the range for the domain iothreads value. Multiple disks may be assigned to the same IOThread and are numbered from 1 to the domain iothreads value. Available for a disk device target configured to use "virtio" bus and "pci" or "ccw" address types. Since 1.2.8 (QEMU 2.1) Does it mean that virtio-scsi disks do not use iothreads? I'm experiencing a horrible performance using nested vms (up to 2 levels of nesting) when accessing NFS storage running on one of the VMs. The NFS server is using scsi disk. My theory is: - Writing to NFS server is very slow (too much nesting, slow disk) - Not using iothreads (because we don't use virtio?) - Guest CPU is blocked by slow I/O Does this make sense? [1] https://libvirt.org/formatdomain.html#hard-drives-floppy-disks-cdroms Nir

3 4

Re: [ovirt-users] Re: Removal of dpdk
by Ales Musil 03 Nov '20

03 Nov '20

On Tue, Nov 3, 2020 at 3:17 PM Florian Schmid <fschmid(a)ubimet.com> wrote: > Hi Ales, > > what do you mean with "not maintained for a long time"? > DPDK is heavily developed and make the linux network extremely fast. > > I don't think, that SR-IOV can replace it, because packets must be still > processed by the kernel, which is really slow and CPU demanding. > > BR Florian > > ------------------------------ > *Von: *"Ales Musil" <amusil(a)redhat.com> > *An: *"Nir Soffer" <nsoffer(a)redhat.com> > *CC: *"users" <users(a)ovirt.org>, "devel" <devel(a)ovirt.org> > *Gesendet: *Dienstag, 3. November 2020 13:56:12 > *Betreff: *[ovirt-users] Re: Removal of dpdk > > > The dpdk inside oVirt is not maintained, of course that dpdk as technology/project is still developed. > > On Tue, Nov 3, 2020 at 1:52 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Tue, Nov 3, 2020 at 1:07 PM Ales Musil <amusil(a)redhat.com> wrote: >> >>> Hello, >>> we have decided to remove dpdk in the upcoming version of oVirt namely >>> 4.4.4. Let us know if there are any concerns about this. >>> >> >> Can you give more info why we want to remove this feature, and what is >> the replacement for existing users? >> >> Nir >> > > Sure, > the feature was only experimental and not maintained for a long time. The > replacement is to use SR-IOV > which is supported by oVirt. > > Thanks, > Ales > > > -- > > Ales Musil > > Software Engineer - RHV Network > > Red Hat EMEA <https://www.redhat.com> > > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3FHIRQKEEKLGW… > -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Removal of dpdk
by Ales Musil 03 Nov '20

03 Nov '20

Hello, we have decided to remove dpdk in the upcoming version of oVirt namely 4.4.4. Let us know if there are any concerns about this. Thank you. Regards, Ales Musil -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

2 2

ovirt-engine has been tagged (ovirt-engine-4.4.3.10)
by Tal Nisan 02 Nov '20

02 Nov '20

1 0

Re: [virt-devel] Timeout failures in the OST
by Nir Soffer 02 Nov '20

02 Nov '20

On Mon, Nov 2, 2020 at 2:27 PM Benny Zlotnik <bzlotnik(a)redhat.com> wrote: Issues like this belong to oVirt devel mailing list. > looks like live merge failed[1]: > 2020-11-01 10:31:49,903+0100 ERROR (periodic/0) [virt.vm] (vmId='fcabfd2e-2937-4419-9b25-78fdd2b9c7c2') Unable to get watermarks for drive vdb: invalid argument: invalid path /rhev/data-center/mnt/blockSD/97b6175e-b6a9-419b-bd54-7c1e38c1bf71/images/fbb11a06-b8ef-4078-9530-978e7ca8ea0b/a911ad89-e461-4db4-88bf-a5d6590608b5 not assigned to domain (vm:1213) This may be a bug in vdsm live merge flow, tring to monitor a volume after the volume was already removed, or it may be libvirt/qemu bug. > ... > 2020-11-01 10:31:53,138+0100 ERROR (jsonrpc/1) [virt.vm] (vmId='fcabfd2e-2937-4419-9b25-78fdd2b9c7c2') merge: libvirt does not support volume chain monitoring. Unable to perform live merge. drive: vdb, alias: ua-fbb11a06-b8ef-4078-9530-978e7ca8ea0b, chains: {} (vm:5411) > > libvirt logs report: > ... > 2020-11-01 09:30:50.021+0000: 40137: error : virProcessRunInFork:1161 : internal error: child reported (status=125): > 2020-11-01 09:30:50.025+0000: 40137: error : virProcessRunInFork:1161 : internal error: child reported (status=125): internal error: child reported (status=125): > 2020-11-01 09:30:50.025+0000: 40137: warning : qemuDomainSnapshotDiskUpdateSource:15582 : Unable to move disk metadata on vm vm0 > 2020-11-01 09:31:45.539+0000: 40134: error : qemuMonitorJSONCheckError:412 : internal error: unable to execute QEMU command 'blockdev-del': Node libvirt-6-format is in use > 2020-11-01 09:31:45.539+0000: 40134: error : qemuMonitorJSONCheckError:412 : internal error: unable to execute QEMU command 'blockdev-del': Block device libvirt-6-storage is in use > 2020-11-01 09:31:45.540+0000: 40134: error : qemuMonitorJSONCheckError:412 : internal error: unable to execute QEMU command 'blockdev-del': Node 'libvirt-7-format' is busy: node is used as backing hd of 'libvirt-6-format' > 2020-11-01 09:31:45.541+0000: 40134: error : qemuMonitorJSONCheckError:412 : internal error: unable to execute QEMU command 'blockdev-del': Block device libvirt-7-storage is in use > 2020-11-01 09:31:45.900+0000: 40133: error : qemuDomainGetBlockInfo:12272 : invalid argument: invalid path /rhev/data-center/mnt/blockSD/97b6175e-b6a9-419b-bd54-7c1e38c1bf71/images/fbb11a06-b8ef-4078-9530-978e7ca8ea0b/a911ad89-e461-4db4-88bf-a5d6590608b5 not assigned to domain These smell like libvirt/qemu bug. Is this reproducible with RHEL 8.3? > Looks like the issue previously discussed in "[rhev-devel] Live storage migration instability in OST" two months ago has resurfaced > > > > Another issue seems to be the removal of the source disk: > 2020-11-01 10:31:48,056+0100 ERROR (tasks/3) [storage.StorageDomainManifest] removed image dir: /rhev/data-center/mnt/192.168.202.2:_exports_nfs_share1/3ca0e492-45f2-4383-b149-439043408bce/images/_remove_me_fbb11a06-b8ef-4078-9530-978e7ca8ea0b can't be removed (fileSD:258) > 2020-11-01 10:31:48,056+0100 ERROR (tasks/3) [storage.TaskManager.Task] (Task='70db80c2-076a-4ba1-a65d-821e6b5fe52c') Unexpected error (task:880) > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 251, in purgeImage > self.oop.os.rmdir(toDelDir) > File "/usr/lib/python3.6/site-packages/vdsm/storage/outOfProcess.py", line 238, in rmdir > self._iop.rmdir(path) > File "/usr/lib/python3.6/site-packages/ioprocess/__init__.py", line 550, in rmdir > return self._sendCommand("rmdir", {"path": path}, self.timeout) > File "/usr/lib/python3.6/site-packages/ioprocess/__init__.py", line 479, in _sendCommand > raise OSError(errcode, errstr) > OSError: [Errno 39] Directory not empty > > 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 887, in _run > return fn(*args, **kargs) > File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 350, in run > return self.cmd(*self.argslist, **self.argsdict) > File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper > return method(self, *args, **kwargs) > File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1947, in purgeImage > domain.purgeImage(sdUUID, imgUUID, volsByImg, discard) > File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 855, in purgeImage > self._manifest.purgeImage(sdUUID, imgUUID, volsImgs, discard) > File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 259, in purgeImage > raise se.ImageDeleteError("%s %s" % (imgUUID, str(e))) > vdsm.storage.exception.ImageDeleteError: Could not remove all image's volumes: ('fbb11a06-b8ef-4078-9530-978e7ca8ea0b [Errno 39] Directory not empty',) > > But it's unclear what the leftover is Maybe be leftover from previous failed LSM. I think we need a better error message here, it should list the files in the non-empty directory. > [1] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12782… > > > On Mon, Nov 2, 2020 at 1:44 PM Steven Rosenberg <srosenbe(a)redhat.com> wrote: >> >> Dear Benny, >> >> Thank you for your response. >> >> Here is the timeout engine log from one of the ps 45 failures [1]. >> >> It seems like this timeout is related to the engine failing and the ost scripts are not designed to detect the fail, thus timing out: >> >> 2020-11-01 10:31:55,175+01 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [live_storage_migration] Command id: '60b3f7fc-93db-48b2-82a1-8a93c47e18e1 failed child command status for step 'MERGE_STATUS' >> >> >> >> >> [1] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12796… >> >> With Best Regards. >> >> Steven. >> >> >> >> On Mon, Nov 2, 2020 at 12:51 PM Benny Zlotnik <bzlotnik(a)redhat.com> wrote: >>> >>> Can you link to the relevant engine/vdsm logs? >>> The timeout in the tests indicates that the desired state wasn't >>> reached so test logs don't provide the information about what exactly >>> happened >>> >>> On Sun, Nov 1, 2020 at 5:10 PM Steven Rosenberg <srosenbe(a)redhat.com> wrote: >>> > >>> > Dear virt-devel, >>> > >>> > We are currently experiencing many timeout failures in various patch sets for a gerrit issue 11395 [1]. >>> > >>> > The timeouts occur intermittently and seem to be unrelated to the changes which are only in the 004 module [2] and should have only affected VM1 / Disk1. >>> > >>> > We could use some advice on addressing these issues as well as a review of the patch to ensure we can move this patch forward. The patch sets and relevant timeouts are as follows: >>> > >>> > PS 40: >>> > >>> > test_live_storage_migration – test 004 [3] >>> > >>> > PS 41: >>> > >>> > on test_verify_engine_backup – test 002 [4] >>> > >>> > PS 43: >>> > >>> > on test_virtual_machines - test 100 [5] >>> > >>> > PS 45: >>> > >>> > on test_live_storage_migration – 004 [6] >>> > >>> > >>> > >>> > >>> > [1] https://gerrit.ovirt.org/#/c/111395/ >>> > [2] basic-suite-master/test-scenarios/004_basic_sanity.py >>> > [3] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12628… >>> > [4] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12659… >>> > [5] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12744… >>> > [6] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12782… >>> > >>> > With Best Regards. >>> > >>> > Steven >>> > >>> > >>>

1 0

Fwd: Timeout failures in the OST
by Steven Rosenberg 02 Nov '20

02 Nov '20

---------- Forwarded message --------- From: Steven Rosenberg <srosenbe(a)redhat.com> Date: Sun, Nov 1, 2020 at 5:09 PM Subject: Timeout failures in the OST To: virt-devel <virt-devel(a)redhat.com> Dear ovirt Personnel, We are currently experiencing many timeout failures in various patch sets for a gerrit issue 11395 [1]. The timeouts occur intermittently and seem to be unrelated to the changes which are only in the 004 module [2] and should have only affected VM1 / Disk1. We could use some advice on addressing these issues as well as a review of the patch to ensure we can move this patch forward. The patch sets and relevant timeouts are as follows: PS 40: test_live_storage_migration – test 004 [3] PS 41: on test_verify_engine_backup – test 002 [4] PS 43: on test_virtual_machines - test 100 [5] PS 45: on test_live_storage_migration – 004 [6] [1] https://gerrit.ovirt.org/#/c/111395/ [2] basic-suite-master/test-scenarios/004_basic_sanity.py [3] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12628… [4] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12659… [5] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12744… [6] https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/12782… With Best Regards. Steven

1 0