On Mon, Aug 26, 2019 at 6:42 PM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Mon, Aug 26, 2019 at 6:40 PM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com>
wrote:
>
> It seems that these steps below solved the problem (donna what it was
> though..).
> Based on this similar (No worthy mechs found) I found inspiration from:
>
>
https://lists.ovirt.org/pipermail/users/2017-January/079009.html
>
>
> [root@ovirt01 ~]# vdsm-tool configure
>
> Checking configuration status...
>
> abrt is not configured for vdsm
> Managed volume database is already configured
> lvm is configured for vdsm
> libvirt is already configured for vdsm
> SUCCESS: ssl configured to true. No conflicts
> Manual override for multipath.conf detected - preserving current
> configuration
> This manual override for multipath.conf was based on downrevved template.
> You are strongly advised to contact your support representatives
>
> Running configure...
> Reconfiguration of abrt is done.
>
> Done configuring modules to VDSM.
> [root@ovirt01 ~]#
>
> [root@ovirt01 ~]# systemctl restart vdsmd
>
>
BTW: what are the effects of the command "vdsm-tool configure"? Is it
a
command meant to be used nornally from command line?
Just to know for the future.
Thanks,
Gianluca