[ovirt-users] Re: Upgrade from oVirt 4.5.4 to oVirt 4.5.5 - nothing provides selinux-policy >= 38.1.27-1.el9

2023-12-20 Thread Sandro Bonazzola
As the package has been built on CentOS Stream 9 you need a newer selinux
policy.
You can pick it from here:
https://kojihub.stream.centos.org/koji/buildinfo?buildID=2

Il giorno mer 20 dic 2023 alle ore 15:22 Devin A. Bougie <
devin.bou...@cornell.edu> ha scritto:

> Hi, All.  We're having trouble updating our 4.5.4 cluster to 4.5.5.  We're
> running a self-hosted engine on fully updated AlmaLinux 9 hosts, and get
> the following errors when trying to upgrade to 4.5.5.
>
> Any suggestions would be greatly appreciated.
>
> Many thanks,
> Devin
>
> --
> [root@lnxvirt01 ~]# dnf clean all
> 157 files removed
> [root@lnxvirt01 ~]# dnf update
> CLASSE Packages - x86_64
>
> 36 MB/s | 569 kB 00:00
> CentOS-9-stream - Ceph Pacific
>
>839 kB/s | 557 kB 00:00
> CentOS-9-stream - Gluster 10
>
>240 kB/s |  56 kB 00:00
> CentOS-9 - RabbitMQ 38
>
>354 kB/s | 104 kB 00:00
> CentOS Stream 9 - NFV OpenvSwitch
>
>   923 kB/s | 154 kB 00:00
> CentOS-9 - OpenStack yoga
>
>   5.7 MB/s | 3.0 MB 00:00
> CentOS Stream 9 - OpsTools - collectd
>
>   228 kB/s |  51 kB 00:00
> CentOS Stream 9 - oVirt 4.5
>
>   6.2 MB/s | 1.0 MB 00:00
> oVirt upstream for CentOS Stream 9 - oVirt 4.5
>
>1.0 kB/s | 7.5 kB 00:07
> AlmaLinux 9 - AppStream
>
>87 MB/s | 7.7 MB 00:00
> AlmaLinux 9 - BaseOS
>
> 72 MB/s | 2.4 MB 00:00
> AlmaLinux 9 - BaseOS - Debug
>
>9.9 MB/s | 1.9 MB 00:00
> AlmaLinux 9 - CRB
>
>67 MB/s | 2.3 MB 00:00
> AlmaLinux 9 - Extras
>
>1.5 MB/s |  17 kB 00:00
> AlmaLinux 9 - HighAvailability
>
> 29 MB/s | 434 kB 00:00
> AlmaLinux 9 - NFV
>
>56 MB/s | 1.0 MB 00:00
> AlmaLinux 9 - Plus
>
>2.5 MB/s |  22 kB 00:00
> AlmaLinux 9 - ResilientStorage
>
> 30 MB/s | 446 kB 00:00
> AlmaLinux 9 - RT
>
> 53 MB/s | 1.0 MB 00:00
> AlmaLinux 9 - SAP
>
>   874 kB/s | 9.7 kB 00:00
> AlmaLinux 9 - SAPHANA
>
>   1.3 MB/s |  13 kB 00:00
> Error:
>  Problem 1: cannot install the best update candidate for package
> ovirt-vmconsole-1.0.9-1.el9.noarch
>   - nothing provides selinux-policy >= 38.1.27-1.el9 needed by
> ovirt-vmconsole-1.0.9-3.el9.noarch from centos-ovirt45
>   - nothing provides selinux-policy-base >= 38.1.27-1.el9 needed by
> ovirt-vmconsole-1.0.9-3.el9.noarch from centos-ovirt45
>  Problem 2: package ovirt-vmconsole-host-1.0.9-3.el9.noarch from
> centos-ovirt45 requires ovirt-vmconsole = 1.0.9-3.el9, but none of the
> providers can be installed
>   - cannot install the best update candidate for package
> ovirt-vmconsole-host-1.0.9-1.el9.noarch
>   - nothing provides selinux-policy >= 38.1.27-1.el9 needed by
> ovirt-vmconsole-1.0.9-3.el9.noarch from centos-ovirt45
>   - nothing provides selinux-policy-base >= 38.1.27-1.el9 needed by
> ovirt-vmconsole-1.0.9-3.el9.noarch from centos-ovirt45
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
> to use not only best candidate packages)
> --
> ___
> 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/UDIAOQCVF7CP4TIEGD56AYY6VGEHHXS2/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING

Red Hat In-Vehicle Operating System

Red Hat EMEA 


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


[ovirt-users] Upgrade from oVirt 4.5.4 to oVirt 4.5.5 - nothing provides selinux-policy >= 38.1.27-1.el9

2023-12-20 Thread Devin A. Bougie
Hi, All.  We're having trouble updating our 4.5.4 cluster to 4.5.5.  We're 
running a self-hosted engine on fully updated AlmaLinux 9 hosts, and get the 
following errors when trying to upgrade to 4.5.5.  

Any suggestions would be greatly appreciated.

Many thanks,
Devin

--
[root@lnxvirt01 ~]# dnf clean all
157 files removed
[root@lnxvirt01 ~]# dnf update
CLASSE Packages - x86_64

  36 MB/s | 569 kB 00:00 
CentOS-9-stream - Ceph Pacific  

 839 kB/s | 557 kB 00:00 
CentOS-9-stream - Gluster 10

 240 kB/s |  56 kB 00:00 
CentOS-9 - RabbitMQ 38  

 354 kB/s | 104 kB 00:00 
CentOS Stream 9 - NFV OpenvSwitch   

 923 kB/s | 154 kB 00:00 
CentOS-9 - OpenStack yoga   

 5.7 MB/s | 3.0 MB 00:00 
CentOS Stream 9 - OpsTools - collectd   

 228 kB/s |  51 kB 00:00 
CentOS Stream 9 - oVirt 4.5 

 6.2 MB/s | 1.0 MB 00:00 
oVirt upstream for CentOS Stream 9 - oVirt 4.5  

 1.0 kB/s | 7.5 kB 00:07 
AlmaLinux 9 - AppStream 

  87 MB/s | 7.7 MB 00:00 
AlmaLinux 9 - BaseOS

  72 MB/s | 2.4 MB 00:00 
AlmaLinux 9 - BaseOS - Debug

 9.9 MB/s | 1.9 MB 00:00 
AlmaLinux 9 - CRB   

  67 MB/s | 2.3 MB 00:00 
AlmaLinux 9 - Extras

 1.5 MB/s |  17 kB 00:00
AlmaLinux 9 - HighAvailability  

  29 MB/s | 434 kB 00:00 
AlmaLinux 9 - NFV   

  56 MB/s | 1.0 MB 00:00 
AlmaLinux 9 - Plus  

 2.5 MB/s |  22 kB 00:00 
AlmaLinux 9 - ResilientStorage  

  30 MB/s | 446 kB 00:00 
AlmaLinux 9 - RT

  53 MB/s | 1.0 MB 00:00 
AlmaLinux 9 - SAP   

 874 kB/s | 9.7 kB 00:00 
AlmaLinux 9 - SAPHANA   

 1.3 MB/s |  13 kB 00:00 
Error:  
 Problem 1: cannot install the best update candidate for package 
ovirt-vmconsole-1.0.9-1.el9.noarch
  - nothing provides selinux-policy >= 38.1.27-1.el9 needed by 
ovirt-vmconsole-1.0.9-3.el9.noarch from centos-ovirt45
  - nothing provides selinux-policy-base >= 38.1.27-1.el9 needed by 
ovirt-vmconsole-1.0.9-3.el9.noarch from 

[ovirt-users] Re: iSCSI Storage Domain Issues - Please Help

2023-12-20 Thread Patrick Dubois via Users
Have you reviewed the engine-setup logs?   There might be something 
interesting there.


Pat.

On 2023-12-20 05:07, Matthew J Black wrote:

Hi Guys & Gals,

So I've been researching this issue online for a couple of days now and I can't 
seem to find a solution - so I'm hoping you kind people here can help.

We're running oVirt (on Rocky 8, at the moment) with a iSCSI back-end provided 
by Ceph (Quincy, for the record). Everything from the Ceph-end looks AOK.

However, none of the oVirt Hosts (and therefore the VMs) can connect to the Ceph iSCSI 
RBD Images (oVirt Storage Domains), and only one or two of the Hosts can log into the 
Ceph iSCSI Target - the others throw a "Failed to setup iSCSI subsystem" error.

All of the existing iSCSI Storage Domains are in Maintenance mode, and when I try to do 
*anything* to them the logs spit out a "Storage domain does not exist:" message.

