Multiple dependencies unresolved
by Andrea Chierici
Dear all,
lately the engine started notifying me about some "errors":
"Failed to check for available updates on host XYZ with message 'Task
Ensure Python3 is installed for CentOS/RHEL8 hosts failed to execute.
Please check logs for more details"
I do understand this is not something that can impact my cluster
stability, since it's only a matter of checking updates, anyway it
annoys me a lot.
I checked the logs and apparently the issue is related to some repos
that are missing/unresolved.
Right now on my hosts I have these repos:
ovirt-release44-4.4.8.3-1.el8.noarch
epel-release-8-13.el8.noarch
centos-stream-release-8.6-1.el8.noarch
puppet5-release-5.0.0-5.el8.noarch
The problems come from:
Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8':
Cannot prepare internal mirrorlist: No URLs in mirrorlist
Error: Failed to download metadata for repo 'ovirt-4.4-centos-opstools':
Cannot prepare internal mirrorlist: No URLs in mirrorlist
Error: Failed to download metadata for repo
'ovirt-4.4-openstack-victoria': Cannot download repomd.xml: Cannot
download repodata/repomd.xml: All mirrors were tried
If I disable these repos "yum update" can finish but then I get a large
number of unresolved dependencies and "problems":
Error:
Problem 1: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
requires ansible, but none of the providers can be installed
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.25-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.27-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.17-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.18-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.20-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.21-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.23-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.24-2.el8.noarch
- package ansible-2.9.27-2.el8.noarch conflicts with ansible-core >
2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
provided by ansible-2.9.27-2.el8.noarch
- cannot install the best update candidate for package
cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
- cannot install the best update candidate for package
ansible-2.9.25-1.el8.noarch
- package ansible-2.9.20-1.el8.noarch is filtered out by exclude
filtering
Problem 2: package fence-agents-ibm-powervs-4.2.1-84.el8.noarch
requires fence-agents-common = 4.2.1-84.el8, but none of the providers
can be installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- cannot install the best update candidate for package
fence-agents-ibm-powervs-4.2.1-77.el8.noarch
- cannot install the best update candidate for package
fence-agents-common-4.2.1-77.el8.noarch
Problem 3: cannot install both fence-agents-common-4.2.1-88.el8.noarch
and fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- package fence-agents-amt-ws-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can be
installed
- cannot install the best update candidate for package
fence-agents-ibm-vpc-4.2.1-77.el8.noarch
- cannot install the best update candidate for package
fence-agents-amt-ws-4.2.1-77.el8.noarch
Problem 4: problem with installed package
fence-agents-ibm-vpc-4.2.1-77.el8.noarch
- package fence-agents-ibm-vpc-4.2.1-77.el8.noarch requires
fence-agents-common = 4.2.1-77.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-78.el8.noarch requires
fence-agents-common = 4.2.1-78.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-82.el8.noarch requires
fence-agents-common = 4.2.1-82.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-83.el8.noarch requires
fence-agents-common = 4.2.1-83.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-77.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-78.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-82.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-83.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can be
installed
- cannot install the best update candidate for package
fence-agents-apc-4.2.1-77.el8.noarch
Problem 5: problem with installed package
fence-agents-ibm-powervs-4.2.1-77.el8.noarch
- package fence-agents-ibm-powervs-4.2.1-77.el8.noarch requires
fence-agents-common = 4.2.1-77.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-78.el8.noarch requires
fence-agents-common = 4.2.1-78.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-82.el8.noarch requires
fence-agents-common = 4.2.1-82.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-83.el8.noarch requires
fence-agents-common = 4.2.1-83.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-77.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-78.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-82.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-83.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-snmp-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can be
installed
- cannot install the best update candidate for package
fence-agents-apc-snmp-4.2.1-77.el8.noarch
My question is: since I am not willing to update anything right now, and
I just want to get rid of the stupid python3 error, should I disable
these repos, even if now I get some dep issues or the solution is another?
Any suggestion?
Thanks,
Andrea
--
Andrea Chierici - INFN-CNAF
Viale Berti Pichat 6/2, 40127 BOLOGNA
Office Tel: +39 051 2095463
SkypeID ataruz
--
2 years, 8 months
Does memory ballooning works if memory overcommit is disabled in the cluster
by sohail_akhter3＠hotmail.com
Hi All,
We have one ovirt 4.4 environment running. In Cluster Optimization settings we have checked "None - Disable memory overcommit" Option in Memory Optimization. But Memory Balloon check box option is enabled. My understanding is that Ballooning only works when memory overcommit is enabled. If it is true then this check box should be disabled when we are not overcommitting memory. Or Still memory ballooning works even if we disabled memory overcommit. According to below link ballooning works when memory overcommit is enabled.
https://lists.ovirt.org/pipermail/users/2017-October/084675.html
Please let me know if any further information is required.
Many thanks.
Regards
Sohail
2 years, 8 months
[ANN] oVirt Node 4.4.10.2 Async update
by Sandro Bonazzola
On March 3rd 2022 the oVirt project released an async update of oVirt Node
(4.4.10.2) delivering fixes for the following issues:
Bug 2057447 <https://bugzilla.redhat.com/show_bug.cgi?id=2057447> -
CVE-2022-24407 <https://access.redhat.com/security/cve/CVE-2022-24407>
cyrus-sasl: failure to properly escape SQL input allows an attacker to
execute arbitrary SQL commands [ovirt-4.4]
Bug 2055098 <https://bugzilla.redhat.com/show_bug.cgi?id=2055098> -
CVE-2022-22942 <https://access.redhat.com/security/cve/CVE-2022-22942>
kernel: failing usercopy allows for use-after-free exploitation [ovirt-4.4]
Bug 2047640 <https://bugzilla.redhat.com/show_bug.cgi?id=2047640> -
CVE-2021-0920 <https://access.redhat.com/security/cve/CVE-2021-0920>
kernel: Use After Free in unix_gc() which could result in a local privilege
escalation [ovirt-4.4]
Bug 2047630 <https://bugzilla.redhat.com/show_bug.cgi?id=2047630> -
CVE-2021-4154 <https://access.redhat.com/security/cve/CVE-2021-4154>
kernel: local privilege escalation by exploiting the fsconfig syscall
parameter leads to container breakout [ovirt-4.4]
Bug 2046005 <https://bugzilla.redhat.com/show_bug.cgi?id=2046005> -
CVE-2022-0330 <https://access.redhat.com/security/cve/CVE-2022-0330>
kernel: possible privileges escalation due to missing TLB flush [ovirt-4.4]
Bug 2043471 <https://bugzilla.redhat.com/show_bug.cgi?id=2043471> -
CVE-2021-45417 <https://access.redhat.com/security/cve/CVE-2021-45417>
aide: heap-based buffer overflow on outputs larger than B64_BUF [ovirt-4.4]
Several bug fixes and improvements from CentOS Stream.
Here’s the full list of changes:
ovirt-node-ng-4.4.10.1
ovirt-node-ng-4.4.10.2
NetworkManager 1.36.0-0.4.el8
1.36.0-1.el8
NetworkManager-config-server 1.36.0-0.4.el8
1.36.0-1.el8
NetworkManager-libnm 1.36.0-0.4.el8
1.36.0-1.el8
NetworkManager-ovs 1.36.0-0.4.el8
1.36.0-1.el8
NetworkManager-team 1.36.0-0.4.el8
1.36.0-1.el8
NetworkManager-tui 1.36.0-0.4.el8
1.36.0-1.el8
aide 0.16-14.el8
0.16-14.el8_5.1
alsa-lib 1.2.6.1-1.el8
1.2.6.1-3.el8
audispd-plugins 3.0.7-1.el8
3.0.7-2.el8
audit 3.0.7-1.el8
3.0.7-2.el8
audit-libs 3.0.7-1.el8
3.0.7-2.el8
autofs 5.1.4-77.el8
5.1.4-82.el8
bind-export-libs 9.11.36-2.el8
9.11.36-3.el8
bind-libs 9.11.36-2.el8
9.11.36-3.el8
bind-libs-lite 9.11.36-2.el8
9.11.36-3.el8
bind-license 9.11.36-2.el8
9.11.36-3.el8
bind-utils 9.11.36-2.el8
9.11.36-3.el8
blivet-data 3.4.0-8.el8
3.4.0-9.el8
cairo 1.15.12-3.el8
1.15.12-6.el8
cockpit 261-1.el8
264-1.el8
cockpit-bridge 261-1.el8
264-1.el8
cockpit-storaged 261-1.el8
264-1.el8
cockpit-system 261-1.el8
264-1.el8
cockpit-ws 261-1.el8
264-1.el8
cryptsetup 2.3.3-4.el8
2.3.7-2.el8
cryptsetup-libs 2.3.3-4.el8
2.3.7-2.el8
cups-libs 2.2.6-42.el8
2.2.6-44.el8
cyrus-sasl 2.1.27-5.el8
2.1.27-6.el8_5
cyrus-sasl-gssapi 2.1.27-5.el8
2.1.27-6.el8_5
cyrus-sasl-lib 2.1.27-5.el8
2.1.27-6.el8_5
cyrus-sasl-scram 2.1.27-5.el8
2.1.27-6.el8_5
device-mapper-multipath 0.8.4-21.el8
0.8.4-22.el8
device-mapper-multipath-libs 0.8.4-21.el8
0.8.4-22.el8
dnf 4.7.0-5.el8
4.7.0-7.el8
dnf-data 4.7.0-5.el8
4.7.0-7.el8
dnf-plugins-core 4.0.21-8.el8
4.0.21-10.el8
dnsmasq 2.79-20.el8
2.79-21.el8
dracut 049-191.git20210920.el8
049-201.git20220131.el8
dracut-config-generic 049-191.git20210920.el8
049-201.git20220131.el8
dracut-live 049-191.git20210920.el8
049-201.git20220131.el8
dracut-network 049-191.git20210920.el8
049-201.git20220131.el8
dracut-squash 049-191.git20210920.el8
049-201.git20220131.el8
e2fsprogs 1.45.6-2.el8
1.45.6-3.el8
e2fsprogs-libs 1.45.6-2.el8
1.45.6-3.el8
edk2-ovmf 20210527gite1999b264f1f-3.el8
20220126gitbb1bba3d77-1.el8.test
expat 2.2.5-4.el8
2.2.5-5.el8
fence-agents-all 4.2.1-85.el8
4.2.1-88.el8
fence-agents-amt-ws 4.2.1-85.el8
4.2.1-88.el8
fence-agents-apc 4.2.1-85.el8
4.2.1-88.el8
fence-agents-apc-snmp 4.2.1-85.el8
4.2.1-88.el8
fence-agents-bladecenter 4.2.1-85.el8
4.2.1-88.el8
fence-agents-brocade 4.2.1-85.el8
4.2.1-88.el8
fence-agents-cisco-mds 4.2.1-85.el8
4.2.1-88.el8
fence-agents-cisco-ucs 4.2.1-85.el8
4.2.1-88.el8
fence-agents-common 4.2.1-85.el8
4.2.1-88.el8
fence-agents-compute 4.2.1-85.el8
4.2.1-88.el8
fence-agents-drac5 4.2.1-85.el8
4.2.1-88.el8
fence-agents-eaton-snmp 4.2.1-85.el8
4.2.1-88.el8
fence-agents-emerson 4.2.1-85.el8
4.2.1-88.el8
fence-agents-eps 4.2.1-85.el8
4.2.1-88.el8
fence-agents-heuristics-ping 4.2.1-85.el8
4.2.1-88.el8
fence-agents-hpblade 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ibmblade 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ifmib 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ilo-moonshot 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ilo-mp 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ilo-ssh 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ilo2 4.2.1-85.el8
4.2.1-88.el8
fence-agents-intelmodular 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ipdu 4.2.1-85.el8
4.2.1-88.el8
fence-agents-ipmilan 4.2.1-85.el8
4.2.1-88.el8
fence-agents-kdump 4.2.1-85.el8
4.2.1-88.el8
fence-agents-mpath 4.2.1-85.el8
4.2.1-88.el8
fence-agents-redfish 4.2.1-85.el8
4.2.1-88.el8
fence-agents-rhevm 4.2.1-85.el8
4.2.1-88.el8
fence-agents-rsa 4.2.1-85.el8
4.2.1-88.el8
fence-agents-rsb 4.2.1-85.el8
4.2.1-88.el8
fence-agents-sbd 4.2.1-85.el8
4.2.1-88.el8
fence-agents-scsi 4.2.1-85.el8
4.2.1-88.el8
fence-agents-vmware-rest 4.2.1-85.el8
4.2.1-88.el8
fence-agents-vmware-soap 4.2.1-85.el8
4.2.1-88.el8
fence-agents-wti 4.2.1-85.el8
4.2.1-88.el8
firewalld 0.9.3-11.el8
0.9.3-13.el8
firewalld-filesystem 0.9.3-11.el8
0.9.3-13.el8
fuse 2.9.7-12.el8
2.9.7-15.el8
fuse-common 3.2.1-12.el8
3.3.0-15.el8
fuse-libs 2.9.7-12.el8
2.9.7-15.el8
fuse3-libs 3.2.1-12.el8
3.3.0-15.el8
gawk 4.2.1-2.el8
4.2.1-4.el8
glibc 2.28-184.el8
2.28-189.el8
glibc-common 2.28-184.el8
2.28-189.el8
glibc-langpack-en 2.28-184.el8
2.28-189.el8
gpgme 1.13.1-9.el8
1.13.1-11.el8
hwdata 0.314-8.11.el8
0.314-8.12.el8
info 6.5-6.el8
6.5-7.el8_5
initscripts 10.00.15-1.el8
10.00.17-1.el8
iotop 0.6-16.el8
0.6-17.el8
iproute 5.15.0-2.el8
5.15.0-3.el8
iproute-tc 5.15.0-2.el8
5.15.0-3.el8
iputils 20180629-8.el8
20180629-9.el8
iwl100-firmware 39.31.5.1-105.el8.1
39.31.5.1-106.el8.1
iwl1000-firmware 39.31.5.1-105.el8.1
39.31.5.1-106.el8.1
iwl105-firmware 18.168.6.1-105.el8.1
18.168.6.1-106.el8.1
iwl135-firmware 18.168.6.1-105.el8.1
18.168.6.1-106.el8.1
iwl2000-firmware 18.168.6.1-105.el8.1
18.168.6.1-106.el8.1
iwl2030-firmware 18.168.6.1-105.el8.1
18.168.6.1-106.el8.1
iwl3160-firmware 25.30.13.0-105.el8.1
25.30.13.0-106.el8.1
iwl5000-firmware 8.83.5.1_1-105.el8.1
8.83.5.1_1-106.el8.1
iwl5150-firmware 8.24.2.2-105.el8.1
8.24.2.2-106.el8.1
iwl6000-firmware 9.221.4.1-105.el8.1
9.221.4.1-106.el8.1
iwl6000g2a-firmware 18.168.6.1-105.el8.1
18.168.6.1-106.el8.1
iwl6050-firmware 41.28.5.1-105.el8.1
41.28.5.1-106.el8.1
iwl7260-firmware 25.30.13.0-105.el8.1
25.30.13.0-106.el8.1
kernel 4.18.0-358.el8
4.18.0-365.el8
kernel-core 4.18.0-358.el8
4.18.0-365.el8
kernel-modules 4.18.0-358.el8
4.18.0-365.el8
kernel-tools 4.18.0-358.el8
4.18.0-365.el8
kernel-tools-libs 4.18.0-358.el8
4.18.0-365.el8
kmod-kvdo 6.2.6.3-82.el8
6.2.6.14-83.el8
kpartx 0.8.4-21.el8
0.8.4-22.el8
libblkid 2.32.1-32.el8
2.32.1-34.el8
libcap 2.26-5.el8
2.48-2.el8
libcom_err 1.45.6-2.el8
1.45.6-3.el8
libdnf 0.63.0-5.el8
0.63.0-7.el8
libfdisk 2.32.1-32.el8
2.32.1-34.el8
libfdt
1.6.0-1.el8
libguestfs
1.44.0-4.module_el8.6.0+983+a7505f3f
1.44.0-5.module_el8.6.0+1087+b42c8331
libguestfs-appliance
1.44.0-4.module_el8.6.0+983+a7505f3f
1.44.0-5.module_el8.6.0+1087+b42c8331
libguestfs-tools-c
1.44.0-4.module_el8.6.0+983+a7505f3f
1.44.0-5.module_el8.6.0+1087+b42c8331
libmount 2.32.1-32.el8
2.32.1-34.el8
libnfsidmap 2.3.3-47.el8
2.3.3-50.el8
libosinfo 1.9.0-2.el8
1.9.0-3.el8
libsemanage 2.9-6.el8
2.9-8.el8
libsmartcols 2.32.1-32.el8
2.32.1-34.el8
libss 1.45.6-2.el8
1.45.6-3.el8
libtpms
0.7.4-6.20201106git2452a24dab.module_el8.6.0+983+a7505f3f
0.9.1-0.20211126git1ff6fe1f43.module_el8.6.0+1087+b42c8331
libudisks2 2.9.0-7.el8
2.9.0-9.el8
libuuid 2.32.1-32.el8
2.32.1-34.el8
libvirt
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-client
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-config-network
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-config-nwfilter
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-interface
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-network
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-nodedev
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-nwfilter
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-qemu
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-secret
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-core
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-disk
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-gluster
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-iscsi
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
Libvirt-daemon-driver-storage-iscsi-direct
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-logical
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-mpath
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-rbd
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-driver-storage-scsi
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-daemon-kvm
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-libs
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libvirt-lock-sanlock
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-2.module_el8.6.0+1087+b42c8331
libwbclient 4.15.4-0.el8
4.15.5-4.el8
libxml2 2.9.7-11.el8
2.9.7-13.el8
linux-firmware 20211119-105.gitf5d51956.el8
20220210-106.git6342082c.el8
mdadm 4.2-rc3.el8
4.2-2.el8
microcode_ctl 20210608-1.el8
20220207-1.el8
nbdkit
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-basic-filters
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-basic-plugins
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-curl-plugin
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-python-plugin
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-server
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-ssh-plugin
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
nbdkit-vddk-plugin
1.24.0-3.module_el8.6.0+983+a7505f3f
1.24.0-4.module_el8.6.0+1087+b42c8331
net-snmp 5.8-24.el8
5.8-25.el8
net-snmp-agent-libs 5.8-24.el8
5.8-25.el8
net-snmp-libs 5.8-24.el8
5.8-25.el8
net-snmp-utils 5.8-24.el8
5.8-25.el8
nfs-utils 2.3.3-47.el8
2.3.3-50.el8
nftables 0.9.3-24.el8
0.9.3-25.el8
nmstate 1.2.1-0.2.alpha2.el8
1.2.1-1.el8
nmstate-plugin-ovsdb 1.2.1-0.2.alpha2.el8
1.2.1-1.el8
openscap 1.3.5-10.el8
1.3.6-3.el8
openscap-scanner 1.3.5-10.el8
1.3.6-3.el8
ovirt-node-ng-image-update-placeholder 4.4.10.1-1.el8
4.4.10.2-1.el8
ovirt-release-host-node 4.4.10.1-1.el8
4.4.10.2-1.el8
ovirt-release44 4.4.10.1-1.el8
4.4.10.2-1.el8
pam 1.3.1-15.el8
1.3.1-16.el8
passwd 0.80-3.el8
0.80-4.el8
pixman 0.38.4-1.el8
0.38.4-2.el8
plymouth 0.9.4-10.20200615git1e36e30.el8
0.9.4-11.20200615git1e36e30.el8
plymouth-core-libs 0.9.4-10.20200615git1e36e30.el8
0.9.4-11.20200615git1e36e30.el8
plymouth-scripts 0.9.4-10.20200615git1e36e30.el8
0.9.4-11.20200615git1e36e30.el8
policycoreutils 2.9-18.el8
2.9-19.el8
policycoreutils-python-utils 2.9-18.el8
2.9-19.el8
postfix 3.5.8-3.el8
3.5.8-4.el8
python-oslo-utils-lang 4.6.0-2.el8
4.6.1-1.el8
python3-audit 3.0.7-1.el8
3.0.7-2.el8
python3-bind 9.11.36-2.el8
9.11.36-3.el8
python3-blivet 3.4.0-8.el8
3.4.0-9.el8
python3-configobj
5.0.6-11.el8
python3-dnf 4.7.0-5.el8
4.7.0-7.el8
python3-dnf-plugin-versionlock 4.0.21-8.el8
4.0.21-10.el8
python3-dnf-plugins-core 4.0.21-8.el8
4.0.21-10.el8
python3-ethtool 0.14-4.el8
0.14-5.el8
python3-firewall 0.9.3-11.el8
0.9.3-13.el8
python3-gpg 1.13.1-9.el8
1.13.1-11.el8
python3-hawkey 0.63.0-5.el8
0.63.0-7.el8
python3-libdnf 0.63.0-5.el8
0.63.0-7.el8
python3-libnmstate 1.2.1-0.2.alpha2.el8
1.2.1-1.el8
python3-libsemanage 2.9-6.el8
2.9-8.el8
python3-libvirt
7.10.0-1.module_el8.6.0+1046+bd8eec5e
8.0.0-1.module_el8.6.0+1087+b42c8331
python3-libxml2 2.9.7-11.el8
2.9.7-13.el8
python3-nftables 0.9.3-24.el8
0.9.3-25.el8
python3-oslo-service 2.4.0-2.el8
2.4.1-1.el8
python3-oslo-utils 4.6.0-2.el8
4.6.1-1.el8
python3-perf 4.18.0-358.el8
4.18.0-365.el8
python3-policycoreutils 2.9-18.el8
2.9-19.el8
python3-rpm 4.14.3-21.el8
4.14.3-22.el8
qemu-guest-agent
6.1.0-5.module_el8.6.0+1040+0ae94936
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-img 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-block-curl 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-block-gluster 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-block-iscsi 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-block-rbd 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-block-ssh 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-common 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-core 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-docs 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-hw-usbredir 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-ui-opengl 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
qemu-kvm-ui-spice 6.0.0-33.el8s
6.2.0-5.module_el8.6.0+1087+b42c8331
radvd
2.17-15.el8
rpm 4.14.3-21.el8
4.14.3-22.el8
rpm-build-libs 4.14.3-21.el8
4.14.3-22.el8
rpm-libs 4.14.3-21.el8
4.14.3-22.el8
rpm-plugin-selinux 4.14.3-21.el8
4.14.3-22.el8
samba-client-libs 4.15.4-0.el8
4.15.5-4.el8
samba-common 4.15.4-0.el8
4.15.5-4.el8
samba-common-libs 4.15.4-0.el8
4.15.5-4.el8
scap-security-guide 0.1.59-1.el8
0.1.60-7.el8
seabios-bin
1.14.0-1.module_el8.6.0+983+a7505f3f
1.15.0-1.module_el8.6.0+1087+b42c8331
seavgabios-bin
1.14.0-1.module_el8.6.0+983+a7505f3f
1.15.0-1.module_el8.6.0+1087+b42c8331
selinux-policy 3.14.3-89.el8
3.14.3-93.el8
selinux-policy-targeted 3.14.3-89.el8
3.14.3-93.el8
sos 4.2-13.el8
4.2-15.el8
swtpm
0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f
0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331
swtpm-libs
0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f
0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331
swtpm-tools
0.6.0-2.20210607gitea627b3.module_el8.6.0+983+a7505f3f
0.7.0-1.20211109gitb79fd91.module_el8.6.0+1087+b42c8331
systemd 239-56.el8
239-58.el8
systemd-container 239-56.el8
239-58.el8
systemd-libs 239-56.el8
239-58.el8
systemd-pam 239-56.el8
239-58.el8
systemd-udev 239-56.el8
239-58.el8
tuned 2.16.0-1.el8
2.18.0-2.el8
udisks2 2.9.0-7.el8
2.9.0-9.el8
util-linux 2.32.1-32.el8
2.32.1-34.el8
vdo 6.2.6.7-14.el8
6.2.6.14-14.el8
vim-minimal 8.0.1763-16.el8_5.4
8.0.1763-16.el8_5.12
yum 4.7.0-5.el8
4.7.0-7.el8
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
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, 8 months
CPU compatibility issues
by Adam Xu
Dear ovirt community,
my cluster cpu type is "Intel Skylake Server Family" . I have 3 hosts
with "Xeon Silver 4114" and 1 host with "Xeon Gold 5118", everything
works ok.
I try to add a new host with "Xeon Silver 4314" now. But it failed.
error log:
Host ovirt7 moved to Non-Operational state as host does not meet the
cluster's minimum CPU level. Missing CPU features : model_Skylake-Server.
How can I add the new host to cluster? Thanks.
2 years, 8 months
Unable to access internet after installing ovirt 4.4.10
by louisb＠ameritech.net
I recently installed ovirt on my server that has four/4 network adapters. I recently installed ovirt on the server successfully; however; after the installation I've not been able to access the internet from the server. I have cockpit installed and I see that "ovirtmgmt" has taken control of the first network adapter. I three/3 remaining adapters left so I liked to just access the internet using one or all of the remaining network adapters. I can see using cockpit that there is a little receiving traffic taken place but no sending traffic.
How do I get internet traffic going on one of the remaining network adapters?
Could this be firewall issue?
Thanks
2 years, 8 months
I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error
by Gangi Reddy
I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error:
booting from dvd/cd...
boot failed: could not read from cdrom (code 0005)
no bootable device
Forum Solution:
Find the location of the ISO image in the storage domain (search for the UUID in the file system) and re-copy the ISO over the top of the file.
Just be 100% sure it's the ISO and not a VM disk (reference modification time, size etc). Once you replace the "uploaded" file with the ISO
directly, everything works as expected.
Kindly share detail steps on how to upload ISO image directly to Storage domain with UUID
2 years, 8 months
Correct method to upload ISOs
by nroach44＠nroach44.id.au
As ISO domains are deprecated, what's the correct/modern procedure to upload ISOs to install / boot from?
When I upload them to a data domain, they get converted into QCOW2 images (as confirmed by qemu-img info), but attached like ISOs to the qemu process. This means the VMs won't boot, until I manually overwrite the disk image on the datastore with the ISO directly (which works fine).
My cluster started on 4.4 just after release, and is fully updated, if that changes things.
Cheers,
Nathaniel
2 years, 8 months
VDSM command SetVolumeDescription failed every hours
by dvx.mellin＠gmail.com
Hi everyone,
My configuration is 3 oVirt servers (CentOS Linux release 8.4.2105) with GlusterFS (glusterfs 8.6). Everything works well, but I have these errors appear every hours in the webgui of engine :
WARN : Failed to update VMs/Templates OVF data for Storage Domain vmstore in Data Center Default.
WARN : Failed to update OVF disks c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain vmstore).
ERR : VDSM command SetVolumeDescriptionVDS failed: Could not acquire resource. Probably resource factory threw an exception.: ()
I guess it's related to these 4 messages in my engine.log :
./ovirt-engine/engine.log:2022-03-02 14:32:46,368+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] START, SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='a902d630-3674-11ec-8b5d-00163e388a46', ignoreFailoverLimit='false', storageDomainId='85b0066a-9dbb-4dfa-8359-5bf494c89c18', imageGroupId='c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7', imageId='cde4b56e-645d-4f18-8eb1-a0ffb0c70599'}), log id: 41fdb7e1
./ovirt-engine/engine.log:2022-03-02 14:32:46,368+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] ++ imageGroupGUID=c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7
./ovirt-engine/engine.log:2022-03-02 14:32:46,408+01 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] Command 'SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='a902d630-3674-11ec-8b5d-00163e388a46', ignoreFailoverLimit='false', storageDomainId='85b0066a-9dbb-4dfa-8359-5bf494c89c18', imageGroupId='c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7', imageId='cde4b56e-645d-4f18-8eb1-a0ffb0c70599'})' execution failed: IRSGenericException: IRSErrorException: Failed to SetVolumeDescriptionVDS, error = Could not acquire resource. Probably resource factory threw an exception.: (), code = 855
./ovirt-engine/engine.log:2022-03-02 14:32:46,408+01 WARN [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] failed to update domain '85b0066a-9dbb-4dfa-8359-5bf494c89c18' ovf store disk 'c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7'
./ovirt-engine/engine.log:2022-03-02 14:32:46,416+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [7f7eee05] EVENT_ID: UPDATE_FOR_OVF_STORES_FAILED(1,016), Failed to update OVF disks c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain vmstore).
The disk which has the ID c2886e02-d0ea-4ff4-8f68-bf3e2ec684b7 is an OVF_STORE on one of my domains.
Thanks for any help or advice and let me know if you need more informations.
Best regards,
Michael
2 years, 8 months
Deleting Snapshot failed
by Jonathan Baecker
Hello everybody,
last night my backup script was not able to finish the backup from a VM
in the last step of deleting the snapshot. And now I also can not delete
this snapshot by hand, the message says:
VDSM onode2 command MergeVDS failed: Drive image file could not be
found: {'driveSpec': {'poolID':
'c9baa5d4-3543-11eb-9c0c-00163e33f845', 'volumeID':
'024e1844-c19b-40d8-a2ac-cb4ea6ec34e6', 'imageID':
'ad23c0db-1838-4f1f-811b-2b213d3a11cd', 'domainID':
'3cf83851-1cc8-4f97-8960-08a60b9e25db'}, 'job':
'96c7003f-e111-4270-b922-d9b215aaaea2', 'reason': 'Cannot find drive'}
The full log you found in the attachment.
Any idea?
Best regard
Jonathan
2 years, 8 months
How to create a new Direct LUN with the API
by michael.wagenknecht＠continentale.de
Hi,
I tried to create a new Fibre Channel Direct LUN with the API. But it doesn't work. My command is:
curl -s \
--cacert '/etc/pki/ovirt-engine/ca.pem' \
--request POST \
--header 'Version: 4' \
--header 'Accept: application/xml' \
--user 'admin@internal:XXXXXXXXXX' \
--data '
<disk>
<alias>DX600RZ2_OLVM_Test</alias>
<name>DX600RZ2_OLVM_Test</name>
<lun_storage>
<type>fcp</type>
<logical_units>
<logical_unit id="3600000e00d2a0000002a0d15034d0000">
</logical_unit>
</logical_units>
</lun_storage>
</disk>
' \
https://olvmmanager/ovirt-engine/api/disks
I think there are parameter missing. But I can't find a working example.
Please help.
Best Regards,
Michael
2 years, 8 months
