oVirt Node 4.5.3.1 Async update
by Sandro Bonazzola
oVirt Node 4.5.3.1 Async update
On October 20th 2022 the oVirt project released an async update of oVirt
Node (4.5.3.1) delivering a fix for OVS/OVN package conflict issue.
The update is already available on resources.ovirt.org and should land on
oVirt mirrors within 24 hours.
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D PERFORMANCE & SCALE
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.*
1 year, 6 months
Re: Users Digest, Vol 133, Issue 36
by David Johnson
> We can try this at our next maintenance window, probably in a week or so
> From: Lev Veyde <lveyde(a)redhat.com>
> To: Brett Maton <matonb(a)ltresources.co.uk>
> Cc: "mmoon(a)maxistechnology.com" <mmoon(a)maxistechnology.com>, "
> users(a)ovirt.org" <users(a)ovirt.org>
> Bcc:
> Date: Wed, 19 Oct 2022 17:36:59 +0300
> Subject: [ovirt-users] Re: Ovirt host update bug
> Hi,
>
> We built a new centos-release-ovirt package that supposed to fix that
> issue (on non manually fixed machine):
>
> https://cbs.centos.org/kojifiles/packages/centos-release-ovirt45/8.7/3.el...
>
> Could somebody please test that it indeed fixes the issue?
>
> Thanks in advance,
>
> On Wed, Oct 19, 2022 at 2:27 PM Brett Maton <matonb(a)ltresources.co.uk>
> wrote:
>
>> Thanks Ales,
>>
>> That fixed it for me, I don't think *rdo-ovn-central* is mentioned in link
>> but that was the final missing exclude for me.
>>
>> Regards,
>> Brett
>>
>> ------------------------------
>> *From:* Ales Musil <amusil(a)redhat.com>
>> *Sent:* 19 October 2022 11:50
>> *To:* Brett Maton <matonb(a)ltresources.co.uk>
>> *Cc:* Lev Veyde <lveyde(a)redhat.com>; mmoon(a)maxistechnology.com <
>> mmoon(a)maxistechnology.com>; users(a)ovirt.org <users(a)ovirt.org>
>> *Subject:* Re: [ovirt-users] Re: Ovirt host update bug
>>
>> Hi,
>>
>> you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and "
>> rdo-ovn-central" in the excluded.
>> See
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT...
>>
>> Best regards,
>> Ales
>>
>> On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk>
>> wrote:
>>
>> I'm seeing the same error
>>
>> Repo config:
>>
>> # grep 'ovirt-45-centos-stream-openstack-yoga'
>> /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15
>>
>> [ovirt-45-centos-stream-openstack-yoga]
>> name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository
>> # baseurl=
>> http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/
>> mirrorlist=
>> http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-o...
>> gpgcheck=1
>> gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud
>> enabled=1
>> module_hotfixes=1
>> exclude=
>> # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on
>> oVirt side
>> ansible
>> ansible-test
>> * rdo-openvswitch*
>> * rdo-ovn*
>>
>>
>> Update attempt:
>>
>> # yum clean all
>> 187 files removed
>>
>> # dnf update
>> CentOS-8-stream - Ceph Pacific
>> 781 kB/s | 456 kB 00:00
>> CentOS-8-stream - Gluster 10
>> 175 kB/s | 40 kB 00:00
>> CentOS-8 - NFV OpenvSwitch
>> 364 kB/s | 168 kB 00:00
>> CentOS-OpsTools - collectd
>> 169 kB/s | 41 kB 00:00
>> CentOS Stream 8 - AppStream
>> 24 MB/s | 25 MB 00:01
>> CentOS Stream 8 - BaseOS
>> 23 MB/s | 25 MB 00:01
>> CentOS Stream 8 - Extras
>> 39 kB/s | 18 kB 00:00
>> CentOS Stream 8 - Extras common packages
>> 24 kB/s | 4.9 kB 00:00
>> CentOS Stream 8 - PowerTools
>> 9.7 MB/s | 5.1 MB 00:00
>> CentOS Stream 8 - oVirt 4.5
>> 4.1 MB/s | 1.2 MB 00:00
>> CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository
>> 3.4 MB/s | 2.2 MB 00:00
>> oVirt upstream for CentOS Stream 8 - oVirt 4.5
>> 47 kB/s | 408 kB 00:08
>> Extra Packages for Enterprise Linux 8 - x86_64
>> 11 MB/s | 13 MB 00:01
>> Extra Packages for Enterprise Linux Modular 8 - x86_64
>> 830 kB/s | 733 kB 00:00
>> Extra Packages for Enterprise Linux 8 - Next - x86_64
>> 1.5 MB/s | 1.4 MB 00:00
>> Error:
>> Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn
>> = 2:22.06-3.el8, but none of the providers can be installed
>> - cannot install the best update candidate for package
>> ovn-2021-central-21.12.0-82.el8s.x86_64
>> - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude
>> filtering
>> Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires
>> rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed
>> - cannot install the best update candidate for package
>> python3-openvswitch2.15-2.15.0-119.el8s.x86_64
>> - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by
>> exclude filtering
>> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
>> to use not only best candidate packages)
>>
>>
>> Regards,
>> Brett
>> ------------------------------
>> *From:* Lev Veyde <lveyde(a)redhat.com>
>> *Sent:* 19 October 2022 11:14
>> *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com>
>> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
>> *Subject:* [ovirt-users] Re: Ovirt host update bug
>>
>> Checked with the networking and looks like the issue is with the
>> conflicting OVS/OVN packages released on the OpenStack channel.
>>
>> Fixing that on our side will require releasing a new version, but one can
>> try to fix it manually by modifying the
>> /etc/yum.repos.d/CentOS-oVirt-4.5.repo file.
>>
>> 1. Find the [ovirt-45-centos-stream-openstack-yoga] section
>> 2. At the end of the section look for ansible-test under exclude=
>> 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same
>> way as *ansible* and *ansible-test* that already exists
>>
>>
>>
>> On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote:
>>
>> Hey I'm having an issue, curious if anyone can help
>>
>> I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but
>> have run into a problem with the update installer.
>>
>> The environment is:
>>
>> Static hostname: ovirt2.xxx.xxx
>> Icon name: computer-desktop
>> Chassis: desktop
>> Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29
>> Boot ID: dbc7438e4d464209ac79452410cf60e7
>> Operating System: CentOS Stream 8
>> CPE OS Name: cpe:/o:centos:centos:8
>> Kernel: Linux 4.18.0-408.el8.x86_64
>> Architecture: x86-64
>>
>>
>>
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> devtmpfs 8023804 0 8023804 0% /dev
>> tmpfs 8055520 24 8055496 1% /dev/shm
>> tmpfs 8055520 99708 7955812 2% /run
>> tmpfs 8055520 0 8055520 0% /sys/fs/cgroup
>> /dev/mapper/cs-root 73364480 11401568 61962912 16% /
>> /dev/mapper/cs-home 166691304 1467260 165224044 1% /home
>> /dev/sda2 1038336 262972 775364 26% /boot
>> /dev/sda1 613184 7416 605768 2% /boot/efi
>> tmpfs 1611104 12 1611092 1% /run/user/42
>> tmpfs 1611104 4 1611100 1% /run/user/1000
>>
>>
>> There are 3 hosts, which can all detect and begin the update, getting
>> most of the way through it, before failing and returning it to a state of
>> non-operation. The log file says that the host is unable to resolve the
>> virtual switch dependency
>> log excerpt:
>> "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false,
>> \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1:
>> package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but
>> none of the providers can be installed\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - packag
>> e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17
>> provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - cannot
>> install the best update candidate for package
>> ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update
>> candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2:
>> package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
>> python3-openvswitch2.15 < 2.17 provided by
>> python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package
>> openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires
>> python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be
>> installed\\n - cannot install the best update candidate for package
>> python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the
>> best update candidate for package
>> openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package
>> ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none
>> of the providers can be installed\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarc
>> h obsoletes ovn-2021 < 22.06 provided by
>> ovn-2021-21.03.0-21.el8s.x86_64\\n - 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\\n
>> - 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\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarch
>> obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n
>> - cannot install the best update candidate for package
>> ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update
>> candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n
>> Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires
>> ovn-2021-host, but none of the providers can be installed\\n - package
>> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
>> by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa
>> ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06
>> provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package
>> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
>> by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package
>> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
>> by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package
>> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
>> by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package
>> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
>> by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best
>> update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n -
>> cannot install the best update candidate for package
>> ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\":
>> []}",
>>
>> On one host, when I attempt to open the ovirt web console from the gui it
>> won't open, and virtual machines on that particular host are unable to run
>> an ovirt web console as well: citing handshake error failure.
>> log excerpt for host web console:
>>
>> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24
>> name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted:
>> custom-ga-command
>> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25
>> name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted:
>> custom-ga-command
>>
>> Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]:
>> ovs|00001|unixctl|WARN|failed to connect to
>> /var/run/ovn/ovn-controller.18617.ctl
>>
>> Thank you in advance
>> _______________________________________________
>> 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/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5USJX6G7ZAZ...
>>
>>
>>
>> --
>>
>> 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>
>> _______________________________________________
>> 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/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HM7YY77DZQI...
>>
>>
>>
>> --
>>
>> Ales Musil
>>
>> Senior Software Engineer - OVN Core
>>
>> Red Hat EMEA <https://www.redhat.com>
>>
>> amusil(a)redhat.com IM: amusil
>> <https://red.ht/sig>
>>
>
>
> --
>
> 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>
> _______________________________________________
> 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 year, 6 months
Re: Ovirt host update bug
by Lev Veyde
Hi,
We built a new centos-release-ovirt package that supposed to fix that issue
(on non manually fixed machine):
https://cbs.centos.org/kojifiles/packages/centos-release-ovirt45/8.7/3.el...
Could somebody please test that it indeed fixes the issue?
Thanks in advance,
On Wed, Oct 19, 2022 at 2:27 PM Brett Maton <matonb(a)ltresources.co.uk>
wrote:
> Thanks Ales,
>
> That fixed it for me, I don't think *rdo-ovn-central* is mentioned in link
> but that was the final missing exclude for me.
>
> Regards,
> Brett
>
> ------------------------------
> *From:* Ales Musil <amusil(a)redhat.com>
> *Sent:* 19 October 2022 11:50
> *To:* Brett Maton <matonb(a)ltresources.co.uk>
> *Cc:* Lev Veyde <lveyde(a)redhat.com>; mmoon(a)maxistechnology.com <
> mmoon(a)maxistechnology.com>; users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* Re: [ovirt-users] Re: Ovirt host update bug
>
> Hi,
>
> you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and "
> rdo-ovn-central" in the excluded.
> See
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT...
>
> Best regards,
> Ales
>
> On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk>
> wrote:
>
> I'm seeing the same error
>
> Repo config:
>
> # grep 'ovirt-45-centos-stream-openstack-yoga'
> /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15
>
> [ovirt-45-centos-stream-openstack-yoga]
> name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository
> # baseurl=
> http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/
> mirrorlist=
> http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-o...
> gpgcheck=1
> gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud
> enabled=1
> module_hotfixes=1
> exclude=
> # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on
> oVirt side
> ansible
> ansible-test
> * rdo-openvswitch*
> * rdo-ovn*
>
>
> Update attempt:
>
> # yum clean all
> 187 files removed
>
> # dnf update
> CentOS-8-stream - Ceph Pacific
> 781 kB/s | 456 kB 00:00
> CentOS-8-stream - Gluster 10
> 175 kB/s | 40 kB 00:00
> CentOS-8 - NFV OpenvSwitch
> 364 kB/s | 168 kB 00:00
> CentOS-OpsTools - collectd
> 169 kB/s | 41 kB 00:00
> CentOS Stream 8 - AppStream
> 24 MB/s | 25 MB 00:01
> CentOS Stream 8 - BaseOS
> 23 MB/s | 25 MB 00:01
> CentOS Stream 8 - Extras
> 39 kB/s | 18 kB 00:00
> CentOS Stream 8 - Extras common packages
> 24 kB/s | 4.9 kB 00:00
> CentOS Stream 8 - PowerTools
> 9.7 MB/s | 5.1 MB 00:00
> CentOS Stream 8 - oVirt 4.5
> 4.1 MB/s | 1.2 MB 00:00
> CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository
> 3.4 MB/s | 2.2 MB 00:00
> oVirt upstream for CentOS Stream 8 - oVirt 4.5
> 47 kB/s | 408 kB 00:08
> Extra Packages for Enterprise Linux 8 - x86_64
> 11 MB/s | 13 MB 00:01
> Extra Packages for Enterprise Linux Modular 8 - x86_64
> 830 kB/s | 733 kB 00:00
> Extra Packages for Enterprise Linux 8 - Next - x86_64
> 1.5 MB/s | 1.4 MB 00:00
> Error:
> Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn
> = 2:22.06-3.el8, but none of the providers can be installed
> - cannot install the best update candidate for package
> ovn-2021-central-21.12.0-82.el8s.x86_64
> - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude
> filtering
> Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires
> rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed
> - cannot install the best update candidate for package
> python3-openvswitch2.15-2.15.0-119.el8s.x86_64
> - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by exclude
> filtering
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
> to use not only best candidate packages)
>
>
> Regards,
> Brett
> ------------------------------
> *From:* Lev Veyde <lveyde(a)redhat.com>
> *Sent:* 19 October 2022 11:14
> *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com>
> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* [ovirt-users] Re: Ovirt host update bug
>
> Checked with the networking and looks like the issue is with the
> conflicting OVS/OVN packages released on the OpenStack channel.
>
> Fixing that on our side will require releasing a new version, but one can
> try to fix it manually by modifying the
> /etc/yum.repos.d/CentOS-oVirt-4.5.repo file.
>
> 1. Find the [ovirt-45-centos-stream-openstack-yoga] section
> 2. At the end of the section look for ansible-test under exclude=
> 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same
> way as *ansible* and *ansible-test* that already exists
>
>
>
> On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote:
>
> Hey I'm having an issue, curious if anyone can help
>
> I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but
> have run into a problem with the update installer.
>
> The environment is:
>
> Static hostname: ovirt2.xxx.xxx
> Icon name: computer-desktop
> Chassis: desktop
> Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29
> Boot ID: dbc7438e4d464209ac79452410cf60e7
> Operating System: CentOS Stream 8
> CPE OS Name: cpe:/o:centos:centos:8
> Kernel: Linux 4.18.0-408.el8.x86_64
> Architecture: x86-64
>
>
>
> Filesystem 1K-blocks Used Available Use% Mounted on
> devtmpfs 8023804 0 8023804 0% /dev
> tmpfs 8055520 24 8055496 1% /dev/shm
> tmpfs 8055520 99708 7955812 2% /run
> tmpfs 8055520 0 8055520 0% /sys/fs/cgroup
> /dev/mapper/cs-root 73364480 11401568 61962912 16% /
> /dev/mapper/cs-home 166691304 1467260 165224044 1% /home
> /dev/sda2 1038336 262972 775364 26% /boot
> /dev/sda1 613184 7416 605768 2% /boot/efi
> tmpfs 1611104 12 1611092 1% /run/user/42
> tmpfs 1611104 4 1611100 1% /run/user/1000
>
>
> There are 3 hosts, which can all detect and begin the update, getting most
> of the way through it, before failing and returning it to a state of
> non-operation. The log file says that the host is unable to resolve the
> virtual switch dependency
> log excerpt:
> "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false,
> \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1:
> package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but
> none of the providers can be installed\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - packag
> e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17
> provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - cannot
> install the best update candidate for package
> ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update
> candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2:
> package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
> python3-openvswitch2.15 < 2.17 provided by
> python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package
> openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires
> python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be
> installed\\n - cannot install the best update candidate for package
> python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the
> best update candidate for package
> openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package
> ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none
> of the providers can be installed\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarc
> h obsoletes ovn-2021 < 22.06 provided by
> ovn-2021-21.03.0-21.el8s.x86_64\\n - 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\\n
> - 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\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarch
> obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n
> - cannot install the best update candidate for package
> ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update
> candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n
> Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires
> ovn-2021-host, but none of the providers can be installed\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa
> ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06
> provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best
> update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n -
> cannot install the best update candidate for package
> ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\":
> []}",
>
> On one host, when I attempt to open the ovirt web console from the gui it
> won't open, and virtual machines on that particular host are unable to run
> an ovirt web console as well: citing handshake error failure.
> log excerpt for host web console:
>
> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24
> name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted:
> custom-ga-command
> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25
> name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted:
> custom-ga-command
>
> Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]:
> ovs|00001|unixctl|WARN|failed to connect to
> /var/run/ovn/ovn-controller.18617.ctl
>
> Thank you in advance
> _______________________________________________
> 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/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5USJX6G7ZAZ...
>
>
>
> --
>
> 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>
> _______________________________________________
> 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/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HM7YY77DZQI...
>
>
>
> --
>
> Ales Musil
>
> Senior Software Engineer - OVN Core
>
> Red Hat EMEA <https://www.redhat.com>
>
> amusil(a)redhat.com IM: amusil
> <https://red.ht/sig>
>
--
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 year, 6 months
Engine's certification is about to expire at .... Please renew the engine's certification.
by nicolas@devels.es
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.
1 year, 6 months
Re: Ovirt host update bug
by Ales Musil
Hi,
you need to specify also "rdo-ovn-host", "python3-rdo-openvswitch" and "
rdo-ovn-central" in the excluded.
See
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RIHO32QA3NT...
Best regards,
Ales
On Wed, Oct 19, 2022 at 12:35 PM Brett Maton <matonb(a)ltresources.co.uk>
wrote:
> I'm seeing the same error
>
> Repo config:
>
> # grep 'ovirt-45-centos-stream-openstack-yoga'
> /etc/yum.repos.d/CentOS-oVirt-4.5.repo -B1 -A15
>
> [ovirt-45-centos-stream-openstack-yoga]
> name=CentOS Stream $releasever - oVirt 4.5 - OpenStack Yoga Repository
> # baseurl=
> http://mirror.centos.org/centos/$stream/cloud/$basearch/openstack-yoga/
> mirrorlist=
> http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=cloud-o...
> gpgcheck=1
> gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Cloud
> enabled=1
> module_hotfixes=1
> exclude=
> # ansible-2.9.27-4.el8 shipped in yoga repo is breaking dependencies on
> oVirt side
> ansible
> ansible-test
> * rdo-openvswitch*
> * rdo-ovn*
>
>
> Update attempt:
>
> # yum clean all
> 187 files removed
>
> # dnf update
> CentOS-8-stream - Ceph Pacific
> 781 kB/s | 456 kB 00:00
> CentOS-8-stream - Gluster 10
> 175 kB/s | 40 kB 00:00
> CentOS-8 - NFV OpenvSwitch
> 364 kB/s | 168 kB 00:00
> CentOS-OpsTools - collectd
> 169 kB/s | 41 kB 00:00
> CentOS Stream 8 - AppStream
> 24 MB/s | 25 MB 00:01
> CentOS Stream 8 - BaseOS
> 23 MB/s | 25 MB 00:01
> CentOS Stream 8 - Extras
> 39 kB/s | 18 kB 00:00
> CentOS Stream 8 - Extras common packages
> 24 kB/s | 4.9 kB 00:00
> CentOS Stream 8 - PowerTools
> 9.7 MB/s | 5.1 MB 00:00
> CentOS Stream 8 - oVirt 4.5
> 4.1 MB/s | 1.2 MB 00:00
> CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository
> 3.4 MB/s | 2.2 MB 00:00
> oVirt upstream for CentOS Stream 8 - oVirt 4.5
> 47 kB/s | 408 kB 00:08
> Extra Packages for Enterprise Linux 8 - x86_64
> 11 MB/s | 13 MB 00:01
> Extra Packages for Enterprise Linux Modular 8 - x86_64
> 830 kB/s | 733 kB 00:00
> Extra Packages for Enterprise Linux 8 - Next - x86_64
> 1.5 MB/s | 1.4 MB 00:00
> Error:
> Problem 1: package rdo-ovn-central-2:22.06-3.el8.noarch requires rdo-ovn
> = 2:22.06-3.el8, but none of the providers can be installed
> - cannot install the best update candidate for package
> ovn-2021-central-21.12.0-82.el8s.x86_64
> - package rdo-ovn-2:22.06-3.el8.noarch is filtered out by exclude
> filtering
> Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch requires
> rdo-openvswitch = 2:2.17-3.el8, but none of the providers can be installed
> - cannot install the best update candidate for package
> python3-openvswitch2.15-2.15.0-119.el8s.x86_64
> - package rdo-openvswitch-2:2.17-3.el8.noarch is filtered out by exclude
> filtering
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
> to use not only best candidate packages)
>
>
> Regards,
> Brett
> ------------------------------
> *From:* Lev Veyde <lveyde(a)redhat.com>
> *Sent:* 19 October 2022 11:14
> *To:* mmoon(a)maxistechnology.com <mmoon(a)maxistechnology.com>
> *Cc:* users(a)ovirt.org <users(a)ovirt.org>
> *Subject:* [ovirt-users] Re: Ovirt host update bug
>
> Checked with the networking and looks like the issue is with the
> conflicting OVS/OVN packages released on the OpenStack channel.
>
> Fixing that on our side will require releasing a new version, but one can
> try to fix it manually by modifying the
> /etc/yum.repos.d/CentOS-oVirt-4.5.repo file.
>
> 1. Find the [ovirt-45-centos-stream-openstack-yoga] section
> 2. At the end of the section look for ansible-test under exclude=
> 3. Add *rdo-openvswitch* and *rdo-ovn* each on their own line, in same
> way as *ansible* and *ansible-test* that already exists
>
>
>
> On Wed, Oct 19, 2022 at 1:49 AM <mmoon(a)maxistechnology.com> wrote:
>
> Hey I'm having an issue, curious if anyone can help
>
> I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but
> have run into a problem with the update installer.
>
> The environment is:
>
> Static hostname: ovirt2.xxx.xxx
> Icon name: computer-desktop
> Chassis: desktop
> Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29
> Boot ID: dbc7438e4d464209ac79452410cf60e7
> Operating System: CentOS Stream 8
> CPE OS Name: cpe:/o:centos:centos:8
> Kernel: Linux 4.18.0-408.el8.x86_64
> Architecture: x86-64
>
>
>
> Filesystem 1K-blocks Used Available Use% Mounted on
> devtmpfs 8023804 0 8023804 0% /dev
> tmpfs 8055520 24 8055496 1% /dev/shm
> tmpfs 8055520 99708 7955812 2% /run
> tmpfs 8055520 0 8055520 0% /sys/fs/cgroup
> /dev/mapper/cs-root 73364480 11401568 61962912 16% /
> /dev/mapper/cs-home 166691304 1467260 165224044 1% /home
> /dev/sda2 1038336 262972 775364 26% /boot
> /dev/sda1 613184 7416 605768 2% /boot/efi
> tmpfs 1611104 12 1611092 1% /run/user/42
> tmpfs 1611104 4 1611100 1% /run/user/1000
>
>
> There are 3 hosts, which can all detect and begin the update, getting most
> of the way through it, before failing and returning it to a state of
> non-operation. The log file says that the host is unable to resolve the
> virtual switch dependency
> log excerpt:
> "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false,
> \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1:
> package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but
> none of the providers can be installed\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - packag
> e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17
> provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - cannot
> install the best update candidate for package
> ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update
> candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2:
> package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
> python3-openvswitch2.15 < 2.17 provided by
> python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package
> openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires
> python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be
> installed\\n - cannot install the best update candidate for package
> python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the
> best update candidate for package
> openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package
> ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none
> of the providers can be installed\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarc
> h obsoletes ovn-2021 < 22.06 provided by
> ovn-2021-21.03.0-21.el8s.x86_64\\n - 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\\n
> - 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\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarch
> obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n
> - cannot install the best update candidate for package
> ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update
> candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n
> Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires
> ovn-2021-host, but none of the providers can be installed\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa
> ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06
> provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package
> rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided
> by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best
> update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n -
> cannot install the best update candidate for package
> ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\":
> []}",
>
> On one host, when I attempt to open the ovirt web console from the gui it
> won't open, and virtual machines on that particular host are unable to run
> an ovirt web console as well: citing handshake error failure.
> log excerpt for host web console:
>
> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24
> name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted:
> custom-ga-command
> Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25
> name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted:
> custom-ga-command
>
> Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]:
> ovs|00001|unixctl|WARN|failed to connect to
> /var/run/ovn/ovn-controller.18617.ctl
>
> Thank you in advance
> _______________________________________________
> 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/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5USJX6G7ZAZ...
>
>
>
> --
>
> 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>
> _______________________________________________
> 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/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HM7YY77DZQI...
>
--
Ales Musil
Senior Software Engineer - OVN Core
Red Hat EMEA <https://www.redhat.com>
amusil(a)redhat.com IM: amusil
<https://red.ht/sig>
1 year, 6 months
Ovirt host update bug
by mmoon@maxistechnology.com
Hey I'm having an issue, curious if anyone can help
I'm trying to update my ovirt cluster from 4.5.2.4-1.el8 to 4.5.3.1 but have run into a problem with the update installer.
The environment is:
Static hostname: ovirt2.xxx.xxx
Icon name: computer-desktop
Chassis: desktop
Machine ID: 0eb1fcff65214fb399c9d2ffaf1f5a29
Boot ID: dbc7438e4d464209ac79452410cf60e7
Operating System: CentOS Stream 8
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-408.el8.x86_64
Architecture: x86-64
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 8023804 0 8023804 0% /dev
tmpfs 8055520 24 8055496 1% /dev/shm
tmpfs 8055520 99708 7955812 2% /run
tmpfs 8055520 0 8055520 0% /sys/fs/cgroup
/dev/mapper/cs-root 73364480 11401568 61962912 16% /
/dev/mapper/cs-home 166691304 1467260 165224044 1% /home
/dev/sda2 1038336 262972 775364 26% /boot
/dev/sda1 613184 7416 605768 2% /boot/efi
tmpfs 1611104 12 1611092 1% /run/user/42
tmpfs 1611104 4 1611100 1% /run/user/1000
There are 3 hosts, which can all detect and begin the update, getting most of the way through it, before failing and returning it to a state of non-operation. The log file says that the host is unable to resolve the virtual switch dependency
log excerpt:
"stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - packag
e rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - 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\\n - cannot
install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarc
h obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\\n - 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\\n - 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\\n - 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\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - pa
ckage rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": []}",
On one host, when I attempt to open the ovirt web console from the gui it won't open, and virtual machines on that particular host are unable to run an ovirt web console as well: citing handshake error failure.
log excerpt for host web console:
Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=24 name='cen-79-dmz-02' uuid=82fefcfa-bce0-4397-a575-48d3d08fdb61 is tainted: custom-ga-command
Oct 17 15:58:29 ovirt-host-05 journal[96215]: Domain id=25 name='win-10-utl' uuid=11f71942-1d88-40a0-a6c5-45e7718afbcf is tainted: custom-ga-command
Oct 17 03:37:01 ovirt-host-05 ovs-appctl[37436]: ovs|00001|unixctl|WARN|failed to connect to /var/run/ovn/ovn-controller.18617.ctl
Thank you in advance
1 year, 6 months
hosted-engine-setup --deploy fail on Centos Stream 8
by andrea.crisanti@uniroma1.it
Hy,
I am trying to install ovirt 4.5 on a 4-host cluster running Centos Stream 8, but the engine does not start and the whole process fails.
Here is my procedure
dnf install centos-release-ovirt45
dnf module reset virt
dnf module enable virt:rhel
dnf install ovirt-engine-appliance
dnf install ovirt-hosted-engine-setup
The latest version of ansible [ansible-core 2.13] uses python3.9 and the installation fails because some python3.9 modules are missing
[python39-netaddr, python39-jmespath] and cannot be installed [conflict python3-jmespath]. So I downgraded ansible to ansible-core 2.12
dnf downgrade ansible-core
Now
hosted-engine-setup --deploy --4
goes proceed further but stops because it cannot start the engine
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"}
I looked into the log file
/var/log//ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20221007132728-yp7cd1.log
and I found the following error:
2022-10-07 13:28:30,881+0200 ERROR ansible failed {
"ansible_host": "localhost",
"ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml",
"ansible_result": {
"_ansible_no_log": false,
"changed": false,
"cmd": [
"virsh",
"net-undefine",
"default"
],
"delta": "0:00:00.039258",
"end": "2022-10-07 13:28:30.710401",
"invocation": {
"module_args": {
"_raw_params": "virsh net-undefine default",
"_uses_shell": false,
"argv": null,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"stdin": null,
"stdin_add_newline": true,
"strip_empty_ends": true,
"warn": false
}
},
"msg": "non-zero return code",
"rc": 1,
"start": "2022-10-07 13:28:30.671143",
"stderr": "error: failed to get network 'default'\nerror: Network not found: no network with matching name 'default'",
"stderr_lines": [
"error: failed to get network 'default'",
"error: Network not found: no network with matching name 'default'"
],
"stdout": "",
"stdout_lines": []
},
"ansible_task": "Update libvirt default network configuration, undefine",
"ansible_type": "task",
"status": "FAILED",
"task_duration": 0
}
Needless to say
firewalld and libvirtd are both up
and virsh net-list gives:
Name State Autostart Persistent
------------------------------------------------
;vdsmdummy; active no no
default active no yes
I googled around without success.
Has anyone had similar problems?
End of past July I installed Ovirt on another cluster running Centos Stream 8 following the procedure I just described with no problem.
If needed I can post all log files.
Thanks for the help.
Best
Andrea
1 year, 6 months
Get Vlan IDs from multiple VMs
by chry3@hotmail.com
Hello,
I´m exrtracting diferent VM informations from diferent VMs that are deployed on a server that I need to proccess later. I already have informations such as IPs, macs cpu cores etc, but I would like to get the VLAN id from each of the VMs. How can I do that? How can I get the network profile that my VM is using?
Kind Regards.
1 year, 6 months
Adding documentation - Migrating from a self-hosted engine to a standalone
by David White
Hi. I'm working on adding instructions to the documentation for how to migrate from a self-hosted engine to a stand alone manager. This will be the first time I've contributed anything to this project (or any larger open source project for that matter), so before I get too far in the weeds, I wanted to run this by the community so as not to waste my time if this is a bad idea.
My general high level documentation is pasted at the bottom of this email. These are the steps that I took when I did my own migration.
(Note to self: Need to add a step at the end to log into the Manager and disable the Gluster service by going to Computer --> Clusters --> (Edit the cluster) --> Uncheck the "Enable Gluster Service" checkbox.
And I've forked the ovirt-site repo and started working on the documentation here: https://github.com/dmwhite823/ovirt-site/tree/migrate-engine-to-standalone
I still have a ways to go before I'm ready to request a PR, but I'm open to any & all feedback. I think that I'm done with most of the changes necessary to ovirt-site/source/documentation/migrating_from_a_self-hosted_engine_to_a_standalone_manager/index.adoc, but I'm unclear why there's also a master.adoc file.
Note that I copied files into the new directory of migrating_from_a_self-hosted_engine_to_a_standalone_manager from the already existing migrating_from_a_standalone_manager_to_a_self-hosted_engine structure directory, and am editing the files in the new directory.
Will this be useful / helpful? Would others on the team like to contribute to improving these instructions prior to issuing a PR to the ovirt-site git repo? Am I even doing this right? 🤣
Thanks,
David
High level overview of steps required (pasted below):
Pre-req: Make sure VMs are not using HA lease of a gluster domain
1) Migrate all storage off Gluster
2) Remove all gluster volumes from oVirt
3) Put cluster into global maintenance
hosted-engine --set-maintenance --mode=global
4) On new VM:
Install CentOS Stream & add ovirt repos
dnf install centos-release-ovirt45
dnf module enable javapackages-tools pki-deps postgresql:12 mod_auth_openidc:2.3 nodejs:14
Stop & Disable the engine
# systemctl stop ovirt-engine
# systemctl disable ovirt-engine
Setup DNS in /etc/hosts if you don't have local DNS servers
Backup the engine
# engine-backup --mode=backup --file=file_name --log=log_file_name
Restore
# engine-backup --mode=restore --file=engine-backup-09172022-1 --log=restore --restore-permissions
Run engine-setup
# engine-setup
1 year, 6 months