October 2020 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error: Adding new Host to ovirt-engine
by Ahmad Khiet 14 Aug '23

14 Aug '23

Hi, Can't add new host to ovirt engine, because the following error: 2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts : Set facts] ************************************* 2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => { "ansible_facts": { "ansible_python_interpreter": "/usr/bin/python2", "host_deploy_vdsm_version": "4.40.0" }, "changed": false } 2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver : Install ovs] ********************************* 2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! => {} MSG: The conditional check 'cluster_switch == "ovs" or (ovn_central is defined and ovn_central | ipaddr and ovn_engine_cluster_version is version_compare('4.2', '>='))' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller The error appears to be in '/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - block: - name: Install ovs ^ here 2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP ********************************************************************* 2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 whats missing!? Thanks -- Ahmad Khiet Red Hat <https://www.redhat.com/> akhiet(a)redhat.com M: +972-54-6225629 <https://red.ht/sig>

7 10

Purging inactive maintainers from vdsm-master-maintainers
by Nir Soffer 21 Jun '21

21 Jun '21

I want to remove inactive contributors from vdsm-master-maintainers. I suggest the simple rule of 2 years of inactivity for removing from this group, based on git log. See the list below for current status: https://gerrit.ovirt.org/#/admin/groups/106,members Thoughts? Nir

6 11

Merge rights changes in the oVirt Engine project
by Tal Nisan 09 Apr '21

09 Apr '21

Hi everyone, As you probably know we are now in a mode in which we develop our next zstream version on the master branch as opposed to how we worked before where the master version was dedicated for the next major version. This makes the rapid changes in master to be delivered to customers in a much higher cadence thus affecting stability. Due to that we think it's best that from now on merges in the master branch will be done only by stable branch maintainers after inspecting those closely. What you need to do in order to get your patch merged: - Have it pass Jenkins - Have it get code review +2 - Have it mark verified +1 - It's always encourage to have it tested by OST, for bigger changes it's a must Once you have all those covered, please add me as a reviewer and I'll examine it and merge if everything seems right, if I haven't done it in a timely manner feel free to ping me.

3 4

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

CentOS Stream support
by Michal Skrivanek 01 Feb '21

01 Feb '21

Hi all, we would like to ask about interest in community about oVirt moving to CentOS Stream. There were some requests before but it’s hard to see how many people would really like to see that. With CentOS releases lagging behind RHEL for months it’s interesting to consider moving to CentOS Stream as it is much more up to date and allows us to fix bugs faster, with less workarounds and overhead for maintaining old code. E.g. our current integration tests do not really pass on CentOS 8.1 and we can’t really do much about that other than wait for more up to date packages. It would also bring us closer to make oVirt run smoothly on RHEL as that is also much closer to Stream than it is to outdated CentOS. So..would you like us to support CentOS Stream? We don’t really have capacity to run 3 different platforms, would you still want oVirt to support CentOS Stream if it means “less support” for regular CentOS? There are some concerns about Stream being a bit less stable, do you share those concerns? Thank you for your comments, michal

6 12

planned Jenkins restart
by Evgheni Dereveanchin 02 Dec '20

02 Dec '20

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

2 2

Branching out 4.3 in ovirt-system-tests
by Marcin Sobczyk 23 Nov '20

23 Nov '20

Hi all, after minimizing the usage of lago in basic suite, and some minor adjustments in the network suite, we are finally able to remove lago OST plugin as a dependency [1]. This however comes with a price of keeping lots of ugly ifology, i.e. [2][3]. There's big disparity between OST runs we have on el7 and el8. There's also tons of symlink-based code sharing between suites - be it 4.3 suites and master suites or simply different types of suites. The basic suite has its own 'test_utils', which is copied/symlinked in multiple places. There's also 'ost_utils', which is really messy ATM. It's very hard to keep track and maintain all of this... At this moment, we are able to run basic suite and network suite on el8, with prebuilt ost-images and without lago plugin. HE suites should be the next step. We have patches that make them py3-compatible that probably still need some attention [4][5]. We don't have any prebuilt HE ost-images, but this will be handled in the nearest future. I think it's good time to detach ourselves from the legacy stuff and start with a clean slate. My proposition would be to branch out 4.3 in ovirt-system-tests and not use py2/el7 in the master branch at all. This would allow us to focus on py3, el8 and ost-images efforts while keeping the legacy stuff intact. WDYT? Regards, Marcin [1] https://gerrit.ovirt.org/#/c/111643/ [2] https://gerrit.ovirt.org/#/c/111643/6/basic-suite-master/control.sh [3] https://gerrit.ovirt.org/#/c/111643/6/basic-suite-master/test-scenarios/con… [4] https://gerrit.ovirt.org/108809 [5] https://gerrit.ovirt.org/110097

