For anyone in the future looking for this solution, look at my post in this
other thread:
https://lists.ovirt.org/archives/list/us...@ovirt.org/thread/JEW5WIRD67WMF6TVG7367ZMSHX2KYGGV/
Full credit to the poster before me there that was the final step to finding
what I needed to make it work for
> On 26 Sep 2018, at 19:42, Dan Kenigsberg wrote:
>
>
>
>> On Wed, Sep 26, 2018 at 6:35 PM Edward Haas wrote:
>> I should have known better.
>> Deleting /etc/pki/vdsm and re-installing VDSM solved it.
>>
>> There is probably a smarter/simpler way to do this (delete the folder and
>> run 'vd
On Thu, Sep 27, 2018 at 12:31 AM Edward Haas wrote:
>
>
> On 26 Sep 2018, at 19:42, Dan Kenigsberg wrote:
>
>
>
> On Wed, Sep 26, 2018 at 6:35 PM Edward Haas wrote:
>>
>> I should have known better.
>> Deleting /etc/pki/vdsm and re-installing VDSM solved it.
>>
>> There is probably a smarter/sim
On Wed, Sep 26, 2018 at 6:35 PM Edward Haas wrote:
> I should have known better.
> Deleting /etc/pki/vdsm and re-installing VDSM solved it.
>
> There is probably a smarter/simpler way to do this (delete the folder and
> run 'vdsm-tool configure --force'?).
>
yes, more specifically: `vdsm-tool co
I should have known better.
Deleting /etc/pki/vdsm and re-installing VDSM solved it.
There is probably a smarter/simpler way to do this (delete the folder and
run 'vdsm-tool configure --force'?).
Thanks,
Edy.
On Wed, Sep 26, 2018 at 6:16 PM Edward Haas wrote:
> Hi,
>
> I have a VM which acts a
