November 2021 - 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

[OST] Documentation update needed
by Aviv Litman 15 Dec '21

15 Dec '21

Hi All, I tried to follow the steps documented in oVirt System Tests Docs <https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/inde…> . After consulting with Marcin, I understand that we haven't use ./run_suite.sh for a loong time now. I think the right command is for example: ./ost.sh run basic-suite-master el8stream --custom-repo= https://jenkins.ovirt.org/job/ovirt-dwh_standard-check-patch/1346/ We don't know who maintains this docs. Thanks! -- Aviv Litman BI Associate Software Engineer Red Hat <https://www.redhat.com/> alitman(a)redhat.com <https://www.redhat.com/>

3 3

oVirt Community - open discussion around repositories and workflows
by Sandro Bonazzola 03 Dec '21

03 Dec '21

Dear community members, We would like to take some next steps in improving usability and general decision making for our community and are interested in your thoughts and suggestions. The first step is a decision regarding our version control and workflows associated with it. Contributions to new features and general improvements for oVirt outside of Red Hat have been rare and we would like to hear from you if we could simplify this process for you. One suggestion we have is that we could simplify the contribution process and improve the contributor experience by moving our repositories to GitHub or GitLab. Currently, our Gerrit (gerrit.ovirt.org) instance is mirrored to GitHub and we already have several repositories that are exclusively developed there, including their CI running on GitHub Actions, for example: * https://github.com/oVirt/go-ovirt-client * https://github.com/oVirt/512-byte-vm There are also various related projects that run on GitLab, such as: * https://gitlab.com/qemu-project * https://gitlab.com/libvirt One recent project that moved from Gerrit to GitLab with a very similar discussion is mediawiki: https://www.mediawiki.org/wiki/GitLab_consultation/Discussion_summary Once we hear more of your thoughts around this and if the decision falls on moving to either GitHub or GitLab, our plan would be to start changing existing workflows and CI project by project as it makes sense. Both platforms offer similar features. Two key points that stand out for us are that: * GitLab is open source while GitHub isn't * GitHub is more visible which allows contributors to amplify their contributions and raise their profile by contributing to various big projects, including oVirt We are looking forward to hearing your thoughts, -- 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 10

Another CI failure
by Milan Zamazal 02 Dec '21

02 Dec '21

Hi, as demonstrated in https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31133/, OST builds can at least start now but still fail, apparently due to the following: + sudo -n usermod -a -G jenkins qemu usermod: user 'qemu' does not exist + log ERROR 'Failed to add user qemu to group jenkins' + local level=ERROR + shift + local 'message=Failed to add user qemu to group jenkins' + local prefix + [[ 4 -gt 1 ]] + prefix='global_setup[lago_setup]' + echo 'global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins' global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins + return 1 + failed=true What can be done about it? Thanks, Milan

3 4

Failed CI for engine patches - java-client-kubevirt otopi
by Shani Leviim 01 Dec '21

01 Dec '21

Hi, I have a series of engine patches that keep failing although the chain is rebased on the latest master. I ran 'ci build' a couple of minutes ago and it failed with this one: 11:08:45 No match for argument: otopi 11:08:45 Error: Unable to find a match: java-client-kubevirt otopi https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15286/conso… The engine patches: https://gerrit.ovirt.org/q/topic:%22copy-template-mbs-disk%22+(status:open%… Can someone assist, please? *Regards,* *Shani Leviim*

7 11

Opened PRs in ovirt-engine Github
by Saif Abu Saleh 30 Nov '21

30 Nov '21

Hi, I noticed there is this pull requests: https://github.com/oVirt/ovirt-engine/pull/29 https://github.com/oVirt/ovirt-engine/pull/31 That opened to ovirt-engine Github repository, is anyone looking into them? Thanks, Saif

2 1

COPR: How add new project as ovirt-master-snapshots package
by Artur Socha 29 Nov '21

29 Nov '21

Hi Sandro, (** I have included dev@ovirt in CC because the answer might be useful to others as well **) I have created a new gerrit project / package 'ovirt-engine-keycloak' [1] and I would like to somehow enable the COPR build. I saw there is 'ovirt-master-snapshot' [2] that has multiple packages configured ie. vdsm-jsonrpc-java that I searched for reference. What is the process to add a new package there (ie. some patch somewhere, ticket or just pinging relevant people, any special setup in GH repo besides .copr/Makefile)? [1] https://gerrit.ovirt.org/#/q/project:ovirt-engine-keycloak [2] https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/package… thanks! -- Artur Socha Senior Software Engineer, RHV Red Hat

2 2

oVirt Dashpanel - see all open issues and PRs on GitHub
by Sanja Bonic 29 Nov '21

29 Nov '21

Hi everyone, In the ovirt-site repository, we now have an overview of all open issues and PRs: https://github.com/oVirt/ovirt-site/blob/dashpanel/dashpanel-ovirt.md Archived and private repositories are excluded from this list. The .md is linked from https://www.ovirt.org/community/ in the "Developers" section and is updated automatically every day using GitHub Actions. If you have any questions or comments, please let us know. Cheers, Sanja

2 1

ovirt-engine dependency on ovirt-engine-extensions-api
by Sandro Bonazzola 29 Nov '21

29 Nov '21

