January 2020 - Devel - oVirt List Archives

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

11 Jan '24

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

3 5

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

14 Aug '23

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

7 10

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

21 Jun '21

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

6 11

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

Why is vdsm enabled by default?
by Yedidyah Bar David 02 Apr '20

02 Apr '20

If I do e.g.: 1. Install CentOS 2. yum install ovirt-releaseSOMETHING 3. yum install vdsm Then reboot the machine, vdsm starts, and for this, it does all kinds of things to the system (such as configure various services using vdsm-tool etc.). Are we sure we want/need this? Why would we want vdsm configured/running at all at this stage, before being added to an engine? In particular, if (especially during development) we have a bug in this configuration process, and then fix it, it might not be enough to upgrade vdsm - the tooling will then also have to fix the changes done by the buggy previous version, or require a full machine reinstall. Thanks and best regards, -- Didi

7 13

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

Ovirt System Tests "invalid syntax" for yaml import
by raymond.francis＠oracle.com 03 Feb '20

03 Feb '20

Seeing this when i run setup of System Tests for ovirt. Is there something in setup im missing 2020-01-31 10:20:53,167 021036:117 INFO: cd ovirt-system-tests && ./run_suite.sh basic-suite-4.3 + source common/helpers/logger.sh + CLI=lago + DO_CLEANUP=false + RECOMMENDED_RAM_IN_MB=8196 + EXTRA_SOURCES=() + RPMS_TO_INSTALL=() + COVERAGE=false ++ getopt -o ho:e:n:b:cs:r:l:i --long help,output:,engine:,node:,boot-iso:,cleanup,images --long extra-rpm-source,reposync-config:,local-rpms: --long only-verify-requirements,ignore-requirements --long coverage -n run_suite.sh -- basic-suite-4.3 + options=' -- '\''basic-suite-4.3'\''' + [[ 0 != \0 ]] + eval set -- ' -- '\''basic-suite-4.3'\''' ++ set -- -- basic-suite-4.3 + true + case $1 in + shift + break + [[ -z basic-suite-4.3 ]] + export OST_REPO_ROOT=/ovirt-system-tests + OST_REPO_ROOT=/ovirt-system-tests ++ realpath --no-symlinks basic-suite-4.3 + export SUITE=/ovirt-system-tests/basic-suite-4.3 + SUITE=/ovirt-system-tests/basic-suite-4.3 + [[ -z '' ]] + PREFIX=/ovirt-system-tests/deployment-basic-suite-4.3 + export PREFIX + false + [[ -e /ovirt-system-tests/deployment-basic-suite-4.3 ]] + mkdir -p /ovirt-system-tests/deployment-basic-suite-4.3 + [[ -n '' ]] + verify_system_requirements /ovirt-system-tests/deployment-basic-suite-4.3 + local prefix=/ovirt-system-tests/deployment-basic-suite-4.3 + /ovirt-system-tests/common/scripts/verify_system_requirements.py --prefix-path /ovirt-system-tests/deployment-basic-suite-4.3 /ovirt-system-tests/basic-suite-4.3/vars/main.yml Traceback (most recent call last): File "/ovirt-system-tests/common/scripts/verify_system_requirements.py", line 17, in <module> import yaml File "/usr/local/lib64/python3.6/site-packages/yaml/__init__.py", line 399 class YAMLObject(metaclass=YAMLObjectMetaclass): ^ SyntaxError: invalid syntax

2 1

FOSDEM 2020 - AMENDMENT In Memory of our Friend, Lars Kurth
by Doron Fediuck 31 Jan '20

31 Jan '20

Hi all, For those of you who are unaware of this, Lars Kurth from the Xen project has passed away [1]. Lars was one of the people who truly practiced open source and worked with the oVirt project on running FOSDEM's Virtualization and IaaS room in the past years. In Lars' memory there will be a special session [2] on Sunday morning, which will be broadcasted live. You're all welcomed to join physically or via the live stream. Thanks, Doron [1] https://lists.xenproject.org/archives/html/xen-announce/2020-01/msg00004.ht… [2] https://fosdem.org/2020/schedule/event/vai_memory_of_lars_kurth/

1 0