3 8

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

ovirt-engine has been tagged (ovirt-engine-4.4.3.9)
by Tal Nisan 27 Oct '20

27 Oct '20

1 0

vdsm fails on Travis
by Vojtech Juranek 22 Oct '20

22 Oct '20

Hi, some network tests fail on Travis, see e.g. [1]. Could someone from network team take a look? My guess is it's caused by commit 3ec1ad9a9f38 [2], but I'm not sure. Thanks Vojta [1] https://travis-ci.org/github/oVirt/vdsm/jobs/737665066 [2] https://github.com/oVirt/vdsm/commit/3ec1ad9a9f3879bf1c1b4aef2cbed4c3eda169…

3 3

Vdsm: ovirt-4.4.3 branch created
by Milan Zamazal 22 Oct '20

22 Oct '20

Hi, ovirt-4.4.3 branch has been created in Vdsm. Any patches after Vdsm 4.40.35 that should go to 4.4.3 (blockers only) must be backported. You can merge 4.4.4+ patches to master now. Regards, Milan

1 0

ovirt-engine 4.4.3 was branched
by Tal Nisan 22 Oct '20

22 Oct '20

Hi everyone, As you probably know, yesterday we've tagged and built the 4.4.3 RC build, to maintain stability and to allow work on 4.4.4 we have branched 4.4.3 so: For your 4.4.4 work - just push to master For 4.4.3 work (blockers/exceptions only!) - push to master and once it's merged backport to the ovirt-engine-4.4.3.z branch Thanks!

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.3.8)
by Tal Nisan 21 Oct '20

21 Oct '20

1 0

callback hanging making commands executing serial
by Liran Rotenberg 20 Oct '20

20 Oct '20

Hi all, Investigating a bug about serial execution <https://bugzilla.redhat.com/1885286> of the same command more than once shows a problem with our callbacks. The problem is felt when we have synchronized operation (such as running ansible runner service) that takes a bit time to be executed. The problem is, when running multiple commands and one has synchronized long operation within a child command, it will hang out all the commands running on the engine using callbacks. The good example is given in the bug, since export OVA command using ansible(sync) and the pack_ova script takes time to finish. This is not really noticeable with short synchronized commands, but it does execute serial for them as well instead of parallel. Running export to OVA command and then other commands with callbacks will get them hanging if the export command callback started and it reached to performNextOperation. Some technical details: We have one thread in CommandCallbacksPoller[1] that runs, collects the current command on the engine and processes them. Once we have the above scenario (let's say 2 commands), the first one will go into callback.doPolling in invokeCallbackMethodsImpl. [2] In that case it will go to ChildCommandsCallbackBase::doPolling, eventually to childCommandsExecutingEnded. [3] While there are more actions to perform we will do performNextOperation [4], which calls executeNextOperation (in the bug case [5]). When the next operation is long and synchronized, this will block the CommandCallbacksPoller thread and only when it finishes the thread is released and the callbacks continue working. Any idea how to solve this issue? Regards, Liran [1] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/b… [2] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/b… [3] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/b… [4] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/b… [5] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/b…

4 5

oVirt Survey Autumn 2020 results
by Sandro Bonazzola 19 Oct '20

19 Oct '20

Thanks to the 79 participants to oVirt Survey Autumn 2020! The survey is now closed and results are publicly available at https://docs.google.com/forms/d/1eMYaCoysPkYt2iHZW2RRO1HmSqsD0phrwSTVYFlqLy… We'll analyze collected data in order to improve oVirt thanks to your feedback. Thanks, -- 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.* * <https://www.redhat.com/it/forums/emea/italy-track>*

1 0

Re: [CQ]: 111471,2 (ovirt-engine) failed "ovirt-master" system tests
by Yedidyah Bar David 15 Oct '20

15 Oct '20