Hi, In ovirt-engine pom.xml there's a requirement for build time on ovirt-engine-extensions-api = 1.0.0. This dependency is available on maven central so online build works. Any clue on why we are not requiring 1.0.1 <https://search.maven.org/artifact/org.ovirt.engine.api/ovirt-engine-extensi…> instead ? We are packaging ovirt-engine-extensions-api during the development but it ships 1.0.2.SNAPSHOT so when building in offline mode (needed for building on CentOS Virt SIG) it fails as the 1.0.0 artifact was never downloaded. I can rebuild ovirt-engine-extensions-api from 1.0.0 or 1.0.1 which are available in maven central too as requiring explicitly 1.0.2.SNAPSHOT fails with: Failed to execute goal on project common-dependencies: Could not resolve dependencies for project org.ovirt.engine.core.manager:common-dependencies:jar:4.5.0-SNAPSHOT: The following artifacts could not be resolved: org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT, org.ovirt.java-client-kubevirt:java-client-kubevirt:jar:0.5.0, org.apache.sshd:sshd-common:jar:2.6.0, org.apache.sshd:sshd-core:jar:2.6.0, net.i2p.crypto:eddsa:jar:0.3.0, org.ovirt.engine.api:metamodel-server:jar:1.3.7, org.ovirt.vdsm-jsonrpc-java:vdsm-jsonrpc-java-client:jar:1.6.0, com.fasterxml.jackson.core:jackson-databind:jar:2.12.1, org.jboss.resteasy:resteasy-jaxrs:jar:3.9.3.Final, com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.12.1, org.apache.httpcomponents:httpclient:jar:4.5.13: Could not find artifact org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT -> [Help 1] Any recommendations on how to proceed? -- 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.*

2 4

GitHub Actions-based CI for vdsm
by Marcin Sobczyk 28 Nov '21

28 Nov '21

Hi All, I've been working on adding GitHub Actions-based CI to vdsm today. Feel free to check out the patches here: https://gerrit.ovirt.org/q/topic:%22github-actions-ci%22+(status:open%20OR%… Some comments: - the linters work fine already, we can start using them - RPM building works too in general. I think the RPM versions are not right yet, so I'll look into this. After the 'rpm' job is done we get a zipfile with all the built RPMs inside. In the future we may want to run 'createrepo_c' on this dir as well, so we'll have a ready-to-be-used repository in that zip. - 'tests' are working too, but we have a couple of failures we'd need to look at. This job, unlike the others, runs in GitHub's Ubuntu VM inside which we use a privileged container for running the tests. - didn't try 'tests-storage' yet - Not to waist precious free CI minutes and storage, we run linters first, tests after that, but only under the condition that the linters didn't fail, and finally we build RPMs, but this time under the condition that the tests didn't fail. You can find some of the runs I made in my personal fork here: https://github.com/tinez/vdsm/actions/workflows/ci.yml Comments, remarks and reviews are highly appreciated. Regards, Marcin

2 3

CI failing all the time
by Milan Zamazal 28 Nov '21

28 Nov '21

Hi, all patches uploaded today I've seen (for Engine and Vdsm) fail due to problems with availability of packages when preparing the el7 environment. For example: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15291/ Additionally, Vdsm tests are not run on PSI. Does anybody know what's wrong and how to fix it? Can it be related to the Jenkins move? Thanks, Milan

7 11

Build artifacts jobs always fail - OST cannot run
by Nir Soffer 28 Nov '21

28 Nov '21

Since last week, all build artifacts jobs fail with "Testing system error": - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31062/artifact/ci_b… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31064/artifact/ci_b… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31063/artifact/ci_b… This breaks OST, waiting for the builds. The error seems to be in global_setup.sh: [2021-11-26T16:02:21.443Z] + sudo -n systemctl start libvirtd haveged firewalld [2021-11-26T16:02:21.443Z] Failed to start libvirtd.service: Unit not found. [2021-11-26T16:02:21.443Z] Failed to start haveged.service: Unit not found. Nir

1 0

java-client-kubevirt in 4.5
by Sandro Bonazzola 26 Nov '21

26 Nov '21

hi, java-client-kubevirt is failing on missing dependencies: package: java-client-kubevirt-0.5.0-1.20211108071009.gite0a0fe8.el9.src from copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot unresolved deps: maven-plugin-registry maven-profile maven-shade-plugin I'm providing those dependencies temporarily with ovirt-master-snapshot-static repo. I kindly asked for them to be added to CentOS Stream 9 (see as example Bug 2017712 <https://bugzilla.redhat.com/show_bug.cgi?id=2017712> - Missing maven-shade-plugin in CentOS Stream 9 ) But the request was rejected. We have a few options: 1) Ask for building on CentOS Stream 9 Koji instance at https://kojihub.stream.centos.org/koji/ as that dependency is available there in build roots. 2) Change java-client-kubevirt for not requiring those packages (bundling the needed jar files within the .src.rpm?) 3) Drop java-client-kubevirt completely in oVirt 4.5 4) Rebuild the whole maven stack up to those dependencies within CentOS Virt SIG and COPR. 5) Keep the "temporary" solution as-is How should we proceed? -- 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.*

3 4

Gerrit https links broken (since server was moved?)
by Nir Soffer 25 Nov '21

25 Nov '21

Trying to "git pull" from gerrit get stuck now. Checking https://gerrit.ovirt.org/admin/repos/vdsm we see: git clone "https://gerrit.ovirt.org/vdsm" But visiting this url shows: $ curl -i https://gerrit.ovirt.org/vdsm HTTP/1.1 404 Not Found Date: Thu, 25 Nov 2021 12:12:17 GMT Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips Content-Type: text/plain;charset=iso-8859-1 Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: Mon, 01 Jan 1990 00:00:00 GMT Content-Length: 9 Not Found Same for ovirt-engine: $ curl -i https://gerrit.ovirt.org/ovirt-engine HTTP/1.1 404 Not Found Date: Thu, 25 Nov 2021 12:13:13 GMT Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips Content-Type: text/plain;charset=iso-8859-1 Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: Mon, 01 Jan 1990 00:00:00 GMT Content-Length: 9 Not Found I guess this is related to moving to new hardware yesterday? Nir

2 1

build failure for vdsm-jsonrpc-java on cbs.centos.org
by Sandro Bonazzola 25 Nov '21

25 Nov '21

