August 2022 - 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

[ACTION REQUIRED] engine-setup: getCredentials updated
by Yedidyah Bar David 25 Aug '22

25 Aug '22

Hi all, We now merged all of these patches: [1] https://github.com/oVirt/otopi/pull/29 [2] https://github.com/oVirt/ovirt-engine/pull/585 [3] https://github.com/oVirt/ovirt-engine-keycloak/pull/53 [4] https://github.com/oVirt/ovirt-dwh/pull/47 If you have a new dwh and/or keycloak, and an older engine, and run engine-setup, and get an error about getCredentials, please update both otopi and the engine. Thanks and best regards, -- Didi

1 3

Macintosh-oVirt integration with new VIRTIO compliant virtualization framework?
by ovirt＠pixerati.com 24 Aug '22

24 Aug '22

Now that Apple has implemented a VIRTIO-compliant framework (https://developer.apple.com/documentation/virtualization) has anyone tried automating VM deployment to a Macintosh host using oVirt? I'm assuming this would have to take the form of some sort of Ansible hack, correct? I can't imagine getting a Macintosh to show up as a managed node would be a simple task...

1 0

Change in DNF COPR plugin requires action
by Marcin Sobczyk 23 Aug '22

23 Aug '22

Hi All, recently there was a PR merged to DNF COPR plugin [1] that makes the default chroot on CentOS Stream 9 to be 'epel-9'. Because of this we now need to specify the 'centos-stream-9' chroot name that we use in oVirt COPR explicitly, i.e.: dnf copr enable -y ovirt/ovirt-master-snapshot centos-stream-9 I can see there's a bunch of places throughout our projects that need an update. I'll post PRs for the ones I can spot. Regards, Marcin [1] https://github.com/rpm-software-management/dnf-plugins-core/pull/459/files

2 3

ovirt-engine-4.5.2.4 has been tagged
by Martin Perina 19 Aug '22

19 Aug '22

ovirt-engine-4.5.2.4 has been tagged -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0

github testing: merge with branch, or use PR HEAD?
by Yedidyah Bar David 17 Aug '22

17 Aug '22

Hi all, I was annoyed for some time now by the fact that when I used some github-CI-generated RPMs, with a git hash in their names, I could never find this git hash anywhere - not in my local git repo, nor in github. Why is it so? Because, if I got it right, the default for 'actions/checkout@v2' is to merge the PR HEAD with the branch HEAD. See e.g. [1]: HEAD is now at 7bbb40c9a Merge 026bb9c672bf46786dd6d16f4cbe0ecfa84c531d into 35e217936b5571e9657946b47333a563373047bb Meaning: my patch was 026bb9c, master was 35e2179, and the generated RPMs will have 7bbb40c9a, not to be found anywhere else. If you check the main PR page [3], you can find there '026bb9c', but not '7bbb40c9a'. (Even 026bb9c might require some effort, e.g. "didib force-pushed the add-hook-log-console branch 2 times, most recently from c90e658 to 66ebc88 yesterday". I guess this is the result of github discouraging force-pushes, in direct opposite of gerrit, which had a notion of different patchsets for a single change. I already ranted about this in the past, but that's not the subject of the current message). This is not just an annoyance, it's a real difference in semantics. In gerrit/jenkins days, IIRC most/all projects I worked on, ran CI testing/building on the pushed HEAD, and didn't touch it. Rebase, if at all, happened either explicitly, or at merge time. actions/checkout's default, to auto-merge, is probably meant to be more "careful" - to test what would happen if the code is merged. I agree this makes sense. But I personally think it's almost always ok to test on the pushed HEAD and not rebase/merge _implicitely_. What do you think? It should be easy to change, using [2]: - uses: actions/checkout@v2 with: ref: ${{ github.event.pull_request.head.sha }} No need to reach a complete consensus - can be decided upon per-project/repo. But if you disagree, I'd like to understand why. Thanks. Best regards, [1] https://github.com/oVirt/vdsm/runs/6881311961?check_suite_focus=true [2] https://github.com/marketplace/actions/checkout?version=v2.4.2#checkout-pul… [3] https://github.com/oVirt/vdsm/pull/249 -- Didi

6 16

ovirt-engine-4.5.2.2 has been tagged
by Martin Perina 10 Aug '22

10 Aug '22

ovirt-engine-4.5.2.2 has been tagged -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0

Starting with oVirt
by Teemu Saarinen 03 Aug '22

03 Aug '22

Hi, Our company is planning of taking oVirt in into our environment. We would have a few questions for that if you could guide us. Hardware: What would be the minimum configuration for us using oVirt?. Idea would be to replace all our current Linux and Windows servers with oVirt. There are currently 24 servers in use. The goal would also be that the virtual servers could be migrated live and also in the HA configuration, i.e. if one hardware crashes execution continues on the other. As far as I understand Ovirt enables this? So we would like to know what kind of hardware (minimum) we should have for this size of environment? Storagin: Do all machines need a lot of hard disk space or is it enough to have only one or two? I'm referring to shared storage. Can you also have storagin as HA? Host: What happens to HOST1 and HOST2 virtual machines if the oVirt host server crashes? Do they continue to operate without it, or do they crash at the same time? Thank You! Teemu S.

1 0

ovirt-engine-4.5.2.1 has been tagged
by Martin Perina 03 Aug '22

03 Aug '22

ovirt-engine-4.5.2.1 has been tagged -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0