On Wed, Oct 14, 2020 at 7:06 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote: > > Change 111471,2 (ovirt-engine) is probably the reason behind recent system test > failures in the "ovirt-master" change queue and needs to be fixed. > > This change had been removed from the testing queue. Artifacts build from this > change will not be released until it is fixed. > > For further details about the change see: > https://gerrit.ovirt.org/#/c/111471/2 This fails compilation. Liran already commented there with details, posting this for visibility. Is anyone handling this? Should we revert? Thanks and best regards, -- Didi

4 8

ovirt-engine has been tagged (ovirt-engine-4.4.3.7)
by Tal Nisan 14 Oct '20

14 Oct '20

1 0

VDSM CI Fails
by Eyal Shenitzky 11 Oct '20

11 Oct '20

Hi all, I am seeing the following error in VDSM CI - [2020-10-11T08:10:54.836Z] ########################################################## [2020-10-11T08:10:54.836Z] ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv [2020-10-11T08:10:54.836Z] ##! Last 20 log entries: /tmp/mock_logs.VL5n5w1X/init/stdout_stderr.log [2020-10-11T08:10:54.836Z] ##! [2020-10-11T08:10:54.836Z] will then just ignore the repository until you permanently enable it [2020-10-11T08:10:54.836Z] again or use --enablerepo for temporary usage: [2020-10-11T08:10:54.836Z] [2020-10-11T08:10:54.836Z] yum-config-manager --disable fc30-updates-debuginfo [2020-10-11T08:10:54.836Z] or [2020-10-11T08:10:54.836Z] subscription-manager repos --disable=fc30-updates-debuginfo [2020-10-11T08:10:54.836Z] [2020-10-11T08:10:54.836Z] 5. Configure the failing repository to be skipped, if it is unavailable. [2020-10-11T08:10:54.836Z] Note that yum will try to contact the repo. when it runs most commands, [2020-10-11T08:10:54.836Z] so will have to try and fail each time (and thus. yum will be be much [2020-10-11T08:10:54.836Z] slower). If it is a very temporary problem though, this is often a nice [2020-10-11T08:10:54.836Z] compromise: [2020-10-11T08:10:54.836Z] [2020-10-11T08:10:54.836Z] yum-config-manager --save --setopt=fc30-updates-debuginfo.skip_if_unavailable=true [2020-10-11T08:10:54.836Z] [2020-10-11T08:10:54.836Z] failure: repodata/repomd.xml from fc30-updates-debuginfo: [Errno 256] No more mirrors to try. [2020-10-11T08:10:54.836Z] https://mirror.isoc.org.il/pub/fedora/releases/30/Everything/x86_64/debug/t…: [Errno 14] HTTPS Error 404 - Not Found [2020-10-11T08:10:54.836Z] [2020-10-11T08:10:54.836Z] Init took 6 seconds [2020-10-11T08:10:54.836Z] ============================ [2020-10-11T08:10:54.836Z] ##! [2020-10-11T08:10:54.836Z] ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [2020-10-11T08:10:54.836Z] ##!######################################################## Can be found at - https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… Can someone take a look? Thanks -- Regards, Eyal Shenitzky

2 1

engine-setup failure: "ERROR: column network.port_isolation does not exist"
by Nir Soffer 11 Oct '20

11 Oct '20

