December 2019 - 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

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

Container-based CI backend is now available for use
by Barak Korren 26 Mar '20

26 Mar '20

A little less then a month ago I sent an email to this list telling you all about ongoing work to create a new container-based backend for the oVirt CI system. I'm pleased to announce that we have managed to finally merged an initial set of patches implementing that backend yesterday, and it is now available for general use. *What? Were? How do I use it?* Documentation about how to use the new backend is now available in read the docs <https://ovirt-infra-docs.readthedocs.io/en/latest/CI/STDCI-Containers/index…> . *Wait! I needed it to do X which it doesn't!* For the time being the new backend lacks some features that some may consider to be essential, such as automated cloning of patch source code and build artifact collection. We already have implemented patches providing a substantial amount of additional functionality, and hopefully we will be able to merge them soon. Following is a list of those patches and the features they implement: 1. Automated source cloning support: - 104213 <https://gerrit.ovirt.org/104213>: Implement STDCI DSL support for initContainers - 104590 <https://gerrit.ovirt.org/104590>: STDCI DSL: Add the `decorate` option - 104668 <https://gerrit.ovirt.org/104668>: Document source cloning extension for containers 2. Artifact collection support - 104690 <https://gerrit.ovirt.org/104690>: Added NFS server container image - 104273 <https://gerrit.ovirt.org/104273>: STDCI PODS: Unique UID for each job build's POD - 104756 <https://gerrit.ovirt.org/104756>: pipeline-loader: refactor: separate podspec func - 104757 <https://gerrit.ovirt.org/104757>: pipeline-loader: refactor: Use podspec struct def - 104766 <https://gerrit.ovirt.org/104766>: STDCI PODs: Add artifact collection logic - 105522 <https://gerrit.ovirt.org/105522>: Documented artifact collection in containers 3. Extended log collection - 104842 <https://gerrit.ovirt.org/104842>: STDCI PODs: Add POD log collection - 105523 <https://gerrit.ovirt.org/105523>: Documented log collection in containers 4. Privileged container support - 104786 <https://gerrit.ovirt.org/104786>: STDCI DSL: Enable privileged containers 5. Support for using containers in gating jobs: - 104804 <https://gerrit.ovirt.org/104804>: standard-stage: refactor: move DSL to a library - 104811 <https://gerrit.ovirt.org/104811>: gate: Support getting suits from STDCI DSL 6. Providing the `extra_sources` file to OST suit containers: - 104843 <https://gerrit.ovirt.org/104843>: stdci_runner: Create extra_sources for PODs 7. Support for mirror injection and upstream source cloning - 104917 <https://gerrit.ovirt.org/104917>: Added a container with STDCI tools - 104918 <https://gerrit.ovirt.org/104918>: decorate.py: Add script - 104989 <https://gerrit.ovirt.org/104989>: STDCI DSL: Use `tools` container for `decorate` - 104994 <https://gerrit.ovirt.org/104994>: stdci_runner: Inject mirrors in PODs As you can see, we have quite a big pile of reviews to do, as always, help is very welcome... Regards, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 4

Create VM snapshot with no disk
by scott.fitzgerald＠oracle.com 13 Feb '20

13 Feb '20

Hi, A VM Snapshot can be made using SnapshotBuilder builder = new SnapshotBuilder().vm(VM).name("Snap1").description("Test"); sysService.vmsService().vmService(VM.id()).snapshotsService().add().snapshot(builder).send(); It can be made with no memory by using a builder with persistMemorystate(false) How can one be made with no disk? .diskAttachments(emptyList) isnt working. TIA

3 5

vdsmd memory leak
by Chris Adams 04 Feb '20

04 Feb '20

