what happens at vdsm host certificate expiration
by Vinz Vinz
Hi Team,
we are using a custom certificate on the engine apache GUI /etc/pki/ovirt-engine/certs/apache.cer (following https://myhomelab.gr/linux/2020/01/20/replacing_ovirt_ssl.html) and it works fine. The certificate is valid for a very long period.
It seems the vdsm certificate (/etc/pki/vdsm/certs/vdsmcert.pem), on hosts side, has been renewed automatically at that time, but for only one year.
Now we wonder, what will happen when the vdsm certificate will expire? hosts will stop to be in the cluster? if yes what should we do to avoid that? is there a possibility to also apply our custom cert as vdsm cert?
This is for ovirt 4.4 running on rhel8
thx a lot in advance
2 years, 4 months
Hosted-engine update error
by Jason Beard
Greetings! I was updating from ovirt 4.5.3 to ovirt 4.5.4 and my hosted engine has some package errors but the update seems to complete. The errors still exist with dnf. I feel like this is something that needs to be resolved but not sure.
When I query the rpmdb I do see ovirt-*-4.5.4.x packages are installed. When I ran the engine-setup it completed with no errors.
Errors:
# dnf update
Last metadata expiration check: 4:11:16 ago on Tue 20 Dec 2022 04:59:46 AM CST.
Error:
Problem: package gluster-ansible-cluster-1.0.1-2.el8.noarch requires ansible >= 2.6, but none of the providers can be installed
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.20-1.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch
- package ansible-core-2.13.5-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch
- package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.13.5-1.el8.x86_64
- cannot install the best update candidate for package gluster-ansible-cluster-1.0-5.el8.noarch
- cannot install the best update candidate for package ansible-core-2.13.5-1.el8.x86_64
- package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering
- package ansible-1:2.9.27-5.el8.noarch is filtered out by exclude filtering
- package ansible-6.3.0-1.el8.noarch is filtered out by exclude filtering
- package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering
- package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering
- package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering
- package ansible-1:2.9.27-4.el8.noarch is filtered out by exclude filtering
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
2 years, 4 months
dashboard grafana to check status of host (up, maintenance or down)
by layeozil＠gmail.com
Hello team,
I have the rhv plateform installed with the monitoring tool grafana with default dashboard (executive, inventory, servicelevel and trend).
I would like to know how i can create a dashboard which will monitor the hosts status more precisely the status (down, up or in maintenance and list them).
2 years, 4 months
OVF_Store In Every Storage Doamin - Can We Remove?
by Matthew J Black
Hi All,
The Subject pretty much sums up the question I want to ask: There are two OVF_Store Disks created in all eight Storage Domains we have, making 16 total. This is cluttering up several of our views in the oVirt Admin Webpages. Is there anything stopping us from deleting some/all of these?
Cheers
Dulux-Oz
2 years, 4 months
ovirt node Emulex network
by parallax
ovirt-node-ng-installer-4.4.10-2022030308.el8
ovirt-node-ng-installer-4.4.10-2022030308
can't recognize network intefaces:
06:00.0 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.1 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.4 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
06:00.5 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC
(be3) [19a2:0710] (rev 01)
anyone know howto fix it ?
2 years, 4 months
oVirt 4.5.4 is now generally available
by Sandro Bonazzola
oVirt 4.5.4 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.5.4, as of December 5th, 2022.
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.4.
Important notes before you install / upgrade
Some of the features included in oVirt 4.5.4 require content that is
available in RHEL 8.7 (or newer) and derivatives.
NOTE: If you’re going to install oVirt 4.5.4 on RHEL or similar, please
read Installing on RHEL or derivatives
<https://ovirt.org/download/install_on_rhel.html> first.
Documentation
Be sure to follow instructions for oVirt 4.5!
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
What’s new in oVirt 4.5.4 Release?
This release is available now on x86_64 architecture for:
-
CentOS Stream 8
-
CentOS Stream 9
-
RHEL 8.7 and derivatives
-
RHEL 9.1 and derivatives
This release supports Hypervisor Hosts on x86_64:
-
oVirt Node NG based on CentOS Stream 8
-
oVirt Node NG based on CentOS Stream 9
-
CentOS Stream 8
-
CentOS Stream 9
-
RHEL 8.7 and derivatives
-
RHEL 9.1 and derivatives
Builds are also available for ppc64le and aarch64.
Known issues:
-
On EL9 with UEFI secure boot, vdsm fails to decode DMI data due to
Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> -
python-dmidecode module fails to decode DMI data
oVirt Node will be released as soon as GitHub Runners will be back online
(Ticket opened: https://issues.redhat.com/browse/CPDEVOPS-606 )
See the release notes for installation instructions and a list of new
features and bugs fixed.
Additional resources:
-
Read more about the oVirt 4.5.4 release highlights:
https://www.ovirt.org/release/4.5.4/
-
Check out the latest project news on the oVirt blog:
https://blogs.ovirt.org/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
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 years, 4 months
Error try setting up oVirt 4.5 with AD using ovirt-engine-extension-aaa-ldap-setup
by kalilac＠gmail.com
Hello all.
I just did a fresh install of oVirt 4.5 running on top of CentOS 9 Stream. Everything was fine but when I try to setting up to use our AD, using the ovirt-engine-extension-aaa-ldap-setup command, always return me this error:
[WARNING] Cannot resolve Global Catalog SRV record for XXXX.XXX.XX. Please check you have entered correct Active Directory forest name and check that forest is resolvable by your system DNS servers
[ ERROR ] Failed to execute stage 'Environment customization': Active Directory forest is not resolvable, please make sure you've entered correct forest name. If for some reason you can't use forest and you need some special configuration instead, please refer to examples directory provided by ovirt-engine-extension-aaa-ldap package.
What is strange is that if we try to resolve our AD name responds fine.
oVirt version: 4.5.4-1.e|9
CentOS version: Stream 9
Ovirt-engine-extension-aaa-ldap-setup: 1.4.6-1.el9
Anyone passed for this?
Best regards
2 years, 4 months
Thin provisioning max size
by Jean-Louis Dupond
Hi,
This weekend we've got an issue with a disk that did not get extend
anymore because of the following reason:
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') abnormal vm stop device ua-6ccc3ee1-02e5-4fad-b1b7-9f2d6c187416 error enospc (vm:5185)
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') CPU stopped: onIOError (vm:6066)
> 2022-12-17 12:12:27,852+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') drive 'sda' needs extension (storage:963)
> 2022-12-17 12:12:27,854+0100 INFO (libvirt/events) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') CPU stopped: onSuspend (vm:6066)
> 2022-12-17 12:12:27,931+0100 INFO (periodic/3) [virt.vm] (vmId='a2926e08-d19b-4e3a-98fa-cc1ee241a037') Drive sda extended to maximum size, disabling monitoring (thinp:357)
Now I looked into the VDSM code, and noticed that some years ago there
was a commit
https://github.com/oVirt/vdsm/commit/93e955af9e4989711403e81835bb469b2e9c...
Where the estimate of 1.1x the disk size was used as max size.
But is this 1.1x still valid? As for example since some years there are
dirty bitmaps etc which all take space in the qcow2 image.
As far as I see there is no way to really calculate the exact max size
(as it might depend on external factors), but it might be useful to
extend the 1.1x to 1.2x for example?
Or maybe the limit is not needed anymore at all?
Thanks
Jean-Louis
2 years, 4 months
attaching a diskto a vm with the incremental statement
by Nathanaël Blanchet
Hello,
I am used to create new vm with ovirt_vm module.
Now, I want that the disk of each new created vm to be with the
incremental statement.
I tried so:
disks:
- id: "{{result.disk.id}}"
bootable: True
interface: virtio_scsi
backup: incremental
but it seems that the backup item is not implemented.
How to attach a disk with the incremental statement?
2 years, 4 months