Trying to setup engine from master (+some patches) fails now with: [ INFO ] Backing up database localhost:engine to '/home/nsoffer/ovirt-engine/var/lib/ovirt-engine/backups/engine-20201011203045.ttdi_77z.dump'. [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/home/nsoffer/ovirt-engine/share/ovirt-engine/dbscripts/create_views.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed Setup log show: psql:/home/nsoffer/ovirt-engine/share/ovirt-engine/dbscripts/create_views.sql:2799: ERROR: column network.port_isolation does not exist LINE 22: network.port_isolation AS port_isolation, ^ FATAL: Cannot execute sql command: --file=/home/nsoffer/ovirt-engine/share/ovirt-engine/dbscripts/create_views.sql 2020-10-11 20:30:51,712+0300 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:530 schema.sh: FATAL: Cannot execute sql command: --file=/home/nsoffer/ovirt-engine/share/ovirt-engine/dbscripts/create_views.sql 2020-10-11 20:30:51,713+0300 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/nsoffer/ovirt-engine/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 532, in _misc raise RuntimeError(_('Engine schema refresh failed')) I guess this is related to latest networking changes, maybe some patches were wrong, breaking my database? Do we have a way to fix this? I don't want to clear my database, it has useful storage and host setup. Thanks, Nir

1 1

Re: Incremental Backup | oVirt
by Nir Soffer 09 Oct '20

09 Oct '20

On Thu, Oct 8, 2020, 12:28 luwen.zhang(a)vinchin.com <luwen.zhang(a)vinchin.com> wrote: > Dear team, > > My name is Luwen Zhang from Vinchin Backup & Recovery. > > I'm sending you this Email because our developers encountered some > problems while developing incremental backup feature following the oVirt > documentations. > > https://www.ovirt.org/documentation/incremental-backup-guide/incremental-ba… > > We downloaded oVirt 4.4.1 from oVirt website, and is now developing based > on this version, as per the documentation when we perform the first time > full backup, we should obtain a "checkpoint id", so when we perform > incremental backup using this ID we should know what's have changed on the > VM. But now the problem is that we cannot get the checkpoint ID. > > The components and versions of oVirt are as follows: > You are using qemu 4.2 and libvirt 6.0. These versions are too old, missing some features or have bugs which will not be fixed. These version maya be good enough for development, but your product will need newer version. We require now libvirt 6.6 and qemu 5.1. These versions will be available in CentOS 8.3. On libvirt, incremental backup will be fully supported only in RHEL AV 8.3.1. I guess we will build the relevant version for CentOS after this version is released for RHEL. Nir > > > Could you please kindly check on this issue and point out what should be > wrong and what we should do? > > Looking forward to your reply. > > Thanks & regards! > ------------------------------ > *Luwen Zhang* | Product Manager > > Tel: +86-28-8553-0156 > Mob: +86-138-8042-4687 > Skype: luwen.zhang_cn > E-mail: luwen.zhang(a)vinchin.com > > F5, Block 8, National Information Security Industry Park, No.333 YunHua > Road, Hi-Tech Zone, Chengdu, China | P.C.610015 > _______________________________________________ > 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/CC56L57GK3DZQ… >

2 1

Broken CI initialization scripts
by Sandro Bonazzola 09 Oct '20

09 Oct '20

1 0

Re: Incremental Backup | oVirt
by Eyal Shenitzky 08 Oct '20

08 Oct '20

Hi Luwen, Full backup using the new API is supported by default, but in order to enable the use of 'incremental backup' you need to follow the following steps that written in the feature page: # engine-config -s "IsIncrementalBackupSupported=true" # systemctl restart ovirt-engine After those steps are done, each backup operation will create a checkpoint so you will receive the created checkpoint ID. On Thu, 8 Oct 2020 at 12:28, luwen.zhang(a)vinchin.com < luwen.zhang(a)vinchin.com> wrote: > Dear team, > > My name is Luwen Zhang from Vinchin Backup & Recovery. > > I'm sending you this Email because our developers encountered some > problems while developing incremental backup feature following the oVirt > documentations. > > https://www.ovirt.org/documentation/incremental-backup-guide/incremental-ba… > > We downloaded oVirt 4.4.1 from oVirt website, and is now developing based > on this version, as per the documentation when we perform the first time > full backup, we should obtain a "checkpoint id", so when we perform > incremental backup using this ID we should know what's have changed on the > VM. But now the problem is that we cannot get the checkpoint ID. > > The components and versions of oVirt are as follows: > > > > Could you please kindly check on this issue and point out what should be > wrong and what we should do? > > Looking forward to your reply. > > Thanks & regards! > ------------------------------ > *Luwen Zhang* | Product Manager > > Tel: +86-28-8553-0156 > Mob: +86-138-8042-4687 > Skype: luwen.zhang_cn > E-mail: luwen.zhang(a)vinchin.com > > F5, Block 8, National Information Security Industry Park, No.333 YunHua > Road, Hi-Tech Zone, Chengdu, China | P.C.610015 > _______________________________________________ > 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/CC56L57GK3DZQ… > -- Regards, Eyal Shenitzky

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.3.6)
by Tal Nisan 07 Oct '20

07 Oct '20

1 0

certificates not created?
by lejeczek 06 Oct '20

06 Oct '20

