hello
I have a problem to log in to ovirt-engine manager in my browser
the warning message in the browser display me this text:
PKIX path validation failed: java.security.cert.CertPathValidatorException:
validity check failed
to solve this problem I am offered to run engine-setup
and here is a
On Wed, Feb 16, 2022 at 9:18 PM Nir Soffer wrote:
>
> On Wed, Feb 16, 2022 at 5:12 PM Nir Soffer wrote:
> >
> > On Wed, Feb 16, 2022 at 10:10 AM Pablo Olivera wrote:
> > >
> > > Hi community,
> > >
> > > We're dealing with an issue as we occasionally have random reboots on
> > > any of our
I forgot to enroll the certificate,
The connection between the engine and the nodes is broken.
I turned off all vms.
I turned the clock back and enrolled everything was fine but I was a little
nervous
___
Users mailing list -- users@ovirt.org
To
On Wed, Feb 16, 2022 at 5:12 PM Nir Soffer wrote:
>
> On Wed, Feb 16, 2022 at 10:10 AM Pablo Olivera wrote:
> >
> > Hi community,
> >
> > We're dealing with an issue as we occasionally have random reboots on
> > any of our hosts.
> > We're using ovirt 4.4.3 in production with about 60 VM
Hello,
I was familiar with the ansible fetch_nested/nested_attributes to get
additionnal information from API.
Recently it has been deprecated in order to be replaced by the
"follow(s)" verb.
I understand it will follow the links into the schema definition of the
object like:
On Wed, Feb 16, 2022 at 10:10 AM Pablo Olivera wrote:
>
> Hi community,
>
> We're dealing with an issue as we occasionally have random reboots on
> any of our hosts.
> We're using ovirt 4.4.3 in production with about 60 VM distributed over
> 5 hosts. We've a virtualized engine and a DRBD storage
Il giorno mer 16 feb 2022 alle ore 13:33 Yedidyah Bar David
ha scritto:
> On Wed, Feb 16, 2022 at 2:09 PM Gianluca Merlo
> wrote:
> >
> > Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David <
> d...@redhat.com> ha scritto:
> >>
> >> On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <
>
>The impression I've got from this mailing list is they are
intentional design decisions to enforce "correctness" of the cluster.
My understanding of cluster (ever since the VAX) is that it's a fault-tolerance
mechanism and that was originally one of the major selling points of these
Hi,
Let’s say that backup of ovirt engine is done once every day, for example 6 AM
using engine-backup tool.
Then during the day the changes are made that not only influence the database,
but actually influence Libvirt/KVM/QEMU
(create/delete VMs,snapshots, disks, ).
Now let’s say at 18:00 an
On Wed, Feb 16, 2022 at 2:09 PM Gianluca Merlo wrote:
>
> Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David
> ha scritto:
>>
>> On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo
>> wrote:
>> >
>> > Hi Jonas,
>> >
>> > I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am
Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David
ha scritto:
> On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo
> wrote:
> >
> > Hi Jonas,
> >
> > I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am
> trying to upgrade to the latest one, and have this issue. I read
Hi,
Thanks for your answer.
On the other nodes there are no errors in this period.
In the Cisco log there are only link-down errors due to the restart of
'nodo1'. There is no error before. I attach the Cisco log during this
period.
We use bond between nodo1 and Cisco switch. The storage is
Hello, Pablo.
It looks like nodo1 have lost connection with the storage (sanlock on nodo1
can't renew leases), then nodo1 has been reset by the watchdog.
Are there any errors in logs on the other nodes at this period (15:02 - 15:03)?
Are there any errors (near 15:02:13) in cisco9000's log (except
Le 15/02/2022 à 15:01, Arik Hadas a écrit :
On Tue, Feb 15, 2022 at 12:26 PM Nathanaël Blanchet
wrote:
Le 15/02/2022 à 10:32, Arik Hadas a écrit :
On Mon, Feb 14, 2022 at 11:29 PM Nathanaël Blanchet
wrote:
Le 14 févr. 2022 21:09, Arik Hadas a écrit :
Check on /var/lib/iscsi for session records. Check both engine and
Hypervisors.
I'm not sure if group 36 has to be used for iSCSI, so I'm sorry for misleading
you. I think this grouping is only for the TrueNAS, but I'm not sure.
Best Regards,Strahil Nikolov
On Wed, Feb 16, 2022 at 10:28,
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo wrote:
>
> Hi Jonas,
>
> I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am trying
> to upgrade to the latest one, and have this issue. I read through
>
>
>
Ok. The nfs share with the vdsm group is working. But the intent is to
switch to iSCSI. The little bit of documentation about iSCSI mentions
nothing about vdsm or group 36. That gives me something to work with at
least.
Any ideas about how to clean up the mess left by the first attempt? I'm not
17 matches
Mail list logo
