- Devel - oVirt List Archives

Re: RHV and oVirt CBT issue
by Nir Soffer 27 Jul '21

27 Jul '21

On Tue, Jul 27, 2021 at 9:47 AM luwen.zhang <luwen.zhang(a)vinchin.com> wrote: > > Dear team could you please help on the below issue? > > Thanks Sandro for the advice! > On 07/27/2021 14:22，Sandro Bonazzola<sbonazzo(a)redhat.com> > <sbonazzo(a)redhat.com> wrote： > > I would recommend to ask this on devel(a)ovirt.org. > Looping in +Eyal Shenitzky <eshenitz(a)redhat.com> > > Il giorno mar 27 lug 2021 alle ore 08:14 luwen.zhang < > luwen.zhang(a)vinchin.com> ha scritto: > >> >> Dear team, >> >> We had implemented CBT support for RHV and oVirt in our new version, but >> when testing we encountered problems of obtain VM increments and also had >> abnormal with the VM virtual disks. >> >> Our testing environment as below: >> OS Version: RHEL - 8.4.2105.0 - 3.el8 >> OS Description: oVirt Node 4.4.7 >> Kernel Version: 4.18.0 - 315.el8.x86_64 >> KVM Version: 6.0.0 - 19.el8s >> LIBVIRT Version: libvirt-7.4.0-1.el8s >> VDSM Version: vdsm-4.40.70.6-1.el8 >> >> One of the problem is after a successful backup, the VM which gets only >> one virtual disk will get 2 identical virtual disks marked as Complete on >> oVirt engine web console, like shown below. >> >> The additional disk might disappear after a while, but before it’s gone >> there could be a lot of problems with the VM. >> >> 1. We cannot perform a new backup, the backup will fail directly. >> >> 2. The VM itself will run into exception, we cannot even power it off, >> and it will also probably get crashed. >> >> 3. If the VM was initially powered off, after backing up, we cannot power >> on the VM. >> >> And there could be some other problems related with this, is this normal >> or there’s something we did wrong? >> >> Thank you in advance for your help! >> > Unfortunately you are hitting this bug: https://bugzilla.redhat.com/1980428 The bug is fixed in 4.4.7 async release, which should be available now according to the bug. Please upgrade to the latest 4.4.7 version. Nir

2 1

Re: RHV and oVirt CBT issue
by luwen.zhang 27 Jul '21

27 Jul '21

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.8.1)
by Tal Nisan 21 Jul '21

21 Jul '21

2 1

Reminder : last week for submitting an abstract for ovirt conference
by Sandro Bonazzola 21 Jul '21

21 Jul '21

Just a reminder that call for papers closes on July 25 and this is the last week! -- 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://mojo.redhat.com/docs/DOC-1199578>*

1 0

Blog post - Using Ceph only storage for oVirt datacenter
by Sandro Bonazzola 15 Jul '21

15 Jul '21

Hi, I just published the result of the testing of oVirt 4.4.7 with Ceph Pacific and RDO Victoria for deploying an oVirt datacenter using Ceph as storage with a blog post at https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente… Comments and suggestions are welcome. 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 7

a kind reminder oVirt 2021 CfP closing in 11 days
by Sandro Bonazzola 14 Jul '21

14 Jul '21

Hi, a kind reminder oVirt 2021 CfP closing in 11 days. More details: https://blogs.ovirt.org/ovirt-2021-online-conference/ Looking forward to user stories, developers onboarding journeys, integration stories, new features presentation, old features nobody knows about because nobody presented them before and more you see fit. -- 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

ovirt-engine has been tagged (ovirt-engine-4.4.8)
by Tal Nisan 14 Jul '21

14 Jul '21

1 0

OST failure, bad comment
by Nir Soffer 12 Jul '21

12 Jul '21

OST failed, and posted unprocessed comment: OST Verified -1 Patch Set 1: Verified-1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 : OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER failed with: $OST_MESSAGE https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a Looking at: https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 It looks like environment issue: ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer hudson.slaves.SlaveComputer@2e2cb321 and has channel null So we have 2 issues: 1. If build fails, error is not handled properly producing bad comment 2. the actual build failure The first issue should be handled by posting a better comment: OST build error: https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 And OST should not mark the patch as verified -1, since it did not run any test. Marking a patch as -1 means some tests have failed, and the author needs to check why. A build error means OST or CI maintainers need to check why the error happened.

2 2

test_cold_incremental_backup_vm2: "Cannot backup VM. The VM is during a backup operation"
by Yedidyah Bar David 08 Jul '21

08 Jul '21

