- Devel - oVirt List Archives

Support for 5K volumes
by Sandro Bonazzola 09 Mar '21

09 Mar '21

Hi, Gluster 9 introduced support for 5k volumes ( https://docs.gluster.org/en/latest/release-notes/9.0/ ). Is there interest in getting this in oVirt too? Any thoughts about rebasing on Gluster 9 for oVirt 4.4.6? 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.*

4 3

test_ha_recovery failed (was: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1943 - Still Failing!)
by Yedidyah Bar David 09 Mar '21

09 Mar '21

On Sun, Mar 7, 2021 at 5:12 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/1943/ Failed during -basic-suite-master.test-scenarios.test_004_basic_sanity.test_ha_recovery due to timeout. Can't tell exactly why. Now rebuilt, to see if it happens again. Basic suite did pass this point with (mostly) the same code, and there shouldn't be anything HE-specific in this test. FYI. Some more details: The function is: @order_by(_TEST_LIST) def test_ha_recovery(engine_api, get_ansible_host_for_vm): engine = engine_api.system_service() with engine_utils.wait_for_event(engine, [119, 9602, 506]): # VM_DOWN_ERROR event(119) # HA_VM_FAILED event event(9602) # VDS_INITIATED_RUN_VM event(506) ansible_host = get_ansible_host_for_vm(VM2_NAME) pid = ansible_host.shell('pgrep -f qemu.*guest=vm2')['stdout'].strip() ansible_host.shell('kill -KILL {}'.format(pid)) vm_service = test_utils.get_vm_service(engine, VM2_NAME) assertions.assert_true_within_long( lambda: vm_service.get().status == types.VmStatus.UP ) with engine_utils.wait_for_event(engine, 33): # USER_STOP_VM event vm_service.stop() It failed inside the 'with' statement. Can't find any of the expected events in engine.log. In last successful I see all three of them. We do not actively log anything about running the pgrep command, but it's logged by ansible on the host, to /var/log/messages. I see it in last successful, but not in above failed run, in any of the two hosts. So most likely it didn't even get to run pgrep. IMO we probably want some more information logged in such a case, to allow further investigation. Best regards, > Build Number: 1943 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1939 > [hbraha] ost: Check if user custom repos are used on VM > > > Changes for Build #1940 > [hbraha] network: add check_repos fixture > > > Changes for Build #1941 > [Andrej Cernek] network, pylint: Simplify pylintrc file > > > Changes for Build #1942 > [Andrej Cernek] network, pylint: Simplify pylintrc file > > > Changes for Build #1943 > [Andrej Cernek] network, pylint: Simplify pylintrc file > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: he-basic-suite-master.test-scenarios.test_004_basic_sanity.test_ha_recovery > > Error Message: > AssertionError: False != True after 600 seconds > > Stack Trace: > engine_api = <ovirtsdk4.Connection object at 0x7f408114c1d0> > get_ansible_host_for_vm = <function get_ansible_host_for_vm.<locals>.ansible_host_for at 0x7f4081171950> > > @order_by(_TEST_LIST) > def test_ha_recovery(engine_api, get_ansible_host_for_vm): > engine = engine_api.system_service() > with engine_utils.wait_for_event(engine, [119, 9602, 506]): > # VM_DOWN_ERROR event(119) > # HA_VM_FAILED event event(9602) > # VDS_INITIATED_RUN_VM event(506) > ansible_host = get_ansible_host_for_vm(VM2_NAME) > pid = ansible_host.shell('pgrep -f qemu.*guest=vm2')['stdout'].strip() > > ansible_host.shell('kill -KILL {}'.format(pid)) > > ../he-basic-suite-master/test-scenarios/test_004_basic_sanity.py:1070: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > /usr/lib64/python3.6/contextlib.py:88: in __exit__ > next(self.gen) > ../ost_utils/ost_utils/engine_utils.py:42: in wait_for_event > lambda: > ../ost_utils/ost_utils/assertions.py:96: in assert_true_within_long > assert_equals_within_long(func, True, allowed_exceptions) > ../ost_utils/ost_utils/assertions.py:81: in assert_equals_within_long > func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > func = <function wait_for_event.<locals>.<lambda> at 0x7f40810d5bf8> > 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 [] > res = '<no-result-obtained>' > 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:59: AssertionError -- Didi

1 3

Re: Starting a defined VM on a different host
by Benny Zlotnik 08 Mar '21

08 Mar '21

Not too familiar with this, but maybe this example will help[1] [1] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/pin_vm.py On Mon, Mar 8, 2021 at 3:41 PM Lavi Buchnik via Devel <devel(a)ovirt.org> wrote: > Hi Shani, > > > > Thanks for your reply. I’m aware for how to set it in the UI. > > Note that because the VM is defined with Affinity label, I must first > remove the affinity label from the VM and only than to choose a different > host as you specified below (via the UI). > > But my question is for how to set a different host using Python SDK API. > > > > I tried/plan this via Python SDK API: > > > > - Stop the VM. > > - Remove its Affinity label. > > - Update its host to the target host. > > - Start the VM. > > > > But the result is that the VM is always keep starting on its current host. > > For updating the VM host, I used few ways as: > > vm_service.update( types.Vm( host=types.Host( id=host_id ), ) ) > > > > Or: > > > > vm_service.update( types.Vm( host=types.Host( name=host_name ), ) ) > > > > Then started the VM using: > > vm_service.start() > > > > or using: > > vm_service.start( vm=types.Vm( host=types.Host( name=host_name ), ) ) > > vm_service.start( vm=types.Vm( host=types.Host( id=host_id ), ) ) > > > > I get no errors, but VM keeps starting on the current host and not on the > new target host. > > BTW - in case it would start on the target host, the plan is to add > affinity label back just after. > > > > Thanks, > > Lavi Buchnik > > > > *From:* Shani Leviim <sleviim(a)redhat.com> > *Sent:* Monday, March 08, 2021 2:36 PM > *To:* Lavi Buchnik <Lavi.Buchnik(a)exlibrisgroup.com> > *Cc:* devel <devel(a)ovirt.org> > *Subject:* Re: [ovirt-devel] Re: Starting a defined VM on a different host > > > > *CAUTION: *EXTERNAL Email. > > Hi, > > You can set this one from the UI: > > VM > Edit > Show advanced options (bottom left button) > host > Start > running on > specific host > > > > *Regards,* > > *Shani Leviim* > > > > > > On Mon, Mar 8, 2021 at 10:33 AM Lavi.Buchnik--- via Devel <devel(a)ovirt.org> > wrote: > > Hi, > > Can anyone help here? > > Thanks, > Lavi > _______________________________________________ > 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 > <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!Nk…> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZPB676EUPWZWE… > <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/devel@ovir…> > > _______________________________________________ > 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/S4DZTJCLKILIT… >

2 1

Re: Starting a defined VM on a different host
by Lavi.Buchnik＠exlibrisgroup.com 08 Mar '21

08 Mar '21

Hi, Can anyone help here? Thanks, Lavi

3 2

ovirt-engine has been tagged (ovirt-engine-4.4.5.9)
by Tal Nisan 08 Mar '21

08 Mar '21

1 0

Vdsm: ovirt-4.4.5 branch created
by Milan Zamazal 05 Mar '21

05 Mar '21

Hi, ovirt-4.4.5 branch has been created in Vdsm, you can use it for contingent 4.4.5 backports. Regards, Milan

1 0

basic suite failing on test_004_basic_sanity.test_verify_template_disk_copied_and_removed
by Marcin Sobczyk 04 Mar '21

04 Mar '21

Hi All, basic suite started failing on 'test_verify_template_disk_copied_and_removed'. Looking at the error reported (i.e. [1][2]) it seems that we can't get a valid handle to the glance disk. Can someone take a look at this? Regards, Marcin [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… [2] https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta…

6 12

Starting a defined VM on a different host
by Lavi Buchnik 04 Mar '21

04 Mar '21

Hi, I posted this thread a week ago under ovirt users: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EJH2X5X5FDIR7Q… Maybe I posted on the wrong list. Anyway, I didn't get any answer yet. Hope you can help me here. In short, I have a VM under Cluster Affinity label. And need to cold migrate this VM to another host. For that, I'm doing this (Via Python REST API): * Stop the VM. * Remove its Affinity label. * Update its host to the target host. * Start the VM. But the result is that the VM is always keep starting on its current host. For updating the VM host, I used few ways as: vm_service.update( types.Vm( host=types.Host( id=host_id ), ) ) Or: vm_service.update( types.Vm( host=types.Host( name=host_name ), ) ) Then started the VM using: vm_service.start() or using: vm_service.start( vm=types.Vm( host=types.Host( name=host_name ), ) ) vm_service.start( vm=types.Vm( host=types.Host( id=host_id ), ) ) I get no errors, but VM keeps starting on the current host and not on the new target host. BTW - in case it would start on the target host, the plan is to add affinity label back just after. Thanks, Lavi Buchnik Cloud System Engineer T: +972-2-6499352 M: +972-52-8542307 Lavi.Buchnik(a)exlibrisgroup.com [cid:image002.jpg@01D710F9.A61823E0] www.exlibrisgroup.com<http://www.exlibrisgroup.com/>

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.5.8)
by Tal Nisan 03 Mar '21

03 Mar '21

1 0

engine build error: method does not override or implement a method from a supertype
by Sandro Bonazzola 01 Mar '21

01 Mar '21

Hi, can anybody help solving the error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project restapi-jaxrs: Compilation failure [ERROR] /home/jenkins/workspace/ovirt-engine_standard-check-patch/ovirt-engine/backend/manager/modules/restapi/jaxrs/src/main/java/org/ovirt/engine/api/restapi/resource/BackendVmResource.java:[365,5] method does not override or implement a method from a supertype [ERROR] or explaining why this is happening on patch https://gerrit.ovirt.org/#/c/ovirt-engine/+/113464/ Please comment on the patch :-) 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.*

1 0