[ovirt-users] oVirt Node 4.5.3.1 Async update

2022-10-20 Thread 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 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LXCTQGKBF2UBENE2I27TVJSEZFNBUSGC/

[ovirt-users] Re: Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."

2022-10-20 Thread Yedidyah Bar David 
On Thu, Oct 20, 2022 at 1:59 PM Matthew J Black  wrote:
>
> Hi Everyone,
>
> Could someone please help me - I've been trying to do an install of oVirt for 
> *weeks* (including false starts and self-inflicted wounds/errors) and it is 
> still not working.
>
> My setup:
>
> - oVirt v4.5.3
> - A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK
> - 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all 
> working AOK
> - All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK
> - All relevant IPv4 Address in "/etc/hosts" file - all working AOK
> - IPv6 (using "method=auto" in the interface config file) enabled on the 
> relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, 
> but I'm trying to cover all the bases.
> - All relevant Ports (as per the oVirt documentation) set up on the firewall
> - ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | 
> ovirt-vmconsole | vdsm }}
> - All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & 
> PowerTools, and the EPEL, plus the ones from the oVirt documentation)
>
> I have followed the oVirt documentation (including the special 
> RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, 
> no special settings, exactly as they are written.
>
> All the dnf installs, etc, went off without a hitch, including the "dnf 
> install centos-release-ovirt45", "dnf install ovirt-engine-appliance", and 
> "dnf install ovirt-hosted-engine-setup" - no errors anywhere.
>
> Here is the results of a "dnf repolist":
>
> - appstreamRocky Linux 8 - 
> AppStream
> - baseos Rocky Linux 8 - 
> BaseOS
> - centos-ceph-pacific  CentOS-8-stream - Ceph 
> Pacific
> - centos-gluster10   CentOS-8-stream - 
> Gluster 10
> - centos-nfv-openvswitchCentOS-8 - NFV OpenvSwitch
> - centos-opstoolsCentOS-OpsTools - 
> collectd
> - centos-ovirt45   CentOS Stream 8 - 
> oVirt 4.5
> - cs8-extras CentOS Stream 8 
> - Extras
> - cs8-extras-common   CentOS Stream 8 - 
> Extras common packages
> - epel   Extra 
> Packages for Enterprise Linux 8 - x86_64
> - epel-modular Extra Packages for 
> Enterprise Linux Modular 8 - x86_64
> - ovirt-45-centos-stream-openstack-yogaCentOS Stream 8 - oVirt 4.5 - 
> OpenStack Yoga Repository
> - ovirt-45-upstream  oVirt upstream for 
> CentOS Stream 8 - oVirt 4.5
> - powertools Rocky Linux 8 - 
> PowerTools
>
> So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 
> --ansible-extra-vars=he_offline_deployment=true".
>
> I used "--ansible-extra-vars=he_offline_deployment=true" because without that 
> flag I was getting "DNF timout" issues (see my previous post `Local 
> (Deployment) VM Can't Reach "centos-ceph-pacific" Repo`).
>
> I answer the defaults to all of questions the script asked, or entered the 
> deployment-relevant answers where appropriate. In doing this I double-checked 
> every answer before hitting . Everything progressed smoothly until the 
> deployment reached the "Wait for the host to be up" task... which then hung 
> for more than 30 minutes before failing.
>
> From the ovirt-hosted-engine-setup... log file:
>
> - 2022-10-20 17:54:26,285+1100 ERROR 
> otopi.ovirt_hosted_engine_setup.ansible_utils 
> ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": 
> false, "msg": "Host is not up, please check logs, perhaps also on the engine 
> machine"}
>
> I checked the following log files and found all of the relevant ERROR lines, 
> then checked several 10s of proceeding and succeeding lines trying to 
> determine what was going wrong, but I could not determine anything.
>
> - ovirt-hosted-engine-setup...
> - ovirt-hosted-engine-setup-ansible-bootstrap_local_vm...
> - ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I 
> believe
>
> I can include the log files (or the relevant parts of the log files) if 
> people want - but that are very large: several 100 kilobytes each.

You can upload to some file sharing service (dropbox, google drive,
etc.) and share a link. If it's just not-too-long text you can use
some pastebin (might be more or less convenient for some readers, I
didn't do a poll).

>
> I also googled "oVirt Host is not up" and found several entries, but after 
> reading them all the most relevant seems to be a thread from these mailing 
> list: `Install of RHV 4.4 failing - "Host is not up, please check logs, 
> perhaps also on the en

[ovirt-users] Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."

2022-10-20 Thread Matthew J Black 
Hi Everyone,

Could someone please help me - I've been trying to do an install of oVirt for 
*weeks* (including false starts and self-inflicted wounds/errors) and it is 
still not working.

My setup:

- oVirt v4.5.3
- A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK
- 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all 
working AOK
- All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK
- All relevant IPv4 Address in "/etc/hosts" file - all working AOK
- IPv6 (using "method=auto" in the interface config file) enabled on the 
relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, but 
I'm trying to cover all the bases.
- All relevant Ports (as per the oVirt documentation) set up on the firewall
- ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | 
ovirt-vmconsole | vdsm }}
- All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & 
PowerTools, and the EPEL, plus the ones from the oVirt documentation)

I have followed the oVirt documentation (including the special 
RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, 
no special settings, exactly as they are written.

All the dnf installs, etc, went off without a hitch, including the "dnf install 
centos-release-ovirt45", "dnf install ovirt-engine-appliance", and "dnf install 
ovirt-hosted-engine-setup" - no errors anywhere.

Here is the results of a "dnf repolist":

- appstreamRocky Linux 8 - 
AppStream
- baseos Rocky Linux 8 - 
BaseOS
- centos-ceph-pacific  CentOS-8-stream - Ceph 
Pacific
- centos-gluster10   CentOS-8-stream - 
Gluster 10
- centos-nfv-openvswitchCentOS-8 - NFV OpenvSwitch
- centos-opstoolsCentOS-OpsTools - 
collectd
- centos-ovirt45   CentOS Stream 8 - 
oVirt 4.5
- cs8-extras CentOS Stream 8 - 
Extras
- cs8-extras-common   CentOS Stream 8 - Extras 
common packages
- epel   Extra Packages 
for Enterprise Linux 8 - x86_64
- epel-modular Extra Packages for 
Enterprise Linux Modular 8 - x86_64
- ovirt-45-centos-stream-openstack-yogaCentOS Stream 8 - oVirt 4.5 - 
OpenStack Yoga Repository
- ovirt-45-upstream  oVirt upstream for 
CentOS Stream 8 - oVirt 4.5
- powertools Rocky Linux 8 - 
PowerTools

So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 
--ansible-extra-vars=he_offline_deployment=true".

I used "--ansible-extra-vars=he_offline_deployment=true" because without that 
flag I was getting "DNF timout" issues (see my previous post `Local 
(Deployment) VM Can't Reach "centos-ceph-pacific" Repo`).

I answer the defaults to all of questions the script asked, or entered the 
deployment-relevant answers where appropriate. In doing this I double-checked 
every answer before hitting . Everything progressed smoothly until the 
deployment reached the "Wait for the host to be up" task... which then hung for 
more than 30 minutes before failing.

From the ovirt-hosted-engine-setup... log file:

- 2022-10-20 17:54:26,285+1100 ERROR 
otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, 
please check logs, perhaps also on the engine machine"}

I checked the following log files and found all of the relevant ERROR lines, 
then checked several 10s of proceeding and succeeding lines trying to determine 
what was going wrong, but I could not determine anything.

- ovirt-hosted-engine-setup...
- ovirt-hosted-engine-setup-ansible-bootstrap_local_vm...
- ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I 
believe

I can include the log files (or the relevant parts of the log files) if people 
want - but that are very large: several 100 kilobytes each.

I also googled "oVirt Host is not up" and found several entries, but after 
reading them all the most relevant seems to be a thread from these mailing 
list: `Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps 
also on the engine machine"` - but this seems to be talking about an upgrade 
and I didn't gleam anything useful from it - I could, of course, be wrong about 
that.

So my questions are:

- Where else should I be looking (ie other log files, etc, and possible where 
to find them)?
- Does anyone have any idea why this isn't working?
- Does anyone have a work-around (including a completely manual process to get 
things working - I don't mind working in the CLI with virsh, et

[ovirt-users] Re: Users Digest, Vol 133, Issue 36

2022-10-20 Thread David Johnson 
> We can try this at our next maintenance window, probably in a week or so


> From: Lev Veyde 
> To: Brett Maton 
> Cc: "mm...@maxistechnology.com" , "
> users@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.el8s/noarch/centos-release-ovirt45-8.7-3.el8s.noarch.rpm
>
> Could somebody please test that it indeed fixes the issue?
>
> Thanks in advance,
>
> On Wed, Oct 19, 2022 at 2:27 PM Brett Maton 
> 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 
>> *Sent:* 19 October 2022 11:50
>> *To:* Brett Maton 
>> *Cc:* Lev Veyde ; mm...@maxistechnology.com <
>> mm...@maxistechnology.com>; users@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/RIHO32QA3NT6YFCL3H63AEEPW7ELTKMU/
>>
>> Best regards,
>> Ales
>>
>> On Wed, Oct 19, 2022 at 12:35 PM Brett Maton 
>> 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-openstack-yoga
>> 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 
>> *Sent:* 19 October 2022 11:14
>> *To:* mm...@maxistechnology.com 
>> *Cc:* users@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=
>>

[ovirt-users] After failed upgrade from 4.5.1 to 4.5.3, upgrades do not show up anymore

2022-10-20 Thread Gianluca Amato 
Hi all,
I recently tried to upgrade an oVirt node from 4.5.1 to 4.5.3. The upgrade 
failed (I have no idea idea why... how can I access the installation logs?). 
The node is still working fine running the old 4.5.1 release, but now the oVirt 
web console says that it is up to date and it does not let me retry the 
upgrade. However, I am still on version 4.5.1, as witnessed by the result of 
"nodectl info":


bootloader: 
  default: ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64)
  entries: 
ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64): 
  index: 0
  kernel: 
/boot//ovirt-node-ng-4.5.1-0.20220623.0+1/vmlinuz-4.18.0-394.el8.x86_64
  args: crashkernel=auto resume=/dev/mapper/onn_ovirt--clai1-swap 
rd.lvm.lv=onn_ovirt-clai1/ovirt-node-ng-4.5.1-0.20220623.0+1 
rd.lvm.lv=onn_ovirt-clai1/swap rhgb quiet 
boot=UUID=9d44cf2a-38bb-477d-b542-4bfc30463d1f rootflags=discard 
img.bootid=ovirt-node-ng-4.5.1-0.20220623.0+1 intel_iommu=on 
modprobe.blacklist=nouveau transparent_hugepage=never hugepagesz=1G 
hugepages=256 default_hugepagesz=1G
  root: /dev/onn_ovirt-clai1/ovirt-node-ng-4.5.1-0.20220623.0+1
  initrd: 
/boot//ovirt-node-ng-4.5.1-0.20220623.0+1/initramfs-4.18.0-394.el8.x86_64.img
  title: ovirt-node-ng-4.5.1-0.20220623.0 (4.18.0-394.el8.x86_64)
  blsid: ovirt-node-ng-4.5.1-0.20220623.0+1-4.18.0-394.el8.x86_64
layers: 
  ovirt-node-ng-4.5.1-0.20220623.0: 
ovirt-node-ng-4.5.1-0.20220623.0+1
current_layer: ovirt-node-ng-4.5.1-0.20220623.0+1
--

Comparing the situation with other hosts in the same data center, it seems that 
the problem is that the package ovirt-node-ng-image-update-placeholder is not 
installed anymore, hence "dnf upgrade" has nothing to do. My idea was to 
manually download and install the 4.5.1 version of 
ovirt-node-ng-image-update-placeholder and attempt installation again. 

Is it a correct way to proceed ?

Thanks for any help.

--gianluca amato
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2VS5Q56URFSVO2DQGRAGQ4XCI6Q7W7W/