On Wed, Jun 26, 2019 at 10:42 PM Strahil wrote:
>
> What about setting the date and time manually somewhere at 2016 on all hosts
> and blockking ntp at all ?
>
> Then the certs will be still valid and can be renewed ?
>
> Just asking... Not sure what will be the outcome.
Glad you asked.
What about setting the date and time manually somewhere at 2016 on all hosts
and blockking ntp at all ?
Then the certs will be still valid and can be renewed ?
Just asking... Not sure what will be the outcome.
Best Regards,
Strahil NikolovOn Jun 25, 2019 12:31, Yedidyah Bar David
wrote:
>
>
Il 26/06/2019 11:57, Yedidyah Bar David ha scritto:
On Tue, Jun 25, 2019 at 8:37 PM Stefano Danzi wrote:
Il 25/06/2019 14:26, Stefano Danzi ha scritto:
I don't remember to ever seen a question about this during
engine-setup,
but it could be.
In /etc/pki/vdsm/certs/ I can see an old cert and
On Tue, Jun 25, 2019 at 8:37 PM Stefano Danzi wrote:
>
> Il 25/06/2019 14:26, Stefano Danzi ha scritto:
> >
> >>> I don't remember to ever seen a question about this during
> >>> engine-setup,
> >>> but it could be.
> >>> In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
> >>>
>
Il 25/06/2019 14:26, Stefano Danzi ha scritto:
I don't remember to ever seen a question about this during
engine-setup,
but it could be.
In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
[root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
I don't remember to ever seen a question about this during engine-setup,
but it could be.
In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
[root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
/etc/pki/vdsm/certs/cacert.pem.20150205093608 -text'
Certificate:
On Tue, Jun 25, 2019 at 12:28 PM Stefano Danzi wrote:
>
>
>
> Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
> > On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
> >>
> >>
> >> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> >>> On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi
Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
I've found that this issue is related to:
On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
>
>
>
> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> > On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
> >> I've found that this issue is related to:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
> > Are you
Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
I've found that this issue is related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1648190
Are you sure?
That bug is about an old cert, generated by an old version, likely
before we
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
>
> I've found that this issue is related to:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
Are you sure?
That bug is about an old cert, generated by an old version, likely
before we fixed bug 1210486 (even though it's not mentioned
I've found that this issue is related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1648190
But i've no idea how fix it
Il 24/06/2019 18:19, Stefano Danzi ha scritto:
I've just upgraded my test environment from ovirt 4.2 to 4.3.4.
System has only one host (Centos 7.6.1810) and run a
12 matches
Mail list logo