I've seen vdsmd leak memory (RSS increasing) for a while (brought it up on the lists and opened a BZ ticket), and never gotten anywhere with diagnosing or resolving it. I reinstalled my dev setup Friday with up-to-date CentOS 7 (minimal install) and oVirt 4.3, with a hosted engine on iSCSI (multipath if it matters). In just 3 days, vdsmd on the host with the engine has gone up to an RSS of 481 MB. It just continues to steadily increase. Watching with a script, I see (this is VmRSS from /proc/$(pidof -x vdsmd)/status): 12:26:32.892 482076 +20 12:26:35.300 482096 +20 12:26:38.927 482112 +16 12:26:40.034 482128 +16 12:26:47.534 482132 +4 12:26:48.887 482144 +12 12:26:49.133 482156 +12 12:26:50.955 482172 +16 12:26:53.062 482176 +4 12:26:53.092 482204 +28 12:26:59.065 482212 +8 12:26:59.075 482228 +16 12:26:59.361 482244 +16 12:27:03.131 482252 +8 12:27:07.370 482256 +4 12:27:10.091 482272 +16 12:27:13.205 482296 +24 12:27:18.770 482308 +12 12:27:20.437 482332 +24 12:27:23.313 482340 +8 12:27:23.324 482364 +24 12:27:26.667 482372 +8 12:27:26.687 482376 +4 12:27:28.873 482388 +12 12:27:28.883 482392 +4 12:27:28.976 482396 +4 12:27:29.190 482408 +12 That's an increase of 352 kB in a minute. There's got to be some way to diagnose this, but I don't know python well enough. -- Chris Adams <cma(a)cmadams.net>

4 6

Failed to add host using ansible runner
by Eyal Shenitzky 09 Jan '20

09 Jan '20

Hi, I am failing to add a new host to my env with the following message: 2019-12-25 10:57:17,587+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-63) [41ec72c1-88e2-402b-8bb9-f38c678d0bf0] EVENT_ID: VDS_INSTALL_FAILED(505), Host 10.35.0.158 installation failed. Failed to execute Ansible host-deploy role: null. Please check logs for more details: /home/engine/ovirt-engine/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20191225105714-10.35.0.158-41ec72c1-88e2-402b-8bb9-f38c678d0bf0.log. The host is Fedora-30 Ansible version is - 2.9.1 Ansible runner version - 1.3.4 /etc/ansible-runner-service/config.yaml: --- version: 1 target_user: root playbooks_root_dir: '/home/engine/ovirt-engine/share/ovirt-engine/ansible-runner-service-project' ssh_private_key: '/home/engine/ovirt-engine/etc/pki/ovirt-engine/keys/engine_id_rsa' port: 50001 target_user: root There are no logs at all at the specified location in the error message. Did someone encounter that issue? Thanks, -- Regards, Eyal Shenitzky

6 13

New dependency for development environment
by Ondra Machacek 09 Jan '20

09 Jan '20

Hello, we are going to merge a series of patches to master branch, which integrates ansible-runner with oVirt engine. When the patches will be merged you will need to install new package called ansible-runner- service-dev, and follow instructions so your dev-env will keep working smoothly(all relevant info will be also in README.adoc): 1) sudo dnf update ovirt-release-master 2) sudo dnf install -y ansible-runner-service-dev 3) Edit `/etc/ansible-runner-service/config.yaml` file as follows: --- playbooks_root_dir: '$PREFIX/share/ovirt-engine/ansible-runner-service-project' ssh_private_key: '$PREFIX/etc/pki/ovirt-engine/keys/engine_id_rsa' port: 50001 target_user: root Where `$PREFIX` is the prefix of your development environment prefix, which you've specified during the compilation of the engine. 4) Restart and enable ansible-runner-service: # systemctl restart ansible-runner-service # systemctl enable ansible-runner-service That's it, your dev-env should start using the ansible-runner-service for host-deployment etc. Please note that only Fedora 30/31 and Centos7 was packaged, and are natively supported! Thanks, Ondra

9 24

Tracking ovirt integration with gluster 7
by Strahil 30 Dec '19

30 Dec '19

