how kill backup operation
by Diego Ercolani
Hello I saw there are other thread asking how to delete disk snapshots from backup operation.
We definitively need a tool to kill pending backup operations and locked snapshots.
I Think this is very frustrating ovirt is a good piece of software but it's very immature in a dirty asyncronous world.
We need a unified toolbox to clean manually and do database housekeeping.
1 year, 7 months
Interested in contributing with Spanish translation.
by Luis Pereida
Hello,
My name is Luis Pereida, I am Mexican, from Guadalajara and I am currently
an application security specialist.
Some time ago I met the O-Virt project and it helped me a lot to solve many
situations where virtualization was the perfect option.
Since some time ago I have been thinking about how to contribute to the
project, and talking with some friends, they would like to have
documentation in Spanish. Although English is basic for us, many times the
context or expressions are hard to understand.
I would like to help with that. How can I do it? I see that it is necessary
to use a Zanata account. How can I get an account?
Regards and thanks for being so supportive of the community.
1 year, 7 months
Q: Engione 4.4.10 and New Host on CentOS Stream 9
by Andrei Verovski
Hi,
I have engine version 4.4.10.7-1.el8, is it possible to set up new node
host on CentOS Stream 9, or I need to upgrade engine to version 4.5
first (which is not right now possible because of some quite old nodes) ?
Thanks
Andrei
1 year, 7 months
Moving SelfHosted Engine
by murat.celebi＠dbpro.com.tr
Hello
We have got an Production ovirt installation with 1 datacenter and 2 clusters.
Default Cluster has got 2 hosts in it. kvm01 and kvm02.
PrimarySite cluster has got 2 hosts in it. kvm03 and kvm04
Our Self hosted engine is running on kvm01. We need to migrate the Selfhosted-engine to kvm03 or kvm04 since the hosts kvm01 and kvm02 hosts are going to be retired.
Anyone has any idea how this can be accomplished?
1 year, 7 months
Failed to delete snapshot (again)
by Giulio Casella
Hi folks,
since some month I have an issue with snapshot removals (I have storware
vprotect backup system, heavily using snapshots).
After some time spent on a bugzilla
(https://bugzilla.redhat.com/show_bug.cgi?id=1948599) we discovered that
my issue is not depending on that bug :-(
So they pointed me here again.
Briefly: sometime snapshot removal fails, leaving snapshot in illegal
state. Trying to remove again (via ovirt UI) keeps failing and doesn't
solve. The only way to rebuild a consistent situation is live migrating
affected disk to another storage domain; after moving the disk, snapshot
is no more marked illegal and then I can remove it. You can imagine this
is a bit tricky, specially for large disks.
In my logs I can find:
2022-08-29 09:17:11,890+02 ERROR
[org.ovirt.engine.core.bll.MergeStatusCommand]
(EE-ManagedExecutorService-commandCoordinator-Thread-1)
[0eced56f-689d-422b-b15c-20b824377b08] Failed to live merge. Top volume
f8f84b1c-53ab-4c99-a01d-743ed3d7859b is still in qemu chain
[0ea89fbc-d39a-48ff-aa2b-0381d79d7714,
55bb387f-01a6-41b6-b585-4bcaf2ea5e32, f8f84b1c-53ab-4c99-a01d-743ed3d7859b]
My setup is ovirt-engine-4.5.2.4-1.el8.noarch, with hypervisors based on
oVirt Node 4.5.2 (vdsm-4.50.2.2-1.el8).
Thank you in advance.
Regards,
gc
1 year, 7 months
Ovirt 4.4.7, can't renew certificate of ovirt engine (certificates expired)
by vk＠itiviti.com
Hi Team,
I'm looking for your help since I didn't find any clear documentation. Is there somewhere in ovirt website a clear documentation about how to renew the engine certificates located in /etc/pki/ovirt-engine/certs/
We have an engine GUI not working, showing error message "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed".
After checking, all the cert in /etc/pki/ovirt-engine/certs/ are expired.
I didn't find a clear documentation on ovirt website, or even on redhat website (it was always about host but not the engine)
Anyway I've read that the renew process can be done via "engine-setup --offline", but when I try it, it generates this error:
--== PKI CONFIGURATION ==--
[ ERROR ] Failed to execute stage 'Environment customization': Unable to load certificate. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details.
and in log file:
File "/usr/lib64/python3.6/site-packages/cryptography/hazmat/backends/openssl/backend.py", line 1371, in load_pem_x509_certificate
"Unable to load certificate. See https://cryptography.io/en/la"
ValueError: Unable to load certificate. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details.
2022-08-29 19:16:29,502+0200 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': Unable to load certificate. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details.
I've also tried the manual procedure (using /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh) mentioned in https://users.ovirt.narkive.com/4ugjgicE/ovirt-regenerating-new-ssl-certi... (message from Alon Bar-Lev), but the 4th command always says I enter a wrogn apssword, but it's not.
we are blocked here and we can't use our ovirt cluster, so it's pretty blocking.
Thx a lot in advance
1 year, 7 months
unable to bring up gluster bricks after 4.5 upgrade
by Jayme
Hello All,
I've been struggling with a few issues upgrading my 3-node HCI custer from
4.4 to 4.5.
At present the self hosted engine VM is properly running oVirt 4.5 on
CentOS 8x stream.
First host node, I set in maintenance and installed new node-ng image. I
ran into issue with rescue mode on boot which appears to have been related
to LVM devices bug. I was able to work past that and get the node to boot.
The node running 4.5.2 image is booting properly and gluster/lvm mounts etc
all look good. I am able to activate the host and run VMs on it etc.
however, oVirt cli is showing that all bricks on host are DOWN.
I was unable to get the bricks back up even after doing a force start of
the volumes.
Here is the glusterd log from the host in question when I try force start
on the engine volume (other volumes are similar:
==> glusterd.log <==
The message "I [MSGID: 106568] [glusterd-svc-mgmt.c:266:glusterd_svc_stop]
0-management: bitd service is stopped" repeated 2 times between [2022-08-29
18:09:56.027147 +0000] and [2022-08-29 18:10:34.694144 +0000]
[2022-08-29 18:10:34.695348 +0000] I [MSGID: 106618]
[glusterd-svc-helper.c:909:glusterd_attach_svc] 0-glusterd: adding svc
glustershd (volume=engine) to existing process with pid 2473
[2022-08-29 18:10:34.695669 +0000] I [MSGID: 106131]
[glusterd-proc-mgmt.c:84:glusterd_proc_stop] 0-management: scrub already
stopped
[2022-08-29 18:10:34.695691 +0000] I [MSGID: 106568]
[glusterd-svc-mgmt.c:266:glusterd_svc_stop] 0-management: scrub service is
stopped
[2022-08-29 18:10:34.695832 +0000] I [MSGID: 106617]
[glusterd-svc-helper.c:698:glusterd_svc_attach_cbk] 0-management: svc
glustershd of volume engine attached successfully to pid 2473
[2022-08-29 18:10:34.703718 +0000] E [MSGID: 106115]
[glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
failed on gluster2.xxxxx. Please check log file for details.
[2022-08-29 18:10:34.703774 +0000] E [MSGID: 106115]
[glusterd-mgmt.c:119:gd_mgmt_v3_collate_errors] 0-management: Post commit
failed on gluster1.xxxxx. Please check log file for details.
[2022-08-29 18:10:34.703797 +0000] E [MSGID: 106664]
[glusterd-mgmt.c:1969:glusterd_mgmt_v3_post_commit] 0-management: Post
commit failed on peers
[2022-08-29 18:10:34.703800 +0000] E [MSGID: 106664]
[glusterd-mgmt.c:2664:glusterd_mgmt_v3_initiate_all_phases] 0-management:
Post commit Op Failed
If I run start command manually on host cli:
gluster volume start engine force
volume start: engine: failed: Post commit failed on gluster1.xxxx. Please
check log file for details.
Post commit failed on gluster2.xxxx. Please check log file for details.
I feel like this may be some issue with the difference in major versions of
GlusterFS on the nodes but I am unsure. The other nodes are running
ovirt-node-ng-4.4.6.3
At this point I am afraid to bring down any other node to attempt upgrading
it without the bricks in UP status on the first host. I do not want to lose
quorum and potentially disrupt running VMs.
Any idea why I can't seem to start the volumes on the upgraded host?
Thanks!
1 year, 8 months
(no subject)
by parallax
oVirt version:4.4.4.7-1.el8
I have several servers in cluster and I got this error:
Data Center is being initialized, please wait for initialization to
complete.
VDSM command GetStoragePoolInfoVDS failed: PKIX path validation failed:
java.security.cert.CertPathValidatorException: validity check failed
the SPM role is constantly being transferred to the servers and I can't do
anything
in StorageDomains storages are in inactive status but virtual machines are
runnig
how ti fix it?
1 year, 8 months
Commissioning hew host on centos9
by David Johnson
Good evening all,
I am trying to commission an ovirt host on new hardware using Centos 9.
I followed the pre-install instructions at
https://www.ovirt.org/download/install_on_rhel.html, and eventually figured
out that this line was missing from the preparation scripts:
dnf install rdo-openvswitch-2.15
With that, I was able to continue installation.
After completing the instructions, DNF update reports this:
[root@localhost administrator]# dnf update --nobest
Last metadata expiration check: 0:01:06 ago on Fri 26 Aug 2022 08:20:27 PM
CDT.
Dependencies resolved.
Problem 1: package ovirt-openvswitch-2.15-4.el9.noarch requires
openvswitch2.15, but none of the providers can be installed
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-99.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-51.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-56.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-81.el9s.x86_64
- cannot install the best update candidate for package
ovirt-openvswitch-2.15-4.el9.noarch
- cannot install the best update candidate for package
openvswitch2.15-2.15.0-99.el9s.x86_64
Problem 2: problem with installed package
ovirt-openvswitch-2.15-4.el9.noarch
- package ovirt-openvswitch-2.15-4.el9.noarch requires openvswitch2.15,
but none of the providers can be installed
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-99.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-51.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-56.el9s.x86_64
- package rdo-openvswitch-2:2.17-2.el9s.noarch obsoletes openvswitch2.15
< 2.17 provided by openvswitch2.15-2.15.0-81.el9s.x86_64
- cannot install the best update candidate for package
rdo-openvswitch-1:2.15-2.el9s.noarch
DNF info lists these
[root@localhost administrator]# dnf list installed |grep openvswitch
centos-release-nfv-openvswitch.noarch 1-4.el9s
@c9s-extras-common
network-scripts-openvswitch2.15.x86_64 2.15.0-99.el9s
@centos-nfv-openvswitch
openvswitch-selinux-extra-policy.noarch 1.0-31.el9s
@centos-nfv-openvswitch
*openvswitch2.15.x86_64 2.15.0-99.el9s
@centos-nfv-openvswitch*ovirt-openvswitch.noarch
2.15-4.el9 @centos-ovirt45
python3-openvswitch2.15.x86_64 2.15.0-99.el9s
@centos-nfv-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el9s
@centos-openstack-yoga
*Questions:*
1. Is this a problem?
2. If this is a problem, is there an FAQ sheet or known steps to work
around/fix this?
3. Does there need to be an update to the pre-installation instructions?
*David Johnson*
*Director of Development, Maxis Technology*
844.696.2947 ext 702 (o) | 479.531.3590 (c)
<https://www.linkedin.com/in/pojoguy/>
<https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson...>
<https://maxistechnology.com/>
*Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>
1 year, 8 months
oVirt 4.5 self-hosted network not working
by Paul-Erik Törrönen
Specifically, the installation (ovirt-hosted-engine-setup) completes successfully, and the engine VM is up and running, but it can not be accessed from any other machine in the same subnet but the host machine.
I can ssh (from the host) to the engine VM, and confirm that initiating the connection from the engine VM to any other machine, except the host, fails. The routing looks correct and stopping the firewalld on the engine VM does not make any difference. Nor does stopping the firewalld on the host either make any difference.
This seems like a failure in correctly setting up the host routing for the engine VM.
How do I fix this?
Poltsi
1 year, 8 months