Hi, can you please have a look at https://cbs.centos.org/kojifiles/work/tasks/8084/2608084/build.log ? I think it may be related to no open network within the mock environment in cbs.centos.org. If so, how can I disable the test during the build? The full task is here: https://cbs.centos.org/koji/taskinfo?taskID=2608074 -- 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.*

2 1

Planned CI system outage
by Evgheni Dereveanchin 24 Nov '21

24 Nov '21

Hi everyone, Today we're moving jenkins.ovirt.org to new hardware which requires an outage for all CI-related systems. Due to the size of this system, the expected outage window is from 16:00 UTC till 22:00 UTC - no builds will be run during this outage and the Jenkins UI will be unreachable. I will follow up with updates after the move is complete. -- Regards, Evgheni Dereveanchin

1 1

build failure for ovirt-engine-extension-aaa-jdbc on cbs.centos.org
by Sandro Bonazzola 24 Nov '21

24 Nov '21

Hi, can you please have a look at build failure on https://cbs.centos.org/kojifiles/work/tasks/8057/2608057/build.log ? Not sure what happened there. The full task is here: https://cbs.centos.org/koji/taskinfo?taskID=2608050 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

[VDSM] Warning: vdsm CI fails, looks like lvm regression in 8.6/stream
by Nir Soffer 24 Nov '21

24 Nov '21

All vdsm CI runs fails now due to: https://bugzilla.redhat.com/2025527 Looks like leftover configuration (locking_type=4) from rhel 7 that was useless but harmless on rhel 8 is harmful now, converted by lvm to --readonly, which breaks lvchange --refresh. So far seen only in vdsm CI, using Centos Stream. It is likely to break also on a real system using the same lvm version (unknown yet). I posted this to log lvm version: https://gerrit.ovirt.org/c/vdsm/+/117741 Nir

1 3

OST gating: Merge aborted
by Milan Zamazal 22 Nov '21

22 Nov '21

Hi, https://gerrit.ovirt.org/c/vdsm/+/117543 reached "OST merge attempted" but the merge hasn't happened. The trigger log says: + echo 'OST_MESSAGE=Patch is good to merge' + touch verified + exit 0 [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path 'ost' [EnvInject] - Variables injected successfully. [ds-ost-gating-trigger3] $ /bin/sh -xe /tmp/jenkins3506416413422390774.sh + [[ -f approved ]] + [[ -f verified ]] + echo 'will submit' will submit + exit 0 Build step 'Groovy Postbuild' changed build result to ABORTED Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: ABORTED Any idea what's wrong? Thanks, Milan

2 2

ovirt-engine has been tagged (ovirt-engine-4.4.10)
by Sandro Bonazzola 20 Nov '21

20 Nov '21

ovirt-engine has been tagged (ovirt-engine-4.4.10) -- 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.5.0_alpha1)
by Sandro Bonazzola 19 Nov '21

19 Nov '21

ovirt-engine has been tagged (ovirt-engine-4.5.0_alpha1) -- 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.*

2 1

OST gating oddities
by Milan Zamazal 19 Nov '21

19 Nov '21

Hi, putting recently experienced problems with OST runs failures aside, I wonder about what currently happens in gerrit on gating. For instance in https://gerrit.ovirt.org/c/vdsm/+/117523/6: - OST OST -1 Patch Set 6: OST-1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4579 : Looking for build artifacts for OST. ci build * Why setting OST-1 when looking for a build? - Jenkins CI Patch Set 6: No Builds Executed https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30672/ : To avoid overloading the infrastructure, a whitelist for running gerrit triggered jobs has been set in place, if you feel like you should be in it, please contact infra at ovirt dot org. * OST not allowed to trigger builds? - OST OST +1 Patch Set 6: OST+1 https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4583 : start OST for https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30681/ * Shouldn't OST set OST+1 after it runs rather than when it starts? Is there any explanation of these phenomenons? Thanks, Milan

3 4

Another CI problem: git not working
by Milan Zamazal 18 Nov '21

18 Nov '21

Hi, another problem that has been observed several times in CI runs on gerrit last days is: ERROR: Error cloning remote repo 'origin' [2021-11-18T16:43:38.688Z] hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: [2021-11-18T16:43:38.688Z] stdout: [2021-11-18T16:43:38.688Z] stderr: error: RPC failed; result=6, HTTP code = 0 [2021-11-18T16:43:38.688Z] fatal: The remote end hung up unexpectedly See https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30774/ for an example. Would it be possible to get it fixed? Thanks, Milan

1 0

qemu-kvm 6.1.0 breaks hosted-engine
by Yedidyah Bar David 18 Nov '21

18 Nov '21

