- Users - oVirt List Archives

Re: Users Digest, Vol 131, Issue 39
by David Johnson 21 Aug '22

21 Aug '22

oVirt engine is not supported on Centos 9. This is resolved. *David Johnson* On Sun, Aug 21, 2022 at 1:29 PM <users-request(a)ovirt.org> wrote: > Send Users mailing list submissions to > users(a)ovirt.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > users-request(a)ovirt.org > > You can reach the person managing the list at > users-owner(a)ovirt.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..."Today's Topics: > > 1. Ovirt 4.5 standalone engine does not install on Centos 9 stream > (David Johnson) > > > > ---------- Forwarded message ---------- > From: David Johnson <djohnson(a)maxistechnology.com> > To: users <users(a)ovirt.org> > Cc: > Bcc: > Date: Sun, 21 Aug 2022 13:28:16 -0500 > Subject: [ovirt-users] Ovirt 4.5 standalone engine does not install on > Centos 9 stream > Good afternoon all, > > The instructions at > https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manage… > say: > > Ensure all packages are up to date: > > # dnf upgrade --nobest > Reboot the machine if any kernel-related packages were updated. > > Install the ovirt-engine package and dependencies. > > # dnf install ovirt-engine > Run the engine-setup command to begin configuring the oVirt Engine: > > # engine-setup > > I did figure out that the modules that were in centos 8 are now straight > out installs except for the pkideps. haven't got that one figured out yet. > > At this step, engine-setup is nowhere to be found on the system, and there > appears to be no ovirt-engine RPM available. > > Terminal dump of the offending session: > > [root@ovirt2 administrator]# *dnf install -y centos-release-ovirt45* > Last metadata expiration check: 0:12:04 ago on Sun 21 Aug 2022 12:58:00 PM > CDT. > Package centos-release-ovirt45-9.1-2.el9s.noarch is already installed. > Dependencies resolved. > Nothing to do. > Complete! > [root@ovirt2 administrator]# > *dnf upgrade --nobest*Last metadata expiration check: 0:12:15 ago on Sun > 21 Aug 2022 12:58:00 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 > - package python3-rdo-openvswitch-2:2.17-2.el9s.noarch requires > rdo-openvswitch = 2:2.17-2.el9s, but none of the providers can be installed > - cannot install the best update candidate for package > python3-openvswitch2.15-2.15.0-99.el9s.x86_64 > > ==================================================================================================================================================== > Package Architecture > Version Repository > Size > > ==================================================================================================================================================== > Skipping packages with broken dependencies: > python3-rdo-openvswitch noarch > 2:2.17-2.el9s centos-openstack-yoga > 7.5 k > > Transaction Summary > > ==================================================================================================================================================== > Skip 1 Package > > Nothing to do. > Complete! > > I confirmed that the required OpenVSwitch version is installed: > > [root@ovirt2 administrator]# *dnf list installed |grep openvswitch* > > centos-release-nfv-openvswitch.noarch 1-4.el9s > @c9s-extras-common > 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 > > > > [root@ovirt2 administrator]# *dnf install ovirt-engine* > Last metadata expiration check: 0:12:29 ago on Sun 21 Aug 2022 12:58:00 PM > CDT. > No match for argument: ovirt-engine > Error: Unable to find a match: ovirt-engine > [root@ovirt2 administrator]# > > > DNF list shows this: > > [root@ovirt2 administrator]# *dnf list|grep engine* > fio-engine-dev-dax.x86_64 3.27-7.el9 > appstream > fio-engine-http.x86_64 3.27-7.el9 > appstream > fio-engine-libaio.x86_64 3.27-7.el9 > appstream > fio-engine-libpmem.x86_64 3.27-7.el9 > appstream > fio-engine-nbd.x86_64 3.27-7.el9 > appstream > fio-engine-pmemblk.x86_64 3.27-7.el9 > appstream > fio-engine-rados.x86_64 3.27-7.el9 > appstream > fio-engine-rbd.x86_64 3.27-7.el9 > appstream > fio-engine-rdma.x86_64 3.27-7.el9 > appstream > gtk-murrine-engine.x86_64 0.98.2-23.el9 > epel > gtk2-engines.x86_64 2.20.2-24.el9 > epel > gtk2-engines-devel.x86_64 2.20.2-24.el9 > epel > kwebenginepart.x86_64 > 22.04.1-1.el9.next epel-next > lumina-themeengine.x86_64 1.6.2-2.el9 > epel > mariadb-oqgraph-engine.x86_64 3:10.5.16-2.el9 > appstream > openscap-engine-sce.i686 1:1.3.6-4.el9 > appstream > openscap-engine-sce.x86_64 1:1.3.6-4.el9 > appstream > openscap-engine-sce-devel.i686 1:1.3.6-4.el9 > crb > openscap-engine-sce-devel.x86_64 1:1.3.6-4.el9 > crb > openstack-heat-engine.noarch 1:18.0.0-1.el9s > centos-openstack-yoga > openstack-mistral-engine.noarch 14.0.0-1.el9s > centos-openstack-yoga > openstack-mistral-event-engine.noarch 14.0.0-1.el9s > centos-openstack-yoga > openstack-murano-engine.noarch 13.0.0-1.el9s > centos-openstack-yoga > openstack-sahara-engine.noarch 1:16.0.0-1.el9s > centos-openstack-yoga > openstack-senlin-engine.noarch 13.0.0-1.el9s > centos-openstack-yoga > openstack-watcher-decision-engine.noarch 8.0.0-1.el9s > centos-openstack-yoga > ovirt-engine-appliance.x86_64 > 4.5-20220419160254.1.el9 ovirt-45-upstream > ovirt-engine-extension-aaa-ldap.noarch 1.4.6-1.el9 > centos-ovirt45 > ovirt-engine-extension-aaa-ldap-setup.noarch 1.4.6-1.el9 > centos-ovirt45 > ovirt-engine-extensions-api.noarch 1.0.1-1.el9 > centos-ovirt45 > ovirt-engine-extensions-api-javadoc.noarch 1.0.1-1.el9 > centos-ovirt45 > ovirt-engine-nodejs-modules.noarch 2.3.9-1.el9 > centos-ovirt45 > ovirt-engine-wildfly.x86_64 24.0.1-1.el9 > centos-ovirt45 > ovirt-hosted-engine-ha.noarch 2.5.0-1.el9 > centos-ovirt45 > ovirt-hosted-engine-setup.noarch 2.6.5-1.el9 > centos-ovirt45 > pentaho-reporting-flow-engine.noarch 1:0.9.4-24.el9 > appstream > pki-servlet-engine.noarch 1:9.0.50-1.el9 > appstream > python3-ovirt-engine-sdk4.x86_64 4.5.1-1.el9 > centos-ovirt45 > qatengine.x86_64 0.6.10-1.el9 > appstream > qt5-qtwebengine.x86_64 > 5.15.8-5.el9.next epel-next > qt5-qtwebengine-devel.x86_64 > 5.15.8-5.el9.next epel-next > qt5-qtwebengine-devtools.x86_64 > 5.15.8-5.el9.next epel-next > qt5-qtwebengine-examples.x86_64 > 5.15.8-5.el9.next epel-next > texlive-stackengine.noarch > 9:20200406-25.el9 appstream > > > Please advise. > > *David Johnson* > > _______________________________________________ > 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/ >