I also cannot create a new iSCSI Storage Domain for a new Ceph pool - again, 
oVirt simply won't/can't see it, even though it clearly visable in the iSCSI 
section of the Ceph Dashboard (and in gwcli on the Ceph Nodes).

All of this started happening after I ran an update of oVirt - including an "engine 
setup" with a full engine-vacuum. Nothing has changed on the Ceph-end.

So I'm looking for help on 2 issues, which or may not be related:

1) Is there a way to "force" oVirt Hosts to log into iSCSI targets? This will 
mean all of the oVirt Hosts will be connected to all of the Ceph iSCSI Gateways.

2) I'm thinking that *somehow* the existing "Storage Domains" registered in oVirt have 
become orphaned, so they need to be "cleaned up" - is there a cli way to do this (I don't 
mind digging into SQL as I'm an old SQL engineer/admin from way back). Thoughts on how to do this - 
and if it should be done at all?

Or should I simple detach the Storage Domain images from the relevant VMs and 
destroy the Storage Domains, recreate them (once I can get the oVirt Hosts to 
log back into the Ceph iSCSI Gateways), and then reattach the relevant images 
to the relevant VMs? I mean, after all, the data is good and available on the 
Ceph SAN, so there is only a little risk (as far as I can see) - but there are 
a *hell* of a lot of VMs to do to do this  :-)

Anyway, any and all help, suggestions, gotchas, etc, etc, etc, are welcome.  :-)

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

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


[ovirt-users] Re: oVirt 4.6 OS versions

2023-12-20 Thread Matthew J Black
Another +1 - We've been using Rocky (8) for a few years now and its been great.

(Yes, we're prep-ing to update to RL9 at the moment, but we've had a "minor" 
iSCSI connectivity issue just raise its ugly head so we're dealing with that 
right now  :-(  )

And for the record: My personal ambition is to contribute to oVirt as soon as I 
can "clear the decks" with some other stuff first, for what its worth.  :-)
___
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/AGOBVUQU6FX6YDCDSO52CUBLALV4TUR4/


[ovirt-users] iSCSI Storage Domain Issues - Please Help

2023-12-20 Thread Matthew J Black
Hi Guys & Gals,

So I've been researching this issue online for a couple of days now and I can't 
seem to find a solution - so I'm hoping you kind people here can help.

We're running oVirt (on Rocky 8, at the moment) with a iSCSI back-end provided 
by Ceph (Quincy, for the record). Everything from the Ceph-end looks AOK.

However, none of the oVirt Hosts (and therefore the VMs) can connect to the 
Ceph iSCSI RBD Images (oVirt Storage Domains), and only one or two of the Hosts 
can log into the Ceph iSCSI Target - the others throw a "Failed to setup iSCSI 
subsystem" error.

All of the existing iSCSI Storage Domains are in Maintenance mode, and when I 
try to do *anything* to them the logs spit out a "Storage domain does not 
exist:" message.

I also cannot create a new iSCSI Storage Domain for a new Ceph pool - again, 
oVirt simply won't/can't see it, even though it clearly visable in the iSCSI 
section of the Ceph Dashboard (and in gwcli on the Ceph Nodes).

All of this started happening after I ran an update of oVirt - including an 
"engine setup" with a full engine-vacuum. Nothing has changed on the Ceph-end.

So I'm looking for help on 2 issues, which or may not be related:

1) Is there a way to "force" oVirt Hosts to log into iSCSI targets? This will 
mean all of the oVirt Hosts will be connected to all of the Ceph iSCSI Gateways.

2) I'm thinking that *somehow* the existing "Storage Domains" registered in 
oVirt have become orphaned, so they need to be "cleaned up" - is there a cli 
way to do this (I don't mind digging into SQL as I'm an old SQL engineer/admin 
from way back). Thoughts on how to do this - and if it should be done at all?

Or should I simple detach the Storage Domain images from the relevant VMs and 
destroy the Storage Domains, recreate them (once I can get the oVirt Hosts to 
log back into the Ceph iSCSI Gateways), and then reattach the relevant images 
to the relevant VMs? I mean, after all, the data is good and available on the 
Ceph SAN, so there is only a little risk (as far as I can see) - but there are 
a *hell* of a lot of VMs to do to do this  :-)

Anyway, any and all help, suggestions, gotchas, etc, etc, etc, are welcome.  :-)

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