oVirh Host Update Problem
by Vladislav Solovei
Freshly installed using nightly build, freshly installed OS :)
OS: AlmaLinux 9.5
Can't update the system (and can't reinstall the Host)
Repository copr:copr.fedorainfracloud.org:ovirt:ovirt-master-snapshot is listed more than once in the configuration
Last metadata expiration check: 0:22:12 ago on Fri 24 Jan 2025 11:41:49 EET.
Error:
Problem: package rdo-ovn-host-2:22.12-2.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires rdo-ovn = 2:22.12-2.el9s, but none of the providers can be installed
- cannot install the best update candidate for package ovn22.09-host-22.09.0-31.el9s.x86_64
- package rdo-ovn-2:22.12-2.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing is filtered out by exclude filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[ovirt-master-centos-stream-openstack-yoga-testing]
name=CentOS Stream 9 - OpenStack Yoga Repository - testing
baseurl=https://buildlogs.centos.org/9-stream/cloud/$basearch/openstack-y...
gpgcheck=0
enabled=1
exclude=
openstack-ansible-core
python3-rdo-openvswitch
rdo-network-scripts-openvswitch
rdo-openvswitch
rdo-ovn
rdo-ovn-central
How can this problem be resolved?
Should the rdo-ovn package, which is a dependency of rdo-ovn-host-2:22.12-2, be filtered out?
1 week, 6 days
Couldn't resolve host name for http://mirrorlist.centos.org/
by fiorletta＠ssolo.eu
Hi Dear,
I need to install 3 nodes with self-hosted-engine but with all linux distributions tried I receive the error below:
ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.1.50]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=storage-c... [Could not resolve host: mirrorlist.centos.org]", "rc": 1, "results": []}
2025-02-24 17:03:59,038+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}
2025-02-24 17:03:59,640+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. \n'
2025-02-24 17:03:59,640+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'The Python crypt module is deprecated and will be removed from Python 3.13. \n'
2025-02-24 17:03:59,641+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'Install the passlib library for continued encryption functionality. This \n'
2025-02-24 17:03:59,641+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'feature will be removed in version 2.17. Deprecation warnings can be disabled \n'
2025-02-24 17:03:59,641+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'by setting deprecation_warnings=False in ansible.cfg.\n'
2025-02-24 17:03:59,643+0100 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Failed executing ansible-playbook
2025-02-24 17:04:21,338+0100 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:164 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.
In /etc/yum.repos.d there isn't the site http://mirrorlist.centos.org on none of the repository configuration files.
If I install the engine on physical host all work fine and the installation done without problems.
Does anyone have any idea why I find the old, now decommissioned, Centos site in the engine configuration?
Tnx
2 weeks
Re: Unable to create a network bond in OLVM
by kodfejtok-hamachi.6＠icloud.com
Hey,
I had the same issue with Oracle Linux Virtualization. There is a known bug which prevents using bonds.
If you’re on Oracle Linux, you can use kernel version kernel-uek-0:5.15.0-103.114.4.el8uek, which is known to work. (Anything above that has not worked, below that works fine too). Unfortunately I don’t know anything about other OSes.
Best regards,
Mark
1 month, 2 weeks
oVirt Chat
by Jean-Louis Dupond
Hi all,
As we want to bring some more action in the community and some
collaboration, we would like to setup some new place to communicate for
oVirt.
The current IRC channel is quite dead, and I think IRC is not what we
want to use anymore.
Therefor the idea was to setup a Matrix Server/Channels or a Mattermost
instance.
I think both have their advantages and disadvantages, but might be nice
to hear some feedback from the community.
What would you prefer as a place to communicate with each other?
- Matrix channel on matrix.org
- Matrix server with multiple channels
- Mattermost instance
Or perhaps some other idea's? :)
Please let me know so this can be setup!
Thanks
Jean-Louis
1 month, 2 weeks
Re: oVirt New versioon ? Centos 10?
by Geoff O'Callaghan
In case you're wondering how I built it, there's no real magic.
I checked out the repository (https://github.com/oVirt/ovirt-node-ng-image)
on my alma system. It will likely be a similar result on other Linux
systems, but I didn't test any other combinations.
I use docker-ce on alma9. Note: The underlying system needs to be a
working kvm environment as the build script performs qemu based builds.
docker run -v /lib/modules/$(uname -r)/kernel:/kernel -v $PWD:/workspace
--device=/dev/kvm --device=/dev/kvm/tun --ulimit=nofile=262144:262144
--privileged -it quay.io/ovirt/buildcontainer:almalinux9 /bin/bash
cd /workspace
./build.sh
The .github/workflows/build.yml looks *mostly* correct, just some tweaks
and it should be able to create build isos - assuming the upload actions
etc still work.
Personally I do my builds via vscode devcontainers, but that's
fundamentally the above docker command.
I hope this helps.
On Thu, 13 Feb 2025 at 13:49, Geoff O'Callaghan <geoffocallaghan(a)gmail.com>
wrote:
> I've been able to build ovirt node (next) with almalinux 9 as the base
> OS. I haven't really had a chance to test it out.
>
> ovirt-node-ng-installer-4.5.6-2025021302.el9.iso
>
> ------------------------------
> *From:* Jean-Louis Dupond via Users
> *Sent:* Monday, February 03, 2025 8:43 PM
> *To:* ecsi(a)ecsi.hu; users(a)ovirt.org
> *Subject:* [ovirt-users] Re: oVirt New versioon ? Centos 10?
>
> Hi,
>
> The ovirt-node images are unmaintained atm. As the advantages versus the
> work for it are quite low.
> So except if somebody takes up maintenance of the node images, they will
> be unmaintained.
>
> CentOS 10 support will come, but that takes some time.
> Guess it's not that urgent neither, as CentOS 10 is still in early/beta
> stage.
>
> On 2/3/25 10:20, ecsi(a)ecsi.hu wrote:
> > Hi all!
> >
> > What can we know about this?
> > https://resources.ovirt.org/repos/ovirt/github-ci/ovirt-node-ng-image/
> > and will there ever be a new version besides the promises? Will there be
> Centos 10 support?
> >
> > And for those who have already given up on oVirt, what do they use
> besides proxmox?
> > _______________________________________________
> > Users mailing list -- users(a)ovirt.org
> > To unsubscribe send an email to users-leave(a)ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/OYLBS3NPEFO...
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4HYD7FA4O32...
>
1 month, 3 weeks
Powering oVirt Cluster – UPS with LiFePO4 Batteries and Automatic Shutdown
by Andrei Verovski
Hi,
I have published in my blog
https://www.vacuum-tube.eu/wp/?p=908 <https://www.vacuum-tube.eu/wp/?p=908>
small guide covering 2 topics:
1) Powering oVirt cluster hardware with budget-level UPS with LiFePO4 batteries. Most today’s budget priced UPS with power up to 10kWt still use lead-acid batteries with very low energy capacity per weight ratio and short lifespan.
2) Automatic shutdown script for all VMs and nodes in case of power line failure. It is not dependent of UPS model and its software agent. In fact, it doesn’t require UPS to have any built-in and agent software at all.
Feedback welcome.
with best regards
Andrei Verovski
1 month, 3 weeks
Shared disks with sgio and RHEL 9 or derivates
by buettner＠decoit.de
Hello ovirt Community
we are running some ovirt clusters in 4.5.x each with FC backend.
Since switching from CentOS 8 to Rockly Linux 9 as ovirt-host, the VMs with a shared LUN and SCSI-PR can no longer be started with the error sgio=unfiltered.
This means that the Windows SQL failover clusters, file server failover clusters and so on no longer work.
As is known, support for SGIO=filtered has been removed in RHEL 9 and its derivatives.
But how can shared discs be passed through to the VMs again so that SCSI-PR works? Is there an alternative?
Thanks for your feedback
1 month, 3 weeks
Networking help needed for a newbee
by mtavasso＠yahoo.co.uk
Hi experts,
I have successfully set up my KVM and hosted engine on virtmgmt network ( the KVM has the ip address of 172.18.100.15 and the hosted engine 172.18.100.30) ,
I have been able to import existing VMs (10.1.10.XXX) using virt-v2v successfully and start them, I can even access the imported VMs using the console.
However, When I try to ping or ssh these VMs from the KVM (or anywhere else for that matter) I get host unreachable .
the interesting thing is I can still access the non-migrated VMs on the same subnet from the KVM!
Examp: the non-migrated VM on 10.1.10.191 is reachable , but the migrated VM on OVIRT at 10.1.10.192 is unreachable from the KVM!
My guess is I need to tell virtmgmt to allow traffic between different IP ranges but I am not sure how and where!
Any pointers or help is much appreciated.
Thanks
Masi
1 month, 3 weeks