Hi all, For a few days now we have failures in CI of the he-basic suite. At one point the failure seemed to have been around networking/routing/firewalling, but later it changed, and now the deploy process fails while trying to first start the engine vm after it's copied to the shared storage. I ran locally OST he-basic with current ost-images, reproduced the issue, and managed to "fix" it by enabling ovirt-master-centos-stream-advanced-virtualization-testing and downgrading qemu-kvm-* from 6.1.0 (from AppStream) to 15:6.0.0-33.el8s. Is this a known issue? How do we handle? Perhaps we should conflict with it somewhere until we find and fix the root cause. Please note that the flow is: 1. Create a local VM from the appliance image 2. Do stuff on this machine 3. Shut it down 4. Copy its disk to shared storage 5. Start the machine from the shared storage And that (1.) did work with 6.1.0, and also (5.) did work with 6.0.0 (so the copying (using qemu-img) did work well) and the difference is elsewhere. Following is the diff between the qemu commands of (1.) and (5.) (as found in the respective logs). Any clue? --- localq 2021-11-16 08:48:01.230426260 +0100 +++ sharedq 2021-11-16 08:48:46.884937598 +0100 @@ -1,54 +1,79 @@ -2021-11-14 15:09:56.430+0000: starting up libvirt version: 7.9.0, package: 1.module_el8.6.0+983+a7505f3f (CentOS Buildsys <bugs(a)centos.org>, 2021-11-09-20:38:08, ), qemu version: 6.1.0qemu-kvm-6.1.0-4.module_el8.6.0+983+a7505f3f, kernel: 4.18.0-348.el8.x86_64, hostname: ost-he-basic-suite-master-host-0.lago.local +2021-11-14 15:29:10.686+0000: starting up libvirt version: 7.9.0, package: 1.module_el8.6.0+983+a7505f3f (CentOS Buildsys <bugs(a)centos.org>, 2021-11-09-20:38:08, ), qemu version: 6.1.0qemu-kvm-6.1.0-4.module_el8.6.0+983+a7505f3f, kernel: 4.18.0-348.el8.x86_64, hostname: ost-he-basic-suite-master-host-0.lago.local LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ -HOME=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal \ -XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/.local/share \ -XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/.cache \ -XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/.config \ +HOME=/var/lib/libvirt/qemu/domain-2-HostedEngine \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-2-HostedEngine/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-2-HostedEngine/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-2-HostedEngine/.config \ /usr/libexec/qemu-kvm \ --name guest=HostedEngineLocal,debug-threads=on \ +-name guest=HostedEngine,debug-threads=on \ -S \ --object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/master-key.aes"}' \ --machine pc-q35-rhel8.5.0,accel=kvm,usb=off,dump-guest-core=off,memory-backend=pc.ram \ --cpu Cascadelake-Server,ss=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,umip=on,pku=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,tsx-ctrl=on,hle=off,rtm=off,kvmclock=on \ --m 3171 \ --object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":3325034496}' \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-HostedEngine/master-key.aes"}' \ +-machine pc-q35-rhel8.4.0,accel=kvm,usb=off,dump-guest-core=off,graphics=off \ +-cpu Cascadelake-Server-noTSX,mpx=off \ +-m size=3247104k,slots=16,maxmem=12988416k \ -overcommit mem-lock=off \ --smp 2,sockets=2,cores=1,threads=1 \ --uuid 716b26d9-982b-4c51-ac05-646f28346007 \ +-smp 2,maxcpus=32,sockets=16,dies=1,cores=2,threads=1 \ +-object '{"qom-type":"iothread","id":"iothread1"}' \ +-object '{"qom-type":"memory-backend-ram","id":"ram-node0","size":3325034496}' \ +-numa node,nodeid=0,cpus=0-31,memdev=ram-node0 \ +-uuid a10f5518-1fc2-4aae-b7da-5d1d9875e753 \ +-smbios type=1,manufacturer=oVirt,product=RHEL,version=8.6-1.el8,serial=d2f36f31-bb29-4e1f-b52d-8fddb632953c,uuid=a10f5518-1fc2-4aae-b7da-5d1d9875e753,family=oVirt \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=40,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ --rtc base=utc \ +-rtc base=2021-11-14T15:29:08,driftfix=slew \ +-global kvm-pit.lost_tick_policy=delay \ +-no-hpet \ -no-shutdown \ -global ICH9-LPC.disable_s3=1 \ -global ICH9-LPC.disable_s4=1 \ --boot menu=off,strict=on \ +-boot strict=on \ -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ --device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ --blockdev '{"driver":"file","filename":"/var/tmp/localvm1hjkqhu2/images/b4985de8-fa7e-4b93-a93c-f348ef17d91e/b1614c86-bf90-44c4-9f5d-fd2b3c509934","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ --blockdev '{"node-name":"libvirt-2-format","read-only":false,"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ --device virtio-blk-pci,bus=pci.3,addr=0x0,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 \ --blockdev '{"driver":"file","filename":"/var/tmp/localvm1hjkqhu2/seed.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ --blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ --device ide-cd,bus=ide.0,drive=libvirt-1-format,id=sata0-0-0 \ --netdev tap,fd=42,id=hostnet0,vhost=on,vhostfd=43 \ --device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:52:4d:89:07:dc,bus=pci.1,addr=0x0 \ --chardev pty,id=charserial0 \ +-device pcie-root-port,port=21,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ +-device pcie-root-port,port=22,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \ +-device pcie-root-port,port=23,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \ +-device pcie-root-port,port=24,chassis=9,id=pci.9,bus=pcie.0,multifunction=on,addr=0x3 \ +-device pcie-root-port,port=25,chassis=10,id=pci.10,bus=pcie.0,addr=0x3.0x1 \ +-device pcie-root-port,port=26,chassis=11,id=pci.11,bus=pcie.0,addr=0x3.0x2 \ +-device pcie-root-port,port=27,chassis=12,id=pci.12,bus=pcie.0,addr=0x3.0x3 \ +-device pcie-root-port,port=28,chassis=13,id=pci.13,bus=pcie.0,addr=0x3.0x4 \ +-device pcie-root-port,port=29,chassis=14,id=pci.14,bus=pcie.0,addr=0x3.0x5 \ +-device pcie-root-port,port=30,chassis=15,id=pci.15,bus=pcie.0,addr=0x3.0x6 \ +-device pcie-root-port,port=31,chassis=16,id=pci.16,bus=pcie.0,addr=0x3.0x7 \ +-device pcie-root-port,port=32,chassis=17,id=pci.17,bus=pcie.0,addr=0x4 \ +-device pcie-pci-bridge,id=pci.18,bus=pci.1,addr=0x0 \ +-device qemu-xhci,p2=8,p3=8,id=ua-56e0dd42-5016-4a70-b2b6-7e3bfbc4002f,bus=pci.4,addr=0x0 \ +-device virtio-scsi-pci,iothread=iothread1,id=ua-1ba84ec0-6eb7-4e4c-9e5f-f446e0b2e67c,bus=pci.3,addr=0x0 \ +-device virtio-serial-pci,id=ua-5d6442e9-af6c-459a-8105-6d0cd90214a6,max_ports=16,bus=pci.5,addr=0x0 \ +-device ide-cd,bus=ide.2,id=ua-8a1b74dd-0b24-4f88-9df1-81d4cb7f404c,werror=report,rerror=report \ +-blockdev '{"driver":"host_device","filename":"/run/vdsm/storage/8468bc65-907a-4c95-8f93-4d29fa722f62/5714a85b-8d09-4ba6-a89a-b39f98e664ff/68f4061e-a537-4051-af1e-baaf04929a25","aio":"native","node-name":"libvirt-1-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ +-device virtio-blk-pci,iothread=iothread1,bus=pci.6,addr=0x0,drive=libvirt-1-format,id=ua-5714a85b-8d09-4ba6-a89a-b39f98e664ff,bootindex=1,write-cache=on,serial=5714a85b-8d09-4ba6-a89a-b39f98e664ff,werror=stop,rerror=stop \ +-netdev tap,fds=44:45,id=hostua-33528c78-5281-4ebd-a5e2-5e8894d6a4aa,vhost=on,vhostfds=46:47 \ +-device virtio-net-pci,mq=on,vectors=6,host_mtu=1500,netdev=hostua-33528c78-5281-4ebd-a5e2-5e8894d6a4aa,id=ua-33528c78-5281-4ebd-a5e2-5e8894d6a4aa,mac=54:52:4d:89:07:dc,bus=pci.2,addr=0x0 \ +-chardev socket,id=charserial0,fd=48,server=on,wait=off \ -device isa-serial,chardev=charserial0,id=serial0 \ --chardev socket,id=charchannel0,fd=45,server=on,wait=off \ --device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ --audiodev id=audio1,driver=none \ --vnc 127.0.0.1:0,sasl=on,audiodev=audio1 \ --device VGA,id=video0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ --object '{"qom-type":"rng-random","id":"objrng0","filename":"/dev/random"}' \ --device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.4,addr=0x0 \ +-chardev socket,id=charchannel0,fd=49,server=on,wait=off \ +-device virtserialport,bus=ua-5d6442e9-af6c-459a-8105-6d0cd90214a6.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-chardev spicevmc,id=charchannel1,name=vdagent \ +-device virtserialport,bus=ua-5d6442e9-af6c-459a-8105-6d0cd90214a6.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 \ +-chardev socket,id=charchannel2,fd=50,server=on,wait=off \ +-device virtserialport,bus=ua-5d6442e9-af6c-459a-8105-6d0cd90214a6.0,nr=3,chardev=charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0 \ +-audiodev id=audio1,driver=spice \ +-spice port=5900,tls-port=5901,addr=192.168.200.3,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on \ +-device qxl-vga,id=ua-60b147e1-322a-4f49-bb16-0e7a76732396,ram_size=67108864,vram_size=33554432,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ +-device intel-hda,id=ua-fe1a3722-6c25-4719-9d0b-baeeb5d74a3e,bus=pci.18,addr=0x1 \ +-device hda-duplex,id=ua-fe1a3722-6c25-4719-9d0b-baeeb5d74a3e-codec0,bus=ua-fe1a3722-6c25-4719-9d0b-baeeb5d74a3e.0,cad=0,audiodev=audio1 \ +-device virtio-balloon-pci,id=ua-bd2a17f1-4d39-4d4d-8793-089081a2065c,bus=pci.7,addr=0x0 \ +-object '{"qom-type":"rng-random","id":"objua-7e3d85f3-15da-4f97-9434-90396750e2b2","filename":"/dev/urandom"}' \ +-device virtio-rng-pci,rng=objua-7e3d85f3-15da-4f97-9434-90396750e2b2,id=ua-7e3d85f3-15da-4f97-9434-90396750e2b2,bus=pci.8,addr=0x0 \ +-device vmcoreinfo \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on -char device redirected to /dev/pts/1 (label charserial0) -2021-11-14 15:18:02.749+0000: Domain id=1 is tainted: custom-ga-command +2021-11-14T15:44:46.647989Z qemu-kvm: terminating on signal 15 from pid 21473 (<unknown process>) Best regards, -- Didi

4 8

CI fails to clone git repo
by Vojtech Juranek 16 Nov '21

16 Nov '21

Hi, CI fails to clone git repo, fails with: stderr: fatal: unable to access 'https://gerrit.ovirt.org/jenkins/': Could not resolve host: gerrit.ovirt.org; Unknown error See [1] for full log. Could you please take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30631/console

2 1

suspend resume test broken
by Michal Skrivanek 16 Nov '21

16 Nov '21

HI all, suspend/resume is currently broken on master/el8stream, can anyone please take a look and find out the reason and fix it? Thanks, michal

1 1

Bugs easy to fix but left behind for more important ones
by Sandro Bonazzola 16 Nov '21

16 Nov '21

Hi, there's a bunch of bugs which are easy to fix and can possibly be fixed also by someone with little / no programming experience. They are low priority, low severity, and likely going to be closed deferred / wontfix due to capacity by the end of the 4.5.0 development cycle. But if you have time and you want to try to contribute to oVirt for the first time, these are likely to be easy enough to let you contribute. *Bug 1581672* <https://bugzilla.redhat.com/show_bug.cgi?id=1581672> - [TEXT] add help for --otopi-environment to ovirt-engine-provisiondb tool *Bug 2000121* <https://bugzilla.redhat.com/show_bug.cgi?id=2000121> - docs/comments/etc misguide about postgresql credentials defaults *Bug 1999049* <https://bugzilla.redhat.com/show_bug.cgi?id=1999049> - hosted engine installation fails if locale is Greek If you give it a try and you have issues please let me know, I'll try to help unblock you. 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

OST: Vdsm: Occasional failures when stopping vdsmd
by Milan Zamazal 15 Nov '21

15 Nov '21

Hi, Michal has observed occasional OST failures in test_vdsm_recovery last days, which hadn't been seen before. When `systemctl stop vdsmd' is called (via Ansible) there, vdsmd (almost?) never finishes its shutdown within the 10 seconds timeout and gets then killed with SIGKILL. If this action is accompanied by "Job for vdsmd.service canceled." message then the test fails; otherwise OST continues normally. The situation is reproducible by running OST basic-suite-master and making it artificially failing after test_vdsm_recovery. Then running `systemctl stop vdsmd' manually on the given OST host (can be done repeatedly, so it provides a good opportunity to examine the problem). There are two problems there: - "Job for vdsmd.service canceled." message that sometimes occurs after `systemctl stop vdsmd' and then the test fails. I don't know what it means and I can't identify any difference in journal between when the message occurs and when it doesn't. - The fact that Vdsm doesn't stop within the timeout and must be killed. This doesn't happen in my normal oVirt installation. It apparently blocks in self.irs.prepareForShutdown() call from clientIF.py. Journal says: systemd[1]: Stopping Virtual Desktop Server Manager... systemd[1]: vdsmd.service: State 'stop-sigterm' timed out. Killing. systemd[1]: vdsmd.service: Killing process 132608 (vdsmd) with signal SIGKILL. systemd[1]: vdsmd.service: Killing process 133445 (ioprocess) with signal SIGKILL. systemd[1]: vdsmd.service: Killing process 133446 (ioprocess) with signal SIGKILL. systemd[1]: vdsmd.service: Killing process 133447 (ioprocess) with signal SIGKILL. systemd[1]: vdsmd.service: Main process exited, code=killed, status=9/KILL systemd[1]: vdsmd.service: Failed with result 'timeout'. systemd[1]: Stopped Virtual Desktop Server Manager. And vdsm.log (from a different run, sorry): 2021-11-12 07:09:30,274+0000 INFO (MainThread) [vdsm.api] START prepareForShutdown() from=internal, task_id=21b12bbd-1d61-4217-b92d-641a53d5f7bb (api:48) 2021-11-12 07:09:30,317+0000 DEBUG (vmchannels) [vds] VM channels listener thread has ended. (vmchannels:214) 2021-11-12 07:09:30,317+0000 DEBUG (vmchannels) [root] FINISH thread <Thread(vmchannels, stopped daemon 140163095193344)> (concurrent:261) 2021-11-12 07:09:30,516+0000 DEBUG (mailbox-hsm/4) [root] FINISH thread <Thread(mailbox-hsm/4, stopped daemon 140162799089408)> (concurrent:261) 2021-11-12 07:09:30,517+0000 INFO (ioprocess/143197) [IOProcess] (3a729aa1-8e14-4ea0-8794-e3d67fbde542) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,521+0000 INFO (ioprocess/143199) [IOProcess] (ost-he-basic-suite-master-storage:_exports_nfs_share1) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,535+0000 INFO (ioprocess/143193) [IOProcess] (ost-he-basic-suite-master-storage:_exports_nfs_share2) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,679+0000 INFO (ioprocess/143195) [IOProcess] (0187cf2f-2344-48de-a2a0-dd007315399f) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,719+0000 INFO (ioprocess/143192) [IOProcess] (15fa3d6c-671b-46ef-af9a-00337011fa26) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,756+0000 INFO (ioprocess/143194) [IOProcess] (ost-he-basic-suite-master-storage:_exports_nfs_exported) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,768+0000 INFO (ioprocess/143198) [IOProcess] (ost-he-basic-suite-master-storage:_exports_nfs__he) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,774+0000 INFO (ioprocess/143196) [IOProcess] (a8bab4ef-2952-4c42-ba44-dbb3e1b8c87c) Starting ioprocess (__init__:465) 2021-11-12 07:09:30,957+0000 DEBUG (mailbox-hsm/2) [root] FINISH thread <Thread(mailbox-hsm/2, stopped daemon 140162815874816)> (concurrent:261) 2021-11-12 07:09:31,629+0000 INFO (mailbox-hsm) [storage.mailbox.hsmmailmonitor] HSM_MailboxMonitor - Incoming mail monitoring thread stopped, clearing outgoing mail (mailbox:500) 2021-11-12 07:09:31,629+0000 INFO (mailbox-hsm) [storage.mailbox.hsmmailmonitor] HSM_MailMonitor sending mail to SPM - ['/usr/bin/dd', 'of=/rhev/data-center/f54c6052-437f-11ec-9094-54527d140533/mastersd/dom_md/inbox', 'iflag=fullblock', 'oflag=direct', 'conv=notrunc', 'bs=4096', 'count=1', 'seek=2'] (mailbox:382) 2021-11-12 07:09:32,610+0000 DEBUG (mailbox-hsm/1) [root] FINISH thread <Thread(mailbox-hsm/1, stopped daemon 140162841052928)> (concurrent:261) 2021-11-12 07:09:32,792+0000 DEBUG (mailbox-hsm/3) [root] FINISH thread <Thread(mailbox-hsm/3, stopped daemon 140162807482112)> (concurrent:261) 2021-11-12 07:09:32,818+0000 DEBUG (mailbox-hsm/0) [root] FINISH thread <Thread(mailbox-hsm/0, stopped daemon 140162824267520)> (concurrent:261) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Shutting down domain monitors (monitor:243) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Stop monitoring 15fa3d6c-671b-46ef-af9a-00337011fa26 (shutdown=True) (monitor:268) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Stop monitoring a8bab4ef-2952-4c42-ba44-dbb3e1b8c87c (shutdown=True) (monitor:268) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Stop monitoring 3a729aa1-8e14-4ea0-8794-e3d67fbde542 (shutdown=True) (monitor:268) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Stop monitoring 0187cf2f-2344-48de-a2a0-dd007315399f (shutdown=True) (monitor:268) 2021-11-12 07:09:32,820+0000 INFO (MainThread) [storage.monitor] Stop monitoring 186180cb-5cc5-4aa4-868a-9e1ed7965ddf (shutdown=True) (monitor:268) 2021-11-12 07:09:32,831+0000 INFO (monitor/0187cf2) [storage.check] Stop checking '/rhev/data-center/mnt/ost-he-basic-suite-master-storage:_exports_nfs_exported/0187cf2f-2344-48de-a2a0-dd007315399f/dom_md/metadata' (check:135) 2021-11-12 07:09:32,838+0000 INFO (monitor/a8bab4e) [storage.check] Stop checking '/rhev/data-center/mnt/ost-he-basic-suite-master-storage:_exports_nfs_share1/a8bab4ef-2952-4c42-ba44-dbb3e1b8c87c/dom_md/metadata' (check:135) 2021-11-12 07:09:32,844+0000 INFO (monitor/15fa3d6) [storage.check] Stop checking '/rhev/data-center/mnt/ost-he-basic-suite-master-storage:_exports_nfs__he/15fa3d6c-671b-46ef-af9a-00337011fa26/dom_md/metadata' (check:135) 2021-11-12 07:09:32,864+0000 INFO (monitor/3a729aa) [storage.check] Stop checking '/rhev/data-center/mnt/ost-he-basic-suite-master-storage:_exports_nfs_share2/3a729aa1-8e14-4ea0-8794-e3d67fbde542/dom_md/metadata' (check:135) 2021-11-12 07:09:32,865+0000 INFO (monitor/186180c) [storage.check] Stop checking '/dev/186180cb-5cc5-4aa4-868a-9e1ed7965ddf/metadata' (check:135) 2021-11-12 07:09:32,867+0000 INFO (monitor/186180c) [storage.blocksd] Tearing down domain 186180cb-5cc5-4aa4-868a-9e1ed7965ddf (blockSD:996) 2021-11-12 07:09:32,867+0000 DEBUG (monitor/186180c) [common.commands] /usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm vgchange --config 'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405423a0b45cef54e6e9fd0c7df4$|^/dev/mapper/36001405e9302e3f55e74aedbf352b79f$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }' --available n 186180cb-5cc5-4aa4-868a-9e1ed7965ddf (cwd None) (commands:154) 2021-11-12 07:09:38,063+0000 DEBUG (monitor/186180c) [common.commands] FAILED: <err> = b' Logical volume 186180cb-5cc5-4aa4-868a-9e1ed7965ddf/ids in use.\n Can\'t deactivate volume group "186180cb-5cc5-4aa4-868a-9e1ed7965ddf" with 1 open logical volume(s)\n'; <rc> = 5 (commands:186) 2021-11-12 07:09:38,066+0000 WARN (monitor/186180c) [storage.lvm] Command with specific filter failed or returned no data, retrying with a wider filter: LVM command failed: 'cmd=[\'/sbin/lvm\', \'vgchange\', \'--config\', \'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405423a0b45cef54e6e9fd0c7df4$|^/dev/mapper/36001405e9302e3f55e74aedbf352b79f$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }\', \'--available\', \'n\', \'186180cb-5cc5-4aa4-868a-9e1ed7965ddf\'] rc=5 out=[] err=[\' Logical volume 186180cb-5cc5-4aa4-868a-9e1ed7965ddf/ids in use.\', \' Can\\\'t deactivate volume group "186180cb-5cc5-4aa4-868a-9e1ed7965ddf" with 1 open logical volume(s)\']' (lvm:532) 2021-11-12 07:09:38,067+0000 DEBUG (monitor/186180c) [common.commands] /usr/bin/taskset --cpu-list 0-1 /usr/bin/sudo -n /sbin/lvm vgchange --config 'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405423a0b45cef54e6e9fd0c7df4$|^/dev/mapper/36001405d40a7e761def4ed09aac63282$|^/dev/mapper/36001405e9302e3f55e74aedbf352b79f$|^/dev/mapper/36001405ece10ae48e99470295edda1bb$|^/dev/mapper/36001405f269e8e9efb34e5f9170b349b$|^/dev/mapper/36001405f8c5fe6c239e46a0976b842df$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }' --available n 186180cb-5cc5-4aa4-868a-9e1ed7965ddf (cwd None) (commands:154) What is interesting here is that ioprocess is started here rather than being killed as on clean vdsmd shutdowns. Any ideas? Thanks, Milan

3 5

Gerrit: ovirt-engine build is unstable
by Saif Abu Saleh 15 Nov '21

15 Nov '21

Hi, Gerrit build on ovirt-engine on master branch seems to be unstable I ran twice and it failed on two errors un-related to my changes, failures: 1- job link: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15074/ Errors: fatal: unable to access 'https://gerrit.ovirt.org/ovirt-engine/': Could not resolve host: gerrit.ovirt.org; Unknown error 2- job link: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/15080/ Errors: [2021-11-14T12:32:21.224Z] No matching package to install: 'ovirt-jboss-modules-maven-plugin >= 2.0.1' [2021-11-14T12:32:21.224Z] Error: Some packages could not be found. irt.oer: Anyone is aware of / checking these failures? Thanks, Saif

2 1

ovirt-ansible-collection on el9
by Sandro Bonazzola 12 Nov '21

12 Nov '21

Hi, repository closure on ovirt-ansible-collection reports broken dependency: package: ovirt-ansible-collection-1.7.0-0.1.master.20211108095017.el9.noarch from copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot unresolved deps: ansible >= 2.9.21 Do we need to provide ansible 2.9.z in CentOS Virt SIG for CentOS 9 Stream? If not, can you please fix the dependency on el9? 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.*

2 2

resources.ovirt.org migration
by Denis Volkov 11 Nov '21

11 Nov '21

Hello Server `resources.ovirt.org` hosting repositories for ovirt is going to be migrated to new hardware in a different datacenter within the next couple of hours. No service interruption is expected during the migration. I will follow-up when the process is complete -- Denis Volkov

1 1

oVirt SDK docs services.m.html cut in the middle
by Yedidyah Bar David 11 Nov '21

11 Nov '21

Hi all, I was searching for something in the SDK and noticed that [1] is cut in the middle. The last class that appears there is 'TemplateService'. If you scroll down on the left pane and press something below this one, such as [2], you see that the right pane does not scroll down - you are at (close to) its bottom. The last link that seems to be included is [3]. Known issue? Thanks, [1] https://ovirt.github.io/ovirt-engine-sdk/master/services.m.html [2] https://ovirt.github.io/ovirt-engine-sdk/master/services.m.html#TemplateCdr… [3] https://ovirt.github.io/ovirt-engine-sdk/master/services.m.html#TemplateSer… -- Didi

2 1

changes in dbscripts/common_sp.sql functions validation
by Eli Mesika 11 Nov '21

11 Nov '21

Hi All Patch [1] is about to be merged soon and it changes the behaviour of dbscripts/common_sp.sql functions validation. In dbscripts/common_sp.sql we have several helper functions that execute dynamic SQL using the EXECUTE command In order to validate parameters as table name , column name etc, we used to check those parameters with the information stored in the information_schema data Due to that we had some side effects: 1. fn_db_change_column_type did not accept valid types as DECIMAL since in the information_schema data in is named NUMERIC 2. fn_db_change_column_type did not accept precision in the origin column type as NUMERIC(24,4) for example 3. fn_db_change_column_type swallowed any error causing scripts not to perform the action but to consider as successful Patch [1] fixes all those issues and now the comon_sp.sql functions will trust errors thrown by using the EXECUTE command without validating the SQL syntax before. This will resolve issues 1 and 2 listed above In addition, the patch fixes issue 3 by adding the needed upgrade scripts to enforce the changes that were not performed in former upgrade scripts updates. Please feel free to contact me on any issues/questions regarding those changes Regards Eli Mesika [1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/117448/

1 0

C9S/x86_64 Bug 2021809 - gcc and python3 dependencies broken
by Sandro Bonazzola 10 Nov '21

10 Nov '21

Hi, just a heads up CentOS Stream 9 repo for x86_64 is broken. Reported *Bug 2021809* <https://bugzilla.redhat.com/show_bug.cgi?id=2021809> - gcc and python3 dependencies broken Both Jenkins and COPR are failing builds on x86_64 due to that. -- 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

ansible-runner in CentOS Virtualization SIG 4.5/el8s
by Sandro Bonazzola 10 Nov '21

10 Nov '21

Hi, in ovirt-4.5 repo we have ansible-runner-1.4.6-1.el8 <https://cbs.centos.org/koji/buildinfo?buildID=31901> which also provides python3-ansible-runner-1.4.6-1.el8. But we are also consuming openstack-yoga repos and they are shipping python-ansible-runner-1.4.6-3.el8 <https://cbs.centos.org/koji/buildinfo?buildID=30640> but there's no ansible-runner package there. This ends up with repository closure failure: package: ansible-runner-1.4.6-1.el8.noarch from ovirt-master-centos-stream-ovirt45-testing unresolved deps: python3-ansible-runner = 1.4.6-1.el8 Do we need to maintain ansible-runner packaging in CentOS Virt SIG? Should we rebuild ansible-runner with higher NVR? +Martin Necas <mnecas(a)redhat.com> can you please look into this? 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 1

ovirt-engine has been tagged (ovirt-engine-4.4.9.5)
by Sandro Bonazzola 09 Nov '21

09 Nov '21

ovirt-engine has been tagged (ovirt-engine-4.4.9.5) -- 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

Gerrit host SSH key changed
by Tomáš Golembiovský 09 Nov '21

09 Nov '21

Hi, it seems there was a change to host SSH keys on gerrit.ovirt.org. Can annyone comment on when and why that has happened? What is the new host key? Thanks, Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 1

Publishing oVirt Go modules under ovirt.org namespace
by Nir Soffer 06 Nov '21

06 Nov '21

Currently we have 3 go modules: - github.com/ovirt/go-ovirt https://github.com/oVirt/go-ovirt/ seems that this repo generated by https://github.com/oVirt/ovirt-engine-sdk-go - github.com/ovirt/go-ovirt-client https://github.com/oVirt/go-ovirt-client - github.com/ovirt/go-ovirt-client-log https://github.com/oVirt/go-ovirt-client-log These modules share the issue of depending on the hosting service and the repo the code is located. I started to work on the imageio go module here: https://gerrit.ovirt.org/c/ovirt-imageio/+/117277 And I'm trying to avoid the issues above by naming the module: ovirt.org/imageio The module name does not depend on the hosting service, or on the actual repo or the location in the repo. To make this work, the web server at ovirt.org should serve this resource: https://ovirt.org/imageio returning an HTML document that contains a magic <meta> tag in the page header <meta name="go-import" content="ovirt.org/imageio git https://github.com/ovirt/ovirt-imageio/imageio-go"/> Is this possible with our current infrastructure? Should we rename all the go modules to fit this scheme? Nir

2 4

Is https://ovirt-jira.atlassian.net/ still used?
by Sandro Bonazzola 03 Nov '21

03 Nov '21

Hi, quick question, is someone still monitoring https://ovirt-jira.atlassian.net/ ? 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 1

ost-images is not mirrored to github
by Sandro Bonazzola 02 Nov '21

02 Nov '21

Hi, looks like ost-images is not mirrored to github.com/oVirt. Infra team: can you please fix this? 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

ovirt-engine-nodejs-modules is not mirrored to github
by Sandro Bonazzola 02 Nov '21

02 Nov '21

Hi, looks like ovirt-engine-nodejs-modules is not mirrored to github.com/oVirt. Infra team: can you please fix this? 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