Oh no! :) just posted here and an invalid certificate message came
___
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:/
> On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users wrote:
>
>
> Hi,
>
> Enroll certificate function re-enrolls certificates only hosts. If your
> engine certificate is going to expire, then you need to run engine-setup to
> renew engine certificate.
>
> Regards,
> Martin
Oh im assume, tha
> On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users wrote:
>
>
> Hi,
>
> Enroll certificate function re-enrolls certificates only hosts. If your
> engine certificate is going to expire, then you need to run engine-setup to
> renew engine certificate.
>
> Regards,
> Martin
Hi Martin! No, t
On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users
wrote:
> Hi there! I have a problem to enroll host certificate.
>
Hi,
Enroll certificate function re-enrolls certificates only hosts. If your
engine certificate is going to expire, then you need to run engine-setup to
renew engine certificat
El 2022-03-28 13:12, Nir Soffer escribió:
On Mon, Mar 28, 2022 at 11:01 AM wrote:
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
> On Wed, Mar 23, 2022 at 3:09 PM wrote:
>> We're running oVirt 4.4.8.6. We have uploaded a qcow2 image
>> (metasploit
>> v.3, FWIW)
>
> Is it Metasploitable3-0
On Tue, Mar 29, 2022 at 12:21 PM Vladimir Belov wrote:
>
>
> I'm trying to deploy oVirt from a self-hosted engine, but at the last step I
> get an engine startup error.
>
> [ INFO ] TASK [Wait for the engine to come up on the target VM]
> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120
When I try to deploy the engine using self-hosted-engine technology, I get an
error at the end of the installation.
[ INFO ] TASK [Wait for the engine to come up on the target VM]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
"cmd": ["hosted-engine", "--vm-status",
I'm trying to deploy oVirt from a self-hosted engine, but at the last step I
get an engine startup error.
[ INFO ] TASK [Wait for the engine to come up on the target VM]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
"cmd": ["hosted-engine", "--vm-status", "--json"
Hello everyone. I have a Gluster distributed replication cluster deployed. The
cluster - store for ovirt. For bricks - VDO over a raw disk. When discarding
via 'fstrim -av' the storage hangs for a few seconds and the connection is
lost. Does anyone know the best practices for using TRIM with VDO
9 matches
Mail list logo