[ovirt-users] Re: Error during deployment of ovirt-engine
try to downgrade ansible-core to 2.12, or the last version requiring python 3.8. On Fri, Oct 14, 2022 at 9:29 AM Roberto Ramirez wrote: > Can you tell me which version of ansible-core you install > I am having the same issue > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be > up] > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/GVJMM6U7B5WCK43DY66TXBXF4SREPBFG/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/2MTMJN3ERNDCRSG77ULSUWMO4G4TMUPF/
[ovirt-users] Re: OVS Task Error when Add EL Host
Hi, I'm having the exact same problem doing a fresh install of RHEL and setting
up (command line: hosted-engine --deploy --4) the ovirt-engine. I assume it
must have been some kind of update to the base OS - (in my case RHEL 8.6
(Ootpa), because i have done previous installations with this exact OS and
centos-release-ovirt45 repos without having an issues. The failed task is:
TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]
and, on the hosted-engine log:
/var/log/ovirt-hosted-engine-setup/engine-logs-2022-10-11T18:43:29Z/log/ovirt-engine/host-deploy
I see:
"stdout" : "fatal: [x]: FAILED! => {\"msg\": \"The conditional check
'cluster_switch == \\\"ovs\\\" or (ovn_central is defined and ovn_central |
ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be
installed on the ansible controller\\n\\nThe error appears to be in
'/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml':
line 3, column 5, but may\\nbe elsewhere in the file depending on the exact
syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n -
name: Install ovs\\n^ here\\n\"}",
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/UPOI4AGM3XRFQLBDYA4S2Y3CVHGUHPKN/
[ovirt-users] Re: OVS Task Error when Add EL Host
Hello, I am facing the same issue on multiple Operating Systems (Rocky Linux 8,9, oVirt Node 4.5.2). Did you maybe find a solution for this problem? All best, Aleksandar ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/BYIEQS4U7ZURLCHZFK2PHKLB7W265SEU/
[ovirt-users] Re: Error during deployment of ovirt-engine
Can you tell me which version of ansible-core you install I am having the same issue [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/GVJMM6U7B5WCK43DY66TXBXF4SREPBFG/
[ovirt-users] Invalid GPG keys for rhel9 package
Hi, OS used is AlmaLinux 9.0. I tried to install the appliance with "hosted-engine", but unfortunately it complained about invalid GPG keys. The last 2 lines of the Key block seem strange. How can I fix this? I get the following message: [root@master ~]# yum install ovirt-engine-appliance Last metadata expiration check: 3:08:01 ago on Wed 12 Oct 2022 05:38:43 PM EDT. Dependencies resolved. Package ArchitectureVersion Repository Size Installing: ovirt-engine-appliance x86_64 4.5-20220419160254.1.el9 ovirt-45-upstream 1.6 G Transaction Summary Install 1 Package Total download size: 1.6 G Installed size: 1.6 G Is this ok [y/N]: y Downloading Packages: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64.rpm 17 MB/s | 1.6 GB 01:36 Total 15 MB/s | 1.6 GB 01:45 oVirt upstream for CentOS Stream 9 - oVirt 4.5 682 kB/s | 2.9 kB 00:00 Importing GPG key 0xFE590CB7: Userid : "oVirt " Fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 Is this ok [y/N]: y Key import failed (code 2). Failing package is: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'yum clean packages'. Error: GPG check FAILED Here is a part of the GPG key: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2.0.22 (GNU/Linux) mQENBFM3+3YBCADTLqGw5hI0whRPeN0hSjpaZ2yNNtVzgqj8/EFQ9IfR7GasHz/4 kkT3cpKXZygo0AIVEe5dkrcYXF+9C6bowiuGZG+9G6j8MXneunRv7S0mv1mnx7MW [snip] FFm7Fr9czelRSW+NCUvvtKKFG612VvwSSU/u8DarGdLnrKxJ5ito7Pd+n3ZB1YVy sfxDvnYN =SxBW -END PGP PUBLIC KEY BLOCK- ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/FJPII2DUGFRH3UA7GJVR7EEVULAIX3V4/
[ovirt-users] Upgrading from ovirt 4.5 rhel8 to rhel9
Hi, my setup is 3 physical servers with glusterfs. One of them had ovirt-engine. Usually my upgrade was (from 4.2, 4.3, 4.4, 4.5): engine-backup reinstall OS yum install ovirt-engine engine-backup: restore engine-setup. My main server was RHEL 8.6, ovirt 4.52. I did the backup, install AlmaLinux 9. But the package doesn't exist anymore with rhel9. Is the engine on bare-metal still available with rhel9? If not, is it possible to install the appliance with the saved config file with a different hostname and IP for the appliance? Thanks ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/7JMBI5FGQO4JT5BSALAURGFJXVDDPPQJ/
[ovirt-users] There is no glusterfs management dashboard in the Cockpit background
I have many data centers, the first data center contains the engine, the glusterfs management dashboard can be seen in the Cockpit background, but the glusterfs management dashboard cannot be seen in the second data center, Create the second data center step: I create a data center in the engine, then set up a glusterfs cluster in the Cockpit background, and finally mount the glusterfs volume in the engine. Is there something wrong with the way I add it? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/F6D73YP6RSN3O5MYG3MLQR27ILDBSVTJ/
[ovirt-users] Re: OVS Task Error when Add EL Host
Actually, there are some strange stuff going on a newly deployed HE: [root@poc ~]# yum update Failed to set locale, defaulting to C.UTF-8 Last metadata expiration check: 0:34:52 ago on Fri Oct 14 01:09:57 2022. Error: Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch - cannot install the best update candidate for package openvswitch2.15-2.15.0-119.el8s.x86_64 Problem 2: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06
[ovirt-users] Re: OVS Task Error when Add EL Host
I have a same issue with an installation today (oVirt 4.5.2, based on Centos Stream 8) ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/NRDJIOQPHRHFDXWJX6NA62SLXEPDTVYI/
[ovirt-users] Re: Engine's certification is about to expire at .... Please renew the engine's certification.
Hello, That means the engine certificate signed by the internal engine CA is about to expire. (It's used to communicate with VDSM and VNC connections.) The engine should auto renew it during the next upgrade. If you have downtime, you can renew it manually by rerunning engine-setup on the engine host. The custom cert you give to apache is not affected by this renewal, but the engine will start having issues if it's internal cert isn't renewed. Do keep in mind that some users have reported having issues when renewing this cert, (engine-setup not actually renewing it properly, hosts loosing connectivity, etc.) so I would plan on there being a complete service interruption, e.g. all VMs inaccessible / down, during the renewal process. (Maybe do it over a weekend.) -Patrick Hibbs On Thu, 2022-10-13 at 11:14 +0100, nico...@devels.es wrote: > Hi, > > I'm running oVirt 4.4 and recently I got a message in the events list > like this: > > Engine's certification is about to expire at 2022-10-30. Please > renew > the engine's certification. > > What does that exactly mean? And how can it be renewed? > > I'm using a custom TLS certificate both for web access and websocket > proxy. Does it need to be renewed anyways? > > Thanks. > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/Y6VVJOL47YPYGNMXXWUK24F752PRKMLV/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SK4HD755QPUFVXOWPIJ56NMM5F65GP6N/
[ovirt-users] Disks in "Finalizing" state on Web Inteface
Hi! I have few vm-s that have disk status in "Finalizing" This VMs are working normally, but on web interface status is always "Finalizing" and progress bar is not moving. (It's in this state for days now) I can create snapshots and backups of them without problems and everything works ok. Is there any way that I can check why are this disks in that state? Regards, ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/JKILO2R3PR35PCEMJP423WO3PLJVHYKS/
[ovirt-users] Re: Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4.
Nevermind. Fixed it updating the database directly: UPDATE vm_static SET custom_compatibility_version = '4.4' WHERE custom_compatibility_version = '4.3'; Regards. El 2022-10-13 11:55, nico...@devels.es escribió: Hi, I'm running oVirt 4.4 and recently I changed the Data Center compatibility version from 4.3 to 4.4. Now turns out that some Pools are unable to restart machines, returning this error: Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4. I cannot edit manually the custom compatibility version of VMs, as pools won't allow that. Is there any manual way to fix it? I tried to do it via Python SDK but it doesn't seem to work... vm = vms_serv.list(name='X')[0] ver = vm.custom_compatibility_version ver.minor = 4 vm.custom_compatibility_version = ver vmsv = sys_serv.vms_service().vm_service(id=vm.id) vmsv.upfate(vm=vm) It doesn't seem to do any difference, though. Any help is really appreciated, as many our users can't use theis VMs. Thanks. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SWU7PYWUSTKHLV427MXW43Y63S6QBEYM/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/2KJAL37OQUVS6KBRXNYLWV45PGLWEOYQ/
[ovirt-users] Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4.
Hi, I'm running oVirt 4.4 and recently I changed the Data Center compatibility version from 4.3 to 4.4. Now turns out that some Pools are unable to restart machines, returning this error: Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4. I cannot edit manually the custom compatibility version of VMs, as pools won't allow that. Is there any manual way to fix it? I tried to do it via Python SDK but it doesn't seem to work... vm = vms_serv.list(name='X')[0] ver = vm.custom_compatibility_version ver.minor = 4 vm.custom_compatibility_version = ver vmsv = sys_serv.vms_service().vm_service(id=vm.id) vmsv.upfate(vm=vm) It doesn't seem to do any difference, though. Any help is really appreciated, as many our users can't use theis VMs. Thanks. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SWU7PYWUSTKHLV427MXW43Y63S6QBEYM/
[ovirt-users] Engine's certification is about to expire at .... Please renew the engine's certification.
Hi, I'm running oVirt 4.4 and recently I got a message in the events list like this: Engine's certification is about to expire at 2022-10-30. Please renew the engine's certification. What does that exactly mean? And how can it be renewed? I'm using a custom TLS certificate both for web access and websocket proxy. Does it need to be renewed anyways? Thanks. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/Y6VVJOL47YPYGNMXXWUK24F752PRKMLV/
[ovirt-users] Ovirt support on el9
Hello, is there a plan for an official el9 support ? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/QMCI7TA2VH57BFQZBHOUDTXDUQMJSMKU/