1 0

Ovirt 4.5 standalone engine does not install on Centos 9 stream
by David Johnson 21 Aug '22

21 Aug '22

Good afternoon all, The instructions at https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manage… say: Ensure all packages are up to date: # dnf upgrade --nobest Reboot the machine if any kernel-related packages were updated. Install the ovirt-engine package and dependencies. # dnf install ovirt-engine Run the engine-setup command to begin configuring the oVirt Engine: # engine-setup I did figure out that the modules that were in centos 8 are now straight out installs except for the pkideps. haven't got that one figured out yet. At this step, engine-setup is nowhere to be found on the system, and there appears to be no ovirt-engine RPM available. Terminal dump of the offending session: [root@ovirt2 administrator]# *dnf install -y centos-release-ovirt45* Last metadata expiration check: 0:12:04 ago on Sun 21 Aug 2022 12:58:00 PM CDT. Package centos-release-ovirt45-9.1-2.el9s.noarch is already installed. Dependencies resolved. Nothing to do. Complete! [root@ovirt2 administrator]# *dnf upgrade --nobest*Last metadata expiration check: 0:12:15 ago on Sun 21 Aug 2022 12:58:00 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 - package python3-rdo-openvswitch-2:2.17-2.el9s.noarch requires rdo-openvswitch = 2:2.17-2.el9s, but none of the providers can be installed - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-99.el9s.x86_64 ==================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================== Skipping packages with broken dependencies: python3-rdo-openvswitch noarch 2:2.17-2.el9s centos-openstack-yoga 7.5 k Transaction Summary ==================================================================================================================================================== Skip 1 Package Nothing to do. Complete! I confirmed that the required OpenVSwitch version is installed: [root@ovirt2 administrator]# *dnf list installed |grep openvswitch* centos-release-nfv-openvswitch.noarch 1-4.el9s @c9s-extras-common 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 [root@ovirt2 administrator]# *dnf install ovirt-engine* Last metadata expiration check: 0:12:29 ago on Sun 21 Aug 2022 12:58:00 PM CDT. No match for argument: ovirt-engine Error: Unable to find a match: ovirt-engine [root@ovirt2 administrator]# DNF list shows this: [root@ovirt2 administrator]# *dnf list|grep engine* fio-engine-dev-dax.x86_64 3.27-7.el9 appstream fio-engine-http.x86_64 3.27-7.el9 appstream fio-engine-libaio.x86_64 3.27-7.el9 appstream fio-engine-libpmem.x86_64 3.27-7.el9 appstream fio-engine-nbd.x86_64 3.27-7.el9 appstream fio-engine-pmemblk.x86_64 3.27-7.el9 appstream fio-engine-rados.x86_64 3.27-7.el9 appstream fio-engine-rbd.x86_64 3.27-7.el9 appstream fio-engine-rdma.x86_64 3.27-7.el9 appstream gtk-murrine-engine.x86_64 0.98.2-23.el9 epel gtk2-engines.x86_64 2.20.2-24.el9 epel gtk2-engines-devel.x86_64 2.20.2-24.el9 epel kwebenginepart.x86_64 22.04.1-1.el9.next epel-next lumina-themeengine.x86_64 1.6.2-2.el9 epel mariadb-oqgraph-engine.x86_64 3:10.5.16-2.el9 appstream openscap-engine-sce.i686 1:1.3.6-4.el9 appstream openscap-engine-sce.x86_64 1:1.3.6-4.el9 appstream openscap-engine-sce-devel.i686 1:1.3.6-4.el9 crb openscap-engine-sce-devel.x86_64 1:1.3.6-4.el9 crb openstack-heat-engine.noarch 1:18.0.0-1.el9s centos-openstack-yoga openstack-mistral-engine.noarch 14.0.0-1.el9s centos-openstack-yoga openstack-mistral-event-engine.noarch 14.0.0-1.el9s centos-openstack-yoga openstack-murano-engine.noarch 13.0.0-1.el9s centos-openstack-yoga openstack-sahara-engine.noarch 1:16.0.0-1.el9s centos-openstack-yoga openstack-senlin-engine.noarch 13.0.0-1.el9s centos-openstack-yoga openstack-watcher-decision-engine.noarch 8.0.0-1.el9s centos-openstack-yoga ovirt-engine-appliance.x86_64 4.5-20220419160254.1.el9 ovirt-45-upstream ovirt-engine-extension-aaa-ldap.noarch 1.4.6-1.el9 centos-ovirt45 ovirt-engine-extension-aaa-ldap-setup.noarch 1.4.6-1.el9 centos-ovirt45 ovirt-engine-extensions-api.noarch 1.0.1-1.el9 centos-ovirt45 ovirt-engine-extensions-api-javadoc.noarch 1.0.1-1.el9 centos-ovirt45 ovirt-engine-nodejs-modules.noarch 2.3.9-1.el9 centos-ovirt45 ovirt-engine-wildfly.x86_64 24.0.1-1.el9 centos-ovirt45 ovirt-hosted-engine-ha.noarch 2.5.0-1.el9 centos-ovirt45 ovirt-hosted-engine-setup.noarch 2.6.5-1.el9 centos-ovirt45 pentaho-reporting-flow-engine.noarch 1:0.9.4-24.el9 appstream pki-servlet-engine.noarch 1:9.0.50-1.el9 appstream python3-ovirt-engine-sdk4.x86_64 4.5.1-1.el9 centos-ovirt45 qatengine.x86_64 0.6.10-1.el9 appstream qt5-qtwebengine.x86_64 5.15.8-5.el9.next epel-next qt5-qtwebengine-devel.x86_64 5.15.8-5.el9.next epel-next qt5-qtwebengine-devtools.x86_64 5.15.8-5.el9.next epel-next qt5-qtwebengine-examples.x86_64 5.15.8-5.el9.next epel-next texlive-stackengine.noarch 9:20200406-25.el9 appstream Please advise. *David Johnson*

