date:20221021

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

2022-10-21 Thread Volenbovskyi, Konstantin

Hi,
It seems that you are here: 
https://github.com/oVirt/ovirt-ansible-collection/blob/33d273e2e823bf0c2440a9009a0d38d1b383c27c/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml

I would say that in this case following is likely:
1) virsh list (with authentication) shows that hostedEnginelocal is running
2) SSH is successful from ovirt host due to temporary entry in /etc/hosts
3) You might see that ovirt-engine service is running on port 443 and then it 
is exposed
as port 6900 on your ovirt host.

Check out 
https://github.com/oVirt/ovirt-ansible-collection/blob/33d273e2e823bf0c2440a9009a0d38d1b383c27c/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml#L132
That means you can provide he_pause_host Ansible variable with value 'true' and 
take a pause for troubleshooting here.

So in case above is correct for your situation - then you should do port 
forwarding from port 6900
to port 443 on your local workstation/somewhere where you have browser and 
connect to ovengine GUI
Then you go to 'Hosts' and see if the host is 'up'. It is unlikely that it will 
be up.
Alternatively, there is REST API on this I think (=the one used by Ansible 
module in 'wait for host is up' task), but I don't know specifics.

In GUI go to 'Setup host network' and make sure that network bridge/network 
interfaces and maybe try to assign this network
(be careful: you might also connectivity to your ovirt host). Check those 
DHCP/Static IP assignment aspect.

There could be too many assumptions above, but hopefully it gives you something 
to use within troubleshooting.

BR,
Konstantin


On 20.10.22, 12:58, "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

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Latchezar Filtchev

Dear Martin,

Thank you for your advice.
For me the problem started with ovirt- 4.5.2 – I was not able to add new 
virtualization host. After downgrade of ansible-core – virtualization host was 
added successfully.
Than ovirt-4.5.3 came and engine and hosts updates failed.
All good now.
Thank you and all guys working to solve this issue.
Best,
Latcho


From: Martin Perina 
Sent: Friday, October 21, 2022 10:59 AM
To: Latchezar Filtchev 
Cc: Milan Zamazal ; users 
Subject: Re: [ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

Hi Latchezar,

so there seems to be several issues according the error you have posted below:

1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so if this 
package is already installed on your machine, you need to downgrade it to 
ansible-core-2.12 before continuing with engine installation
2. If any of those rdo* packages are already installed on your machine, you 
need remote them manually before proceeding with engine installation
3. Please check that you really have installed only required repositories on 
your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks RDO 
packages to interfere with oVirt

Regards,
Martin


On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev 
mailto:lat...@aubg.bg>> wrote:
Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS Stream release 8 
shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails - the result is 
below. Do you thing manual elimination of rdo-related will solve it?

Thank you!
Best,
Latcho


Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022 06:47:31 AM EEST.
Error:
 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires 
openvswitch2.15, but none of the providers can be installed
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by

[ovirt-users] Re: Unable to delete snapshots on vm

2022-10-21 Thread Roanne Philip

Hi Benny
How would I go about removing it from the tables


Roanne Philip
Architect: Virtualization and Storage
__
D: 087 805  | M: 072 047 5408
A: Suite 302, 3rd Floor, The Waverley Business Park, 27 Kotzee Road, Observatory
roanne.phi...@voxtelecom.co.za

www.vox.co.za



 " If nothing's running the next step would be to remove the commands from the 
command_entities table"

-Original Message-
From: Roanne Philip 
Sent: 19 October 2022 12:00 PM
To: Benny Zlotnik 
Cc: users@ovirt.org
Subject: RE: [ovirt-users] Re: Unable to delete snapshots on vm

engine=# select command_id,root_command_id from command_entities where 
root_command_id = '5de31579-15df-4c61-ac06-2b03a25d5db4’;
engine'# select command_id,root_command_id from command_entities where 
root_command_id = 'a15a8e6b-1624-4082-ac5d-7609626250cf’;
ERROR:  syntax error at or near "a15a8e6b"
LINE 2: ...id from command_entities where root_command_id = 'a15a8e6b-1...
 ^ engine=#

-Original Message-
From: Benny Zlotnik 
Sent: 19 October 2022 11:57 AM
To: Roanne Philip 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Re: Unable to delete snapshots on vm

what's the output of these queries:

select command_id,root_command_id from command_entities where root_command_id = 
'5de31579-15df-4c61-ac06-2b03a25d5db4’;

select command_id,root_command_id from command_entities where root_command_id = 
'a15a8e6b-1624-4082-ac5d-7609626250cf’;


___
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/WFGC3QGMIFM3FNUBCYRZYPF5XN2ZFJTC/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm

OK after reading the message from Martin again I understood that the rdo 
packages should not be installed. By chance I picked one host with such 
packages installed.

I have removed them and update was successful.

So looks like the engine and the ansible-core looks like still a bit 
strange but I have excluded it manually for now on the engine.


Best regards
Christoph

Am 21.10.22 um 11:35 schrieb Christoph Timm:

Hi all,

also the update of a CentOS Stream 8 host is not working.
Also here I have updated the centos-release-ovirt45 (8.7-3) package 
before.


Error:
 Problem: package rdo-openvswitch-1:2.15-2.el8.noarch requires 
network-scripts-openvswitch = 1:2.15, but none of the providers can be 
installed
  - cannot install both 
rdo-network-scripts-openvswitch-2:2.17-3.el8.noarch and 
rdo-network-scripts-openvswitch-1:2.15-2.el8.noarch
  - cannot install the best update candidate for package 
network-scripts-openvswitch2.15-2.15.0-115.el8s.x86_64

  - problem with installed package rdo-openvswitch-1:2.15-2.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting 
packages or '--skip-broken' to skip uninstallable packages or 
'--nobest' to use not only best candidate packages)