hi I have ovirt from ovirt-release44-4.4.2-1.el8.noarch. I presumed these files should be created without any user intervention and I wonder if this is a bug? ... Oct 03 15:02:42 dzien.private.pawel libvirtd[1291696]: Unable to read from monitor: Connection reset by peer Oct 03 15:02:42 dzien.private.pawel libvirtd[1291696]: internal error: qemu unexpectedly closed the monitor: 2020-10-03T14:02:42.051456Z qemu-kvm: warning: Spice: reds.c:2943:reds_init_ssl: Could not load certificates from /etc/pki/vdsm/libvirt-spice/server-cert.pem 2020-10-03T14:02:42.051477Z qemu-kvm: warning: Spice: error:02001002:system library:fopen:No such file or directory 2020-10-03T14:02:42.051483Z qemu-kvm: warning: Spice: error:20074002:BIO routines:file_ctrl:system lib 2020-10-03T14:02:42.051490Z qemu-kvm: warning: Spice: error:140DC002:SSL routines:use_certificate_chain_file:system lib 2020-10-03T14:02:42.051506Z qemu-kvm: failed to initialize spice server Oct 03 15:02:42 dzien.private.pawel libvirtd[1291696]: internal error: process exited while connecting to monitor: 2020-10-03T14:02:42.051456Z qemu-kvm: warning: Spice: reds.c:2943:reds_init_ssl: Could not load certificates from /etc/pki/vdsm/libvirt-spice/server-cert.pem 2020-10-03T14:02:42.051477Z qemu-kvm: warning: Spice: error:02001002:system library:fopen:No such file or directory 2020-10-03T14:02:42.051483Z qemu-kvm: warning: Spice: error:20074002:BIO routines:file_ctrl:system lib 2020-10-03T14:02:42.051490Z qemu-kvm: warning: Spice: error:140DC002:SSL routines:use_certificate_chain_file:system lib 2020-10-03T14:02:42.051506Z qemu-kvm: failed to initialize spice server ... Would any of you experts have a possible resolution, a workaround? many thanks, L.

2 1

Re: Need help in handling catch block in vdsm
by Michal Skrivanek 05 Oct '20

05 Oct '20

[adding devel list] > On 29 Sep 2020, at 09:51, Ritesh Chikatwar <rchikatw(a)redhat.com> wrote: > > Hello, > > i am new to VDSM codebase. > > There is one minor bug in gluster and they don't have any near plan to fix this. So i need to fix this in vdsm. > > The bug is when i run command > [root@dhcp35-237 ~]# gluster v geo-replication status > No active geo-replication sessions > geo-replication command failed > [root@dhcp35-237 ~]# > > So this engine is piling up with error. i need handle this in vdsm the code at this place > > https://github.com/oVirt/vdsm/blob/master/lib/vdsm/gluster/cli.py#L1231 <https://github.com/oVirt/vdsm/blob/master/lib/vdsm/gluster/cli.py#L1231> > > If i run the above command with xml then i will get > > [root@dhcp35-237 ~]# gluster v geo-replication status --xml > geo-replication command failed > [root@dhcp35-237 ~]# > > so i have to run one more command before executing this and check in exception that it contains No active geo-replication sessions this string. for that i did like this maybe it goes to stderr? other than that, no idea, sorry Thanks, michal > > try: > xmltree = _execGluster(command) > except ge.GlusterCmdFailedException as e: > if str(e).find("No active geo-replication sessions") != -1: > return [] > Seems like this is not working can you help me here > > > Any help will be appreciated > Ritesh >

4 6

Disk sizes not updated on unmap/discard
by Tomáš Golembiovský 02 Oct '20

02 Oct '20

Hi, currently, when we run virt-sparsify on VM or user runs VM with discard enabled and when the disk is on block storage in qcow, the results are not reflected in oVirt. The blocks get discarded, storage can reuse them and reports correct allocation statistics, but oVirt does not. In oVirt one can still see the original allocation for disk and storage domain as it was before blocks were discarded. This is super-confusing to the users because when they check after running virt-sparsify and see the same values they think sparsification is not working. Which is not true. It all seems to be because of our LVM layout that we have on storage domain. The feature page for discard [1] suggests it could be solved by running lvreduce. But this does not seem to be true. When blocks are discarded the QCOW does not necessarily change its apparent size, the blocks don't have to be removed from the end of the disk. So running lvreduce is likely to remove valuable data. At the moment I don't see how we could achieve the correct values. If anyone has any idea feel free to entertain me. The only option seems to be to switch to LVM thin pools. Do we have any plans on doing that? Tomas [1] https://www.ovirt.org/develop/release-management/features/storage/pass-disc… -- Tomáš Golembiovský <tgolembi(a)redhat.com>

5 4