1 0

Async release for ovirt-engine (4.5.2.4) is now available
by Lev Veyde 21 Aug '22

21 Aug '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.2.4) that fixes an important bug: - Bug 2097560 <https://bugzilla.redhat.com/2097560> - Fixed checking ovirt-provider-ovn certificate validity The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. Thanks in advance, -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Problems Installing oVirt 4.5 on Centos Stream 9
by David Johnson 21 Aug '22

21 Aug '22

Good evening all, *High level goal:* We are preparing to upgrade our hosting OS to Centos Stream 9, and update to the latest oVirt patch level. We are running with a standalone engine. The immediate goal is to stand up a brand new engine on bare metal running CentOS 9. Once the new engine is configured, the engine database will be migrated from the current system production engine to the new to-be production engine and upgraded. After successful engine upgrade, we will be commissioning a new host and then upgrading the hosts in sequence. *Problem:* When installing the ovirt standalone engine, there is a requirement to follow the instructions at https://www.ovirt.org/download/install_on_rhel.html . I found I had to enable both epel and crb (formerly powertools) (both undocumented) before I could complete this step. After following those instructions with the necessary pieces I had identified as missing, I returned to section 3.2 Enabling the oVirt Engine Repositories. The next step is: [root@ovirt2 administrator]# *dnf install -y centos-release-ovirt45* Last metadata expiration check: 0:12:58 ago on Sat 20 Aug 2022 09:50:00 PM CDT. Package centos-release-ovirt45-9.1-2.el9s.noarch is already installed. Dependencies resolved. Nothing to do. Complete! Following this, The commands to enable the repositories all return "Error Unable to find a match: xxxx" Sample: [root@ovirt2 administrator]# *dnf module -y enable javapackages-tools* Last metadata expiration check: 0:03:31 ago on Sat 20 Aug 2022 09:50:00 PM CDT. Error: Problems in request: missing groups or modules: javapackages-tools [root@ovirt2 administrator]# *dnf module -y enable postgresql:12* Last metadata expiration check: 0:07:43 ago on Sat 20 Aug 2022 09:50:00 PM CDT. Error: Problems in request: missing groups or modules: postgresql:12 Please advise. *David Johnson*