The rdo-openvswitch is getting excluded with the new repo files. I 
guess also rdo-network-scripts-openvswitch needs to be excluded from 
that ovirt-45-centos-stream-openstack-yoga repo in case the version 
2.15 should be used.


dnf list | grep rdo-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el8 @ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-devel.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-test.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga


The command "dnf update --refresh 
--exclude=rdo-network-scripts-openvswitch" would work on the host.


Best regards
Christoph


Am 21.10.22 um 10:55 schrieb Christoph Timm:

Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update 
the self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of 
the please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting 
packages or '--skip-broken' to skip uninstallable packages or 
'--nobest' to use not only best candidate packages)


As you can see the correct version is installed but appstream is 
already providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 2.13.3-1.el8 appstream

DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so 
if this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  
wrote:


Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will
deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS
Stream release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails
- the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm


Hi all,

also the update of a CentOS Stream 8 host is not working.
Also here I have updated the centos-release-ovirt45 (8.7-3) package before.

Error:
 Problem: package rdo-openvswitch-1:2.15-2.el8.noarch requires 
network-scripts-openvswitch = 1:2.15, but none of the providers can be 
installed
  - cannot install both 
rdo-network-scripts-openvswitch-2:2.17-3.el8.noarch and 
rdo-network-scripts-openvswitch-1:2.15-2.el8.noarch
  - cannot install the best update candidate for package 
network-scripts-openvswitch2.15-2.15.0-115.el8s.x86_64

  - problem with installed package rdo-openvswitch-1:2.15-2.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting 
packages or '--skip-broken' to skip uninstallable packages or '--nobest' 
to use not only best candidate packages)


The rdo-openvswitch is getting excluded with the new repo files. I guess 
also rdo-network-scripts-openvswitch needs to be excluded from that 
ovirt-45-centos-stream-openstack-yoga repo in case the version 2.15 
should be used.


dnf list | grep rdo-openvswitch
rdo-openvswitch.noarch 1:2.15-2.el8 @ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-devel.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga
rdo-openvswitch-test.noarch 2:2.17-3.el8 
ovirt-45-centos-stream-openstack-yoga


The command "dnf update --refresh 
--exclude=rdo-network-scripts-openvswitch" would work on the host.


Best regards
Christoph


Am 21.10.22 um 10:55 schrieb Christoph Timm:

Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update 
the self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of 
the please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting 
packages or '--skip-broken' to skip uninstallable packages or 
'--nobest' to use not only best candidate packages)


As you can see the correct version is installed but appstream is 
already providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 2.13.3-1.el8 appstream

DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so 
if this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  
wrote:


Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will
deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS
Stream release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails -
the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package
ovirt-engine-4.5.3.1-1.el8.noarch

