Dear All,
In our Ovirt Engine Infrastructure, recently we have received an alert for one
of our "Storage Domain"
The alert is as mentioned below
===
Storage domains with IDs [fb34e5b7-e850-4d66-ab47-3011d2000338] could not be
synchronized. To synchronize
On Wed, Feb 21, 2024 at 6:24 PM Gianluca Cecchi
wrote:
> Hello,
> I had a lab environment in 4.4.10, composed of only one host and local
> storage DC and with an external engine.
> I had 3 disks on this system, with OS in the first one and local storage
> domains in the second and third one.
> I
Hello,
I had a lab environment in 4.4.10, composed of only one host and local
storage DC and with an external engine.
I had 3 disks on this system, with OS in the first one and local storage
domains in the second and third one.
I detached the storage domains (I forgot to remove them afterwards)
I'm not aware of any specific issue about running engine on el9. It's just a
configuration that Red Hat QE never tested.
I'm not sure if it's covered by oVirt System Test CI on engine commits.
___
Users mailing list -- users@ovirt.org
To unsubscribe
Engine works fine on el9s
On 21/02/2024 16:24, Nathanaël Blanchet via Users wrote:
Hello,
According to official doc, only el8 is supported for engine.
So, has anyone experienced a successfull el9 installation and if not
what is the challenge for finalizing it?
Hello,
According to official doc, only el8 is supported for engine.
So, has anyone experienced a successfull el9 installation and if not
what is the challenge for finalizing it?
--
Nathanaël Blanchet
Administrateur Systèmes et Réseaux
Service Informatique et REseau (SIRE)
Département des
> Hi, for those who remember the Linux Counter project, if you'd like other
> to know you're using oVirt and know some details about your deployment,
> here's a way to count you in:
> https://ovirt.org/community/ovirt-counter.html
>
> Enjoy!
Just a reminder this still exists :-)
I noticed when doing the install of the engine it cant be done in the cockpit i
dont see the tab in the frame so I did the install command line no problem with
that. During the install of the engine it disconnects and in the messages it
just continues with node-ansible-async_wrapper.py [16052]
Yea it finally worked thanks
___
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:
The fix got merged into the 42.2.x branch:
https://github.com/pgjdbc/pgjdbc/commits/release/42.2/
So guess we just need to bump the dep in the pom.
But as far as I see the code doesn't use the PreferQueryMode flag, so
we're save.
Jean-Louis
On 21/02/2024 09:30, Fabrice Bacchella via Users
I think there is a typo in the announcement. 42.2.8 is 4 year old, 42.2.28 was
issued this night. That’s suspicious.
> Le 21 févr. 2024 à 09:24, Sandro Bonazzola a écrit :
>
> I'm not an expert on this topic, but according engine's pom we are using
> 42.2.27 which doesn't seem to be in the
I'm not an expert on this topic, but according engine's pom we are using
42.2.27 which doesn't seem to be in the list of the affected version on
https://github.com/advisories/GHSA-xfg6-62px-cxc2
Il giorno mer 21 feb 2024 alle ore 09:09 Fabrice Bacchella via Users <
users@ovirt.org> ha scritto:
>
Does oVirt is exposed to CVE-2024-1597 ?
To be exposed, the jdbc driver needs to be used with PreferQueryMode=SIMPLE. Is
that the situation ?___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy
13 matches
Mail list logo