Hello Dev List, Is there a bugzilla entry for tracking the progress of oVirt integration with Gluster v7 ? I have met some issues that I would be happy to share . Currently , I'm running oVirt 4.3 with Gluster 7.0 . Best Regards, Strahil Nikolov

1 0

Re: [ovirt-users] [ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by Strahil 25 Dec '19

25 Dec '19

Hi, If the VMs are starting properly and they don't use cloudinit - then the issue is not oVirt specific, but guest specific (Linux/Windows depending on guest OS). So your should check: 1. Does your host have any Netwprks out of sync (Host's network tab) If yes - put the server into maintenance and fix the issue (host's network tab) 2. Check each VM's configuration if it is defined to use CloudInit -> if yes, verify that cloudinit's service is running on the guest 3. Verify each problematic guest's network settings. If needed, set a static IP and try to ping another IP from the same subnet/Vlan . Best Regards, Strahil NikolovOn Dec 25, 2019 11:41, lifuqiong(a)sunyainfo.com wrote: >> >> >>> Dear All: >>> My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. >>> One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) >>> >>> the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 >>> by ovirt rest api. But the ip was changed to templated ip when the accident happened. >>> >>> the vm's os is centos. >>> >>> Hope get help from you soon, Thank you. >>> >>> Mark >>> Sincerely.

1 0

[ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by lifuqiong＠sunyainfo.com 25 Dec '19

25 Dec '19

Dear All: My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 by ovirt rest api. But the ip was changed to templated ip when the accident happened. the vm's os is centos. Hope get help from you soon, Thank you. Mark Sincerely.

1 0

[Ovirt UI GWT ], issue with "EntityModelCheckBoxEditor"
by Prajith Kesava Prasad 24 Dec '19

24 Dec '19

Hi, During the implementation of a checkbox editor in ovirt-engine code, im facing an issue, the checkbox is shown in the ui fine by adding the appropriate popup view and its corresponding java file, i have also set the getter and setter method in the equivalent model class as well, now, im unable to get the value change in the checkbox no matter what, i tried al the possible ways , i tried looking at how other checkbox editor is implemented, but no luck. No matter whether the checkbox is marked or not marked its set as Fasle, could someone help me with this? Thanks& Regards, Prajith

2 1

[ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by lifuqiong＠sunyainfo.com 23 Dec '19

23 Dec '19

Dear All: My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 by ovirt rest api. But the ip was changed to templated ip when the accident happened. the vm's os is centos. Hope get help from you soon, Thank you. Mark Sincerely.

1 0

[ovirt 4.2]vdsm host was shutdown unexpectly, configure of some vms was changed or lost when host was re-powered on and vm was started
by lifuqiong＠sunyainfo.com 23 Dec '19

23 Dec '19

Dear All: My ovirt engine managed two vdsms with nfs storage on another nfs server, it worked fine about three months. One of host (host_1.3; ip:172.18.1.3) was created about 16 vms, but the host_1.3 was shutdown unexpectly about 2019-12-23 16:11, when re-started host and vms; half of the vms was lost some configure or changed , such as lost theirs ip etc.(the vm name is 'zzh_Chain49_ACG_M' in the vdsm.log) the vm zzh_Chain49_ACG_M was create by rest API through vm's templated . the template is 20.1.1.161; the vm zzh_Chain49_ACG_M was created by ovirt rest api and changed the ip to 20.1.1.219 by ovirt rest api. But the ip was changed to templated ip when the accident happened. the vm's os is centos. Hope get help from you soon, Thank you. Mark Sincerely.

1 0

Re: [CQ]: 105811,4 (ovirt-engine) failed "ovirt-master" system tests
by Yedidyah Bar David 22 Dec '19

22 Dec '19

On Thu, Dec 19, 2019 at 3:07 AM oVirt Jenkins <jenkins(a)ovirt.org> wrote: > > Change 105811,4 (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/105811/4 > > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17803/ lago log [1] has: 2019-12-19 01:03:18,289::ssh.py::ssh::58::lago.ssh::DEBUG::Running 57dde5d6 on lago-basic-suite-master-engine: /usr/bin/systemctl stop ovirt-engine 2019-12-19 01:03:20,379::ssh.py::ssh::81::lago.ssh::DEBUG::Command 57dde5d6 on lago-basic-suite-master-engine returned with 0 2019-12-19 01:03:20,381::log_utils.py::__enter__::600::lago.ssh::DEBUG::start task:b30be6a0-81f5-4611-b638-2cc46f8dd28f:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:03:20,512::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:b30be6a0-81f5-4611-b638-2cc46f8dd28f:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:03:20,777::ssh.py::ssh::58::lago.ssh::DEBUG::Running 5959a5f8 on lago-basic-suite-master-engine: /usr/bin/systemctl status --lines=0 ovirt-engine 2019-12-19 01:03:20,828::ssh.py::ssh::81::lago.ssh::DEBUG::Command 5959a5f8 on lago-basic-suite-master-engine returned with 3 2019-12-19 01:03:20,828::ssh.py::ssh::89::lago.ssh::DEBUG::Command 5959a5f8 on lago-basic-suite-master-engine output: â— ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: inactive (dead) since Wed 2019-12-18 20:03:20 EST; 455ms ago Process: 24166 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=0/SUCCESS) Main PID: 24166 (code=exited, status=0/SUCCESS) 2019-12-19 01:03:20,829::log_utils.py::__enter__::600::lago.ssh::DEBUG::start task:6b4dab7c-64f3-43e5-ae85-2fe6246d9376:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:03:20,998::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:6b4dab7c-64f3-43e5-ae85-2fe6246d9376:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:03:21,214::ssh.py::ssh::58::lago.ssh::DEBUG::Running 599c5b96 on lago-basic-suite-master-engine: /usr/bin/systemctl start ovirt-engine 2019-12-19 01:04:13,735::ssh.py::ssh::81::lago.ssh::DEBUG::Command 599c5b96 on lago-basic-suite-master-engine returned with 0 2019-12-19 01:04:13,737::log_utils.py::__enter__::600::lago.ssh::DEBUG::start task:5b775d53-c53c-4d15-9cae-2806c44079b7:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:04:13,971::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:5b775d53-c53c-4d15-9cae-2806c44079b7:Get ssh client for lago-basic-suite-master-engine: 2019-12-19 01:04:14,488::ssh.py::ssh::58::lago.ssh::DEBUG::Running 795d5098 on lago-basic-suite-master-engine: /usr/bin/systemctl status --lines=0 ovirt-engine 2019-12-19 01:04:15,039::ssh.py::ssh::81::lago.ssh::DEBUG::Command 795d5098 on lago-basic-suite-master-engine returned with 0 2019-12-19 01:04:15,040::ssh.py::ssh::89::lago.ssh::DEBUG::Command 795d5098 on lago-basic-suite-master-engine output: â— ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-12-18 20:04:13 EST; 1s ago Main PID: 5718 (ovirt-engine.py) CGroup: /system.slice/ovirt-engine.service â”œâ”€5718 /usr/bin/python2 /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start â””â”€6073 ovirt-engine --add-modules java.se -server -XX:+TieredCompilation -Xms1024M -Xmx1024M -Xss1M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djsse.enableSNIExtension=false -Dresteasy.preferJacksonOverJsonB=true -Djackson.deserialization.whitelist.packages=org,com,java,javax -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/ovirt-engine-wildfly -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config -Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -jar /usr/share/ovirt-engine-wildfly/jboss-modules.jar -mp /usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-extension-aaa-ldap/modules:/usr/share/ovirt-engine-wildfly/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml 2019-12-19 01:04:15,040::log_utils.py::end_log_task::670::nose::INFO:: # add_ldap_provider: [32mSuccess [0m (in 0:01:08) 2019-12-19 01:05:12,552::log_utils.py::start_log_task::655::nose::INFO:: # Failure: RuntimeError (test api call failed): [0m [0m So probably the engine didn't manage to start yet and connecting to its api failed [2]. Perhaps wait, after starting it, until it's really up (checking the api or health)? [1] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17803/artifa… [2] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17803/testRe… > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/P3BLXLG63LC7P… -- Didi

2 2

vdsm [check-patch] failures - error with nmstate repo
by Liran Rotenberg 19 Dec '19

19 Dec '19

Hi, VDSM check patch keep failing, Console output taken from[2]: *15:33:30* failure: repodata/repomd.xml from nmstate: [Errno 256] No more mirrors to try.*15:33:30* https://copr-be.cloud.fedoraproject.org/results/nmstate/nmstate-git-fedora/…: [Errno 14] HTTPS Error 404 - Not Found *15:33:33* ERROR: Command failed: *15:33:33* # /usr/bin/dnf --installroot /var/lib/mock/fedora-30-x86_64-b4b1fa43be798f48f41c1f0af664447e-6272/root/ --releasever 30 --setopt=deltarpm=False --allowerasing --disableplugin=local --disableplugin=spacewalk install @buildsys-build autoconf automake createrepo dnf dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils libguestfs-tools-c lshw make mom openvswitch ovirt-imageio-common python3-augeas python3-blivet python3-coverage python3-dateutil python3-dbus python3-decorator python3-devel python3-dmidecode python3-inotify python3-ioprocess-1.3.0 python3-libselinux python3-libvirt python3-magic python3-netaddr python3-nose python3-pip python3-policycoreutils python3-pyudev python3-pyyaml python3-requests python3-sanlock python3-six python3-yaml rpm-build rpmlint sudo xfsprogs --setopt=tsflags=nocontexts*15:33:33* No matches found for the following disable plugin patterns: local, spacewalk*15:33:33* Custom fc30-updates-debuginfo 1.8 MB/s | 13 MB 00:07 *15:33:33* Custom tested 16 MB/s | 570 kB 00:00 *15:33:33* Custom vdo 61 kB/s | 8.1 kB 00:00 *15:33:33* Custom virt-preview 770 kB/s | 139 kB 00:00 *15:33:33* Custom nmstate 4.7 kB/s | 341 B 00:00 *15:33:33* Error: Failed to download metadata for repo 'nmstate': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/16055/ [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/16058/

2 2

Package does not exist and cannot find symbol even though they exist
by Prajith Kesava Prasad 18 Dec '19

18 Dec '19

Hi, During make install build of ovirt , sometimes i get compilation errors for eg:- Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project uicommonweb: Compilation failure: Compilation failure: [ERROR] /home/vagrant/workspace/ovirt-engine/frontend/webadmin/modules/uicommonweb/src/main/java/org/ovirt/engine/ui/uicommonweb/models/hosts/HostListModel.java:[19,41] package org.ovirt.engine.core.bll.gluster does not exist But they do exists and, usually they go away after a couple of make clean installs, but this time its not going also i was curious if anyone managed to find the root cause for such issues? Thanks in advance, Prajith

1 0

Flaky jsonrpc test? looks like timeout
by Nir Soffer 18 Dec '19

18 Dec '19

I had this failure today, that looks like a timeout, based on the test duration: 18.16s call tests/lib/yajsonrpc/jsonrpcserver_test.py::JsonRpcServerTests::testMethodBadParameters(True) Looking at the log it smells like the known race when connecting to server. Also we see: - ERROR vds.dispatcher:betterAsyncore.py:179 uncaptured python exception, closing channel Should never happen, means we did not handle exceptions in some handler. - WARNING vds.dispatcher:betterAsyncore.py:179 unhandled write event Should not happen, means that we did not implement handle_write() in some dispatcher. See logs below. Nir --- Build log: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/15978//artifact/che… Error: =================================== FAILURES =================================== _______________ JsonRpcServerTests.testMethodBadParameters(True) _______________ self = <jsonrpcserver_test.JsonRpcServerTests testMethod=testMethodBadParameters(True)> use_ssl = True @permutations(USE_SSL) def testMethodBadParameters(self, use_ssl): # Without a schema the server returns an internal error ssl_ctx = self.ssl_ctx if use_ssl else None bridge = _DummyBridge() with constructClient(self.log, bridge, ssl_ctx) as clientFactory: with self._client(clientFactory) as client: with self.assertRaises(JsonRpcErrorBase) as cm: self._callTimeout(client, "echo", [], CALL_ID) self.assertEqual(cm.exception.code, > JsonRpcInternalError().code) E AssertionError: -32605 != -32603 lib/yajsonrpc/jsonrpcserver_test.py:209: AssertionError ------------------------------ Captured log call ------------------------------- WARNING vds.dispatcher:betterAsyncore.py:179 unhandled write event ERROR vds.dispatcher:betterAsyncore.py:179 uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher ('::1', 40156, 0, 0) at 0x7f842cd7d7f0> (<class 'ValueError'>:'b'ept-version:1.2'' contains illegal character ':' [/usr/lib64/python3.6/asyncore.py|readwrite|108] [/usr/lib64/python3.6/asyncore.py|handle_read_event|423] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|71] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|168] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/protocoldetector.py|handle_read|129] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|handle_socket|413] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|add_socket|54] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|createListener|379] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|StompListener|345] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|__init__|47] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|switch_implementation|86] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stompserver.py|init|363] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/rpc/bindingjsonrpc.py|_onAccept|57] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|set_message_handler|645] [/usr/lib64/python3.6/asyncore.py|handle_read_event|423] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|handle_read|71] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/betterAsyncore.py|_delegate_call|168] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|handle_read|421] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|parse|323] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|_parse_command|245] [/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/yajsonrpc/stomp.py|decode_value|167]) WARNING vds.dispatcher:betterAsyncore.py:179 unhandled close event =============================== warnings summary =============================== /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334: PytestUnknownMarkWarning: Unknown pytest.mark.stress - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html PytestUnknownMarkWarning, /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334: PytestUnknownMarkWarning: Unknown pytest.mark.slow - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html PytestUnknownMarkWarning, /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/models.py:442 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/models.py:442: DeprecationWarning: invalid escape sequence \D nicsRexp = re.compile("^(\D*)(\d*)(.*)$") /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/link/validator.py:38 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/link/validator.py:38: DeprecationWarning: invalid escape sequence \w bond for bond in bonds if not re.match('^bond\w+$', bond) /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/link/validator.py:44 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/link/validator.py:44: DeprecationWarning: invalid escape sequence \w and not re.match('^bond\w+$', net_attrs['bonding']) /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/v2v.py:78 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/v2v.py:78: DeprecationWarning: invalid escape sequence \d _SSH_AUTH_RE = b'(SSH_AUTH_SOCK)=([^;]+).*;\nSSH_AGENT_PID=(\d+)' /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/v2v.py:1420 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/v2v.py:1420: DeprecationWarning: invalid escape sequence \^ '(?P<m2_base>[0-9]+){sp}\^{sp}(?P<m2_exp>{exp}))'.format( /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334 /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/lib/lib/python3.6/site-packages/_pytest/mark/structures.py:334: PytestUnknownMarkWarning: Unknown pytest.mark.xpass - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html PytestUnknownMarkWarning, -- Docs: https://docs.pytest.org/en/latest/warnings.html ----------- coverage: platform linux, python 3.6.8-final-0 ----------- Coverage HTML written to dir htmlcov-lib ========================== slowest 10 test durations =========================== 18.16s call tests/lib/yajsonrpc/jsonrpcserver_test.py::JsonRpcServerTests::testMethodBadParameters(True) 2.92s call tests/lib/protocoldetector_test.py::AcceptorTests::test_reject_very_slow_client_concurrency(False) 2.86s call tests/lib/protocoldetector_test.py::AcceptorTests::test_reject_very_slow_client(True) 2.76s call tests/lib/protocoldetector_test.py::AcceptorTests::test_reject_very_slow_client_concurrency(True) 2.63s call tests/lib/protocoldetector_test.py::AcceptorTests::test_reject_very_slow_client(False) 1.28s call tests/pywatch_test.py::TestPyWatch::test_timeout_backtrace 0.89s call tests/pywatch_test.py::TestPyWatch::test_kill_grandkids 0.89s call tests/lib/protocoldetector_test.py::AcceptorTests::test_detect_slow_client_concurrency(True) 0.88s call tests/pywatch_test.py::TestPyWatch::test_timeout_output 0.80s call tests/lib/protocoldetector_test.py::AcceptorTests::test_detect_slow_client(False) =========================== short test summary info ============================

2 2

Bug 1779527 - Hosted engine deploys failed as "Failed to connect to guest agent channel" when creating target vm.
by Sandro Bonazzola 18 Dec '19

18 Dec '19

Hi, QE found *Bug 1779527* <https://bugzilla.redhat.com/show_bug.cgi?id=1779527> - Hosted engine deploys failed as "Failed to connect to guest agent channel" when creating target vm. while testing hosted engine deployment on the downstream version of oVirt Node 4.4. At first look, seems like vdsm is searching for guest agent. If this is the ovirt-guest-agent, we are not adding it anymore to the engine appliance as per virt team request. Can you provide hints on why this test is done on vdsm side and if we can get rid of it or if we need to re-add the ovirt-guest-agent to the appliance? 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

CI system outage
by Evgheni Dereveanchin 17 Dec '19

17 Dec '19

Hello everyone, We received several reports of Jenkins jobs not running properly. The reason turned out to be the Jenkins Master which did not start jobs properly. It has been restarted and is working properly now. If you have any jobs that failed or did not start at all today - please re-trigger them or reach out to me for assistance. -- Regards, Evgheni Dereveanchin

1 0

published master engine is 13 days old
by Yedidyah Bar David 17 Dec '19

17 Dec '19

Hi all, $subject. [1] has ovirt-engine-4.4.0-0.0.master.20191204120550.git04d5d05.el7.noarch . Tried to look around, and I have a few notes/questions: 1. Last successful run of [2] is 3 days old, but apparently it wasn't published. Any idea why? 2. Failed runs of [2] are reported to infra, with emails such as: [CQ]: 105472, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause Is anyone monitoring these? Is this the only alerting that CI generates on such failures? If first is No and second is Yes, then we need someone/something to start monitoring. This was discussed a lot, but I do not see any change. Ideally, such alerts should be To'ed or Cc'ed to the author and reviewers of the patch that CI found to be guilty (which might be wrong, that's not the point). Do we plan to have something like this? Any idea when it will be ready? 3. I looked at a few recent failures of [2], specifically [3][4]. Both seem to have been killed after a timeout, while running 'engine-config'. For [3] that's clear, see [5]: 2019-12-16 17:11:44,766::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:fb6611dc-55bb-4251-aeda-2578b2ec83a2:Get ssh client for lago-basic-suite-master-engine: 2019-12-16 17:11:44,931::ssh.py::ssh::58::lago.ssh::DEBUG::Running 22e2b6b6 on lago-basic-suite-master-engine: engine-config --set VdsmUseNmstate=true 2019-12-16 19:55:21,965::cmd.py::exit_handler::921::cli::DEBUG::signal 15 was caught Can't find stdout/stderr of engine-config, so it's hard to tell if it outputted anything helpful to understand why it was stuck. It's hard to tell that about [4], because it has very few artifacts collected, no idea why, notably no lago.log, but [6] does show: [36m # initialize_engine: [32mSuccess [0m (in 0:04:00) [0m [36m # engine_config: [0m [0m [0m [36m * Collect artifacts: [0m [0m [0m [36m - [Thread-34] lago-basic-suite-master-engine: [31mERROR [0m (in 0:00:04) [0m [36m * Collect artifacts: [31mERROR [0m (in 0:00:04) [0m [36m # engine_config: [31mERROR [0m (in 2:42:57) [0m /bin/bash: line 31: 5225 Killed ${_STDCI_TIMEOUT_CMD} "3h" "$script_path" < /dev/null If I run 'engine-config --set VdsmUseNmstate=true' on my 20191204120550.git04d5d05 engine, it returns quickly. Tried also adding a repo pointing at last successful run of [7], which is currently [8], and it prompts me to input a version, probably as a result of [9]. Ales/Martin, can you please have a look? Thanks. [1] https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ [2] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/ [3] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17768/ [4] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17761/ [5] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17768/artifa… [6] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17761/artifa… [7] https://jenkins.ovirt.org/job/ovirt-engine_standard-on-merge/ [8] https://jenkins.ovirt.org/job/ovirt-engine_standard-on-merge/384/ [9] https://gerrit.ovirt.org/105440 -- Didi

3 3

Failed to start Vagrant
by Ritesh Chikatwar 16 Dec '19

16 Dec '19

Hello, [root@localhost vagrant]# vagrant reload Error while connecting to libvirt: Error making a connection to libvirt URI qemu:///system?no_verify=1&keyfile=/root/.ssh/id_rsa: Call to virConnectOpen failed: authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found) Status Of libvirtd https://pastebin.com/H7yNqXU7 (It is active) I cannot see any logs in /var/log/libvirt/qemu/vagrant_default.log My Vagrant file: https://pastebin.com/JXBd5ci1 Any help would be appreciated. Ritesh CHikatwar

1 0

oVirt 4.4.0 Alpha release is now available for testing
by Sandro Bonazzola 13 Dec '19

13 Dec '19

oVirt 4.4.0 Alpha release is now available for testing The oVirt Project is excited to announce the availability of the alpha release of oVirt 4.4.0 for testing, as of December 13th, 2019 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is an Alpha release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production, and it is not feature complete. In particular, please note that upgrades from 4.3 and future upgrades from this alpha to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Alpha require content that will be available in CentOS Linux 8.1 which is currently being built from Red Hat Enterprise Linux 8.1. If you want to have a better experience you can test oVirt 4.4.0 Alpha on Red Hat Enterprise Linux 8.1. Known Issues - After installation open the Default cluster and hit “Save”, for any other new Cluster using CPU autodetection the dialog needs to be explicitly saved after the detection happens, after first host is added. (bug https://bugzilla.redhat.com/1770697) - Migrate, Cluster Upgrade, Export VM buttons cannot be clicked. Fixed in ovirt-engine-ui-extensions-1.0.11 Installation instructions For the engine: either use appliance or: - Install CentOS Linux 7.7 minimal from http://centos.mirror.garr.it/centos/7.7.1908/isos/x86_64/CentOS-7-x86_64-Mi… - yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - yum update (reboot if needed) - yum install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.0 from http://centos.mirror.garr.it/centos/8.0.1905/isos/x86_64/CentOS-8-x86_64-19… ; select minimal installation - yum config-manager --set-enabled PowerTools - yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - yum update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Alpha? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8.0) * CentOS Linux (or similar) 7.7 or later (but < 8.0) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.0 or later * CentOS Linux (or similar) 8.0 or later * oVirt Node 4.4 based on CentOS Linux 8.0 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 2

CI: jsonrpcserver test fails
by Amit Bawer 11 Dec '19

11 Dec '19

Hi devel, We have (also) frequent connectivity/timeout failures on CI tests for jsonrpcserver tests. Example: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/15642//artifact/che… Proposing the following patches: https://gerrit.ovirt.org/#/c/105518/ https://gerrit.ovirt.org/#/c/105519/ You are most welcome to review or suggest alternative ones. Thanks.

2 3