- cannot install the best update candidate for package
ansible-core-2.12.7-1.el8.x86_64

Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
openvswitch2.15, but none of the providers can be installed

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-119.el8s.x86_64

- package

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

2022-10-21 Thread Matthew J Black

OK, so I think I've identified the issue. I found these lines in the engine.log 
file:

2022-10-20 17:27:36,785+11 ERROR 
[org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) 
[4a1c2931-f754-4020-8bf3-27455338ca6d] Failed to authenticate session with host 
'ovirt_node_1.mynet.local': SSH authentication to 
'root@ovirt_node_1.mynet.local' failed. Please verify provided credentials. 
Make sure key is authorized at host

2022-10-20 17:27:36,786+11 WARN  
[org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) 
[4a1c2931-f754-4020-8bf3-27455338ca6d] Validation of action 'AddVds' failed for 
user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server 
ovirt_node_1.mynet.local,VDS_CANNOT_AUTHENTICATE_TO_SERVER

2022-10-20 17:27:36,822+11 ERROR 
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default 
task-1) [] Operation Failed: [Cannot add Host. SSH authentication failed, 
verify authentication parameters are correct (Username/Password, public-key 
etc.) You may refer to the engine.log file for further details.]

So my next set of questions:

- I don't recall anywhere in the deployment script being asked to supply the 
root login credentials for ovirt_node_1.mynet.local (the host), so what have I 
missed?
- I don't recall being asked to supply a ssh cert for logging into 
ovirt_node_1.mynet.local. The only ssh cert being asked about (and its marked 
as "Optional") is one to log into the deployed engine *after* it is deployed 
(Step 16 of "5.3. Deploying the self-hosted engine using the command line"). Am 
I missing something here?
- In the Prerequisites section of 5.3 the doco mentions "The self-hosted engine 
setup script requires ssh public key access using 2048-bit RSA keys from the 
engine virtual machine to the root account of its bare metal host." and then 
talks about having various settings set in the host's sshd_config file. In the 
host's authoized_keys file there is an RSA key (not placed by me) which I 
assume the deployment script placed there. Again, what am I not understanding 
about this?

I've checked the host's sshd_config file and all of the requirements listed in 
section 5.3 of the doco are there (the PubkeyAcceptedKeyTypes is being picked 
up from the system-wide crypto policy, which are set to DEFAULT, which meets 
the specified 2048-bit RSA keys).

I've included all the logs with the string "ERROR" in this DropBox folder, 
along with a couple of other relevant(?) files: 
https://www.dropbox.com/sh/eymwdy8hzn3sa7z/AACscSP2eaFfoiN-QzyeEVfaa?dl=0

Could someone please be kind enough to point out where things are going wrong?

Cheers

Dulux-Oz
___
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/4P4RGXTBZHWT3YQ3PYOOIER7645OVQGS/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Christoph Timm


Hi all,

I updated my engine to 4.5.3.1 without any issues and want to update the 
self hosted engine (CentOS Stream 8).
There I run into the reported issues which I fix with the update of the 
please centos-release-ovirt45 package (8.7-3).
But still I have the issue with the ansible-core.2-13 which is not 
supported by the engine. Means dnf update is still failing.


Error:
 Problem: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting 
packages or '--skip-broken' to skip uninstallable packages or '--nobest' 
to use not only best candidate packages)


As you can see the correct version is installed but appstream is already 
providing a newer version which needs to be excluded (I guess).

dnf list | grep ansible-core
ansible-core.x86_64 2.12.7-1.el8 @appstream
ansible-core.x86_64 
2.13.3-1.el8   appstream


DNF looks happy if I run: dnf update --refresh --exclude=ansible-core

I guess it should be fine to run it like this?

Best regards
Christoph

Am 21.10.22 um 09:59 schrieb Martin Perina:

Hi Latchezar,

so there seems to be several issues according the error you have 
posted below:


1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so if 
this package is already installed on your machine, you need to 
downgrade it to ansible-core-2.12 before continuing with engine 
installation
2. If any of those rdo* packages are already installed on your 
machine, you need remote them manually before proceeding with engine 
installation
3. Please check that you really have installed only required 
repositories on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of 
ovirt-release45, which is 4.5.3.1. This is the version which blocks 
RDO packages to interfere with oVirt


Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  wrote:

Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will deal
with this.