On Sun, Jul 4, 2021 at 8:26 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… > Build Number: 1291 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1291 > [Marcin Sobczyk] network: Add missing 'ansible_hosts' fixture > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: basic-suite-master.test-scenarios.test_004_basic_sanity.test_cold_incremental_backup_vm2 > > Error Message: > ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot backup VM. The VM is during a backup operation.]". HTTP response code is 409. Something similar now happened to me too: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/17729/ https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/17729… This job triggered also he-basic, which passed. basic failed as in here. Any idea? Best regards, > > Stack Trace: > engine_api = <ovirtsdk4.Connection object at 0x7f1f943c3208> > get_vm_service_for_vm = <function get_vm_service_for_vm.<locals>.service_for at 0x7f1f944e1268> > > @order_by(_TEST_LIST) > def test_cold_incremental_backup_vm2(engine_api, get_vm_service_for_vm): > _verify_vm_state(engine_api.system_service(), VM2_NAME, types.VmStatus.DOWN) > vm2_backups_service = get_vm_service_for_vm(VM2_NAME).backups_service() > backup.perform_incremental_vm_backup( > > engine_api, vm2_backups_service, DISK2_NAME, "cold_vm_backup") > > basic-suite-master/test-scenarios/test_004_basic_sanity.py:1056: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > ost_utils/ost_utils/storage_utils/backup.py:75: in perform_incremental_vm_backup > correlation_id="incremental_" + correlation_id) > ost_utils/ost_utils/storage_utils/backup.py:34: in perform_vm_backup > ), query={'correlation_id': correlation_id} > /usr/lib64/python3.6/site-packages/ovirtsdk4/services.py:34139: in add > return self._internal_add(backup, headers, query, wait) > /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:232: in _internal_add > return future.wait() if wait else future > /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:55: in wait > return self._code(response) > /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:229: in callback > self._check_fault(response) > /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:132: in _check_fault > self._raise_error(response, body) > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > response = <ovirtsdk4.http.Response object at 0x7f1f94399c50> > detail = <ovirtsdk4.types.Fault object at 0x7f1f94399f60> > > @staticmethod > def _raise_error(response, detail=None): > """ > Creates and raises an error containing the details of the given HTTP > response and fault. > > This method is intended for internal use by other components of the > SDK. Refrain from using it directly, as backwards compatibility isn't > guaranteed. > """ > fault = detail if isinstance(detail, types.Fault) else None > > msg = '' > if fault: > if fault.reason: > if msg: > msg += ' ' > msg = msg + 'Fault reason is "%s".' % fault.reason > if fault.detail: > if msg: > msg += ' ' > msg = msg + 'Fault detail is "%s".' % fault.detail > if response: > if response.code: > if msg: > msg += ' ' > msg = msg + 'HTTP response code is %s.' % response.code > if response.message: > if msg: > msg += ' ' > msg = msg + 'HTTP response message is "%s".' % response.message > > if isinstance(detail, six.string_types): > if msg: > msg += ' ' > msg = msg + detail + '.' > > class_ = Error > if response is not None: > if response.code in [401, 403]: > class_ = AuthError > elif response.code == 404: > class_ = NotFoundError > > error = class_(msg) > error.code = response.code if response else None > error.fault = fault > > raise error > E ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot backup VM. The VM is during a backup operation.]". HTTP response code is 409. > > /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:118: Error_______________________________________________ > 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/PCZSYD7BHWGVM… -- Didi

4 3

importing fixtures in ovirt-system-tests
by Yedidyah Bar David 08 Jul '21

08 Jul '21

Hi all, We have several different styles of where/how to import fixtures in ovirt-system-tests: - import directly inside the test code - import in conftest.py - import in fixtures modules - For all of above, both 'import *' and importing specific fixtures I think we should try to agree on a specific style and then follow it. One drawback of importing directly in test/fixtures code is that it's then impossible to override them in conftest.py. A drawback of importing '*' and/or doing this in conftest.py is that you might inadvertently import more than you want, or this might happen eventually (after more stuff are added), that this makes it harder to find what uses what, and that it risks unintended collisions in names - as opposed to intended overrides. A related issue is having to update many places if you add/change something. If there is some kind of "best practices" document somewhere that people are happy with, perhaps we should follow it. Otherwise, we should come up with our own. Personally I think I'd like to have a single file with all the imports, of specific fixtures (not '*'), and import this file from conftest.py of all the suites. Didn't actually try this and no idea what complications it might bring. Comments/ideas/opinions/decisions are welcome :-) Best regards, -- Didi

3 2