2 1

node 4.5.2 doesn't activate logical volumes on boot
by p.staniforth＠leedsbeckett.ac.uk 21 Aug '22

21 Aug '22

Hello when booting an upgraded 4.5.2 node it is not activating local logical volumes used for gluster bricks. The output of lvmconfig is devices { use_devicesfile=1 multipath_wwids_file="" scan_lvs=0 hints="none" } and the output of lvmdevices is Device /dev/sdg2 IDTYPE=sys_wwid IDNAME=t10.ATA_____DELLBOSS_VD_____________________________610c9e14a9070010\0\0\0\0 DEVNAME=/dev/sdg2 PVID=fpim51dQp3b8fwqc8ymFye7vkBa6WeL4 PART=2 Device /dev/sda IDTYPE=sys_wwid IDNAME=t10.ATA_____ST2000NX0423________________________________________W462QSFT DEVNAME=/dev/sda PVID=dkLRQ69NRh0YvRvUK7cyIGLlJMOFkKcD the gluster lv from lvscan are inactive '/dev/RHGS_vg_diska/diska_lv_pool' [<1.79 TiB] inherit inactive '/dev/RHGS_vg_diska/diska_lv' [1.80 TiB] inherit after running vgchange -a y RHGS_vg_diska ACTIVE '/dev/RHGS_vg_diska/diska_lv_pool' [<1.79 TiB] inherit ACTIVE '/dev/RHGS_vg_diska/diska_lv' [1.80 TiB] inherit Thanks for any help