Async upgrade is OK. The update of Standalone engine/CentOS Stream
release 8 shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails -
the result is below. Do you thing manual elimination of
rdo-related will solve it?

Thank you!

Best,

Latcho

Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022
06:47:31 AM EEST.

Error:

 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts
with ansible-core >= 2.13.0 provided by
ansible-core-2.13.3-1.el8.x86_64

- cannot install the best update candidate for package
ovirt-engine-4.5.3.1-1.el8.noarch

- cannot install the best update candidate for package
ansible-core-2.12.7-1.el8.x86_64

Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
openvswitch2.15, but none of the providers can be installed

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-119.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-106.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-110.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-115.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-117.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-22.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-23.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-24.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-27.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-30.el8s.x86_64

- package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes
openvswitch2.15 < 2.17 provided by
openvswitch2.15-2.15.0-32.el8s.x86_64

- package

[ovirt-users] LDAP auth and group members

2022-10-21 Thread Jiří Sléžka


Hi,

I have configured oVirt authentication against our MicroFocus/Novell 
eDirectory (edir) ldap. It is working fine on per user base. Now I am 
tried to set permissions per group but it seems does not work.


My CRO.properties

---
include = 

vars.server = ldap.
vars.port = 389
vars.user = cn=***
vars.password = ***

pool.default.serverset.single.server = ${global:vars.server}
pool.default.serverset.single.port = ${global:vars.port}
pool.default.auth.simple.bindDN = ${global:vars.user}
pool.default.auth.simple.password = ${global:vars.password}

pool.default.ssl.startTLS = true
pool.default.socketfactory.resolver.supportIPv6 = false

sequence-init.init.100-my-edir-init-vars = my-edir-init-vars
sequence.my-edir-init-vars.010.description = set baseDN
sequence.my-edir-init-vars.010.type = var-set
sequence.my-edir-init-vars.010.var-set.variable = simple_baseDN
sequence.my-edir-init-vars.010.var-set.value = o=su

search.default.search-request.derefPolicy = ALWAYS
---

I am able search groups in manager but users with permissions per group 
are unable to login with "The user *** with profile [CRO] is not 
authorized to perform login".


When I try debug it with

ovirt-engine-extensions-tool aaa login-user --profile=CRO 
--user-name=***


I can see common attributes (name, email,...) in PrincipalRecord but not 
any record mentioned group membership.


Group which holds this user has posixGroup objectClass and member 
attributes which points to dn of users.


There were also similar post in this list in 2019 which unfortunately 
was not much specific with solution


https://lists.ovirt.org/archives/list/users@ovirt.org/thread/PBQXDJGOZ2ET347YDZFSQPFJGMNSALHD/

Could any suggest how to better debug this or how to modify group search 
filter in my profile to work with member attribute?


Thanks in advance,

Jiri


smime.p7s
Description: S/MIME Cryptographic Signature
___
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/RPHPO4J42ZYX377KBSBC6QMKVJ26ZA66/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Martin Perina

Hi Latchezar,

so there seems to be several issues according the error you have posted
below:

1. ovirt-engine is not compatible with ansible-core-2.13 on EL8, so if this
package is already installed on your machine, you need to downgrade it to
ansible-core-2.12 before continuing with engine installation
2. If any of those rdo* packages are already installed on your machine, you
need remote them manually before proceeding with engine installation
3. Please check that you really have installed only required repositories
on your machine as mentioned in Installation guide:

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/index.html#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
4. Please make sure that you have installed the latest version of
ovirt-release45, which is 4.5.3.1. This is the version which blocks RDO
packages to interfere with oVirt

Regards,
Martin



On Fri, Oct 21, 2022 at 9:51 AM Latchezar Filtchev  wrote:

> Dear Martin,
>
>
>
> Not getting e-mails from ovirt list is my local issue. I will deal with
> this.
>
>
>
> Async upgrade is OK. The update of Standalone engine/CentOS Stream release
> 8 shows - Version 4.5.3.1-1.el8
>
>
>
> When executing ‘dnf update’ on standalone engine – update fails - the
> result is below. Do you thing manual elimination of rdo-related will solve
> it?
>
>
>
> Thank you!
>
> Best,
>
> Latcho
>
>
>
>
>
> Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022 06:47:31 AM
> EEST.
>
> Error:
>
>  Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with
> ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
>
>   - cannot install the best update candidate for package
> ovirt-engine-4.5.3.1-1.el8.noarch
>
>   - cannot install the best update candidate for package
> ansible-core-2.12.7-1.el8.x86_64
>
> Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires
> openvswitch2.15, but none of the providers can be installed
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64
>
>   - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15
> < 2.17 provided by

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Latchezar Filtchev

Dear Martin,

Not getting e-mails from ovirt list is my local issue. I will deal with this.

Async upgrade is OK. The update of Standalone engine/CentOS Stream release 8 
shows - Version 4.5.3.1-1.el8

When executing ‘dnf update’ on standalone engine – update fails - the result is 
below. Do you thing manual elimination of rdo-related will solve it?

Thank you!
Best,
Latcho


Last metadata expiration check: 3:56:58 ago on Fri 21 Oct 2022 06:47:31 AM EEST.
Error:
 Problem 1: package ovirt-engine-4.5.3.1-1.el8.noarch conflicts with 
ansible-core >= 2.13.0 provided by ansible-core-2.13.3-1.el8.x86_64
  - cannot install the best update candidate for package 
ovirt-engine-4.5.3.1-1.el8.noarch
  - cannot install the best update candidate for package 
ansible-core-2.12.7-1.el8.x86_64
Problem 2: package ovirt-openvswitch-2.15-4.el8.noarch requires 
openvswitch2.15, but none of the providers can be installed
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64
  - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 
2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64
  - cannot install the best update candidate for package 
ovirt-openvswitch-2.15-4.el8.noarch
  - cannot install the best update candidate for package 
openvswitch2.15-2.15.0-119.el8s.x86_64
Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires 
ovn-2021, but none of the providers can be installed
  - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 <

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

2022-10-21 Thread Martin Perina

Hi Gianluca,

In the Events view in webadmin there should be a message announcing that
host upgrade failed and more information could be found within specific log
file on oVirt Engine machine. Could you please share this log file?

Thanks,
Martin


On Thu, Oct 20, 2022 at 10:49 AM Gianluca Amato 
wrote:

> 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/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
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/A4WLHY6Q7K6JNA6U6DTUSFTFAR3ZRXDQ/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Martin Perina

Hi Latchezar,

yesterday we have released an async oVirt 4.5.3.1 version, which is fixing
this repository issue, so once you upgrade your ovirt-release45 package,
you should no longer need to do any manual actions. More info in
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LXCTQGKBF2UBENE2I27TVJSEZFNBUSGC/

Regards,
Martin


On Fri, Oct 21, 2022 at 9:02 AM Latchezar Filtchev  wrote:

> Dear David,
>
>
>
> Can you point where is this official workaround? May be I am missing
> responses you are talking about.
>
>
>
> Thank you!
>
> Best,
>
> Latcho
>
>
>
>
>
> *From:* David Johnson 
> *Sent:* Wednesday, October 19, 2022 4:42 PM
> *To:* Milan Zamazal 
> *Cc:* users 
> *Subject:* [ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3
>
>
>
> Thank you Milan,
>
>
>
> This is also the official workaround, based on other responses.
> ___
> 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/ADW64DEAZAKM3MH4GJ2DHPZ4BDPO2SSZ/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
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/BEJTMLXZHHHWFH4XK2YAHDCHO2M5G3MK/

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

2022-10-21 Thread Latchezar Filtchev

Dear David,

Can you point where is this official workaround? May be I am missing responses 
you are talking about.

Thank you!
Best,
Latcho


From: David Johnson 
Sent: Wednesday, October 19, 2022 4:42 PM
To: Milan Zamazal 
Cc: users 
Subject: [ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

Thank you Milan,

This is also the official workaround, based on other responses.
___
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/ADW64DEAZAKM3MH4GJ2DHPZ4BDPO2SSZ/

[ovirt-users] oVirt Node 4.5.3.1 Async update

2022-10-21 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 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..."

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] Re: Unable to delete snapshots on vm

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

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

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] LDAP auth and group members

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

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

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] Re: RPM issues updating Ovirt 4.5.2 to 4.5.3

[ovirt-users] oVirt Node 4.5.3.1 Async update

14 matches

Site Navigation

Mail list logo

Footer information