2 2

Clone template on MBS not working
by Jöran Malek 20 Aug '22

20 Aug '22

I created a test-setup with oVirt 4.5.2 from scratch, with hyperconverged Ceph installed, with following services in use: - iSCSI Gateway for Hosted Engine Disk - NFS for disk upload/import - RBD/MBS for template disks and VM disks My issue now is that I can download a VM from ovirt-image-repository and import that as template into the NFS domain. After that I go into the template and copy the boot disk onto the block storage. This is successfully copied, and I go ahead and remove the original disk to the NFS storage domain. So now there is only one disk left on the Managed Block Storage domain. Cloning the template results in a failed attempt with erors in DeleteImageGroupVDS. Attached are vdsm.log, supervdsm.log and engine.log. On a related note: Copying the disk from NFS to MBS, then creating a VM, assigning that disk, making a template off of that and cloning that works just fine - though I then have following disks in RBD, which I'd like to avoid: - initial-disk imported to MBS for VM template [deleted] - template disk as snapshot of initial-disk - template clone disk as snapshot of template disk With the copying from NFS approach I get a template which is also the root disk, not a snapshot of a deleted disk. Is this something that hasn't been seen yet? Best, Jöran

1 0

GlusterFS Network issue
by Facundo Badaracco 19 Aug '22

19 Aug '22

Hi everyone. I have deployed a 3x replica glusterfs succesfully. I have 4 nic in each server. Will be using 2 bond, one for gluster and the other for the vm. My doubt is: Actually, my network is 192.168.2.0/23 The IP of bond0 and bond1 should be in differente networks? Can i give, for example, 192.168.2.3 to bond0 and 192.168.2.4 to bond1? If above can be do it, how? Thx in advance

3 4

Should I migrate existing oVirt Engine, or deploy new?
by David White 19 Aug '22

19 Aug '22

Hello, I have just purchased a Synology SA3400 which I plan to use for my oVirt storage domain(s) going forward. I'm currently using Gluster storage in a hyperconverged environment. My goal now is to: - Use the Synology Virtual Machine manager to host the oVirt Engine on the Synology - Setup NFS storage on the Synology as the storage domain for all VMs in our environment - Migrate all VM storage onto the new NFS domain - Get rid of Gluster My first step is to migrate the oVirt Engine off of Gluster storage / off the Hyperconverged hosts into the Synology Virtual Machine manager. Is it possible to migrate the existing oVirt Engine (put the cluster into Global Maintenance Mode, shutdown oVirt, export to VDI or something, and then import into Synology's virtualization)? Or would it be better for me to install a completely new Engine, and then somehow migrate all of the VMs from the old engine into the new engine? Thanks, David Sent with Proton Mail secure email.

2 2

VDSM command GetStoragePoolInfoVDS failed:
by parallax 19 Aug '22

19 Aug '22

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 1

ISO images permissions
by Staniforth, Paul 19 Aug '22

19 Aug '22

Hello, When putting ISOs on the standard data storage domain what permissions can I give them so they are only available to selected groups or users? Thanks, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0