ls -l /rhev/data-center/mnt/glusterSD/*/*/images/*
# any under "engine volume" that are owned by root chown and chmod as
vdsm:kvm 660
# then engine should be able to start.
On Tue, Feb 12, 2019 at 4:43 PM Endre Karlson
wrote:
> I Also tried to run
> service vdsmd stop
> vdsm-tool configure
I Also tried to run
service vdsmd stop
vdsm-tool configure --force
service vdsmd start
and then restart the ha agent on all nodes but it doesnt help, the upgraded
to 4.3 node is still not able to start hte engine.
/ E
Den tir. 12. feb. 2019 kl. 22:01 skrev Endre Karlson <
Yes that seems correct, but is there no way to work around it ?
Den tir. 12. feb. 2019 kl. 06:24 skrev Sahina Bose :
>
>
> On Tue, Feb 12, 2019 at 10:51 AM Endre Karlson
> wrote:
>
>> It's a upgrade from 4.2.x < latest version of 4.2 series. I upgraded by
>> adding the 4.3 repo and doing the
On Tue, Feb 12, 2019 at 10:51 AM Endre Karlson
wrote:
> It's a upgrade from 4.2.x < latest version of 4.2 series. I upgraded by
> adding the 4.3 repo and doing the steps on the upgrade guide page
> https://www.ovirt.org/release/4.3.0/#centos--rhel
>
Seems like you're running into
It's a upgrade from 4.2.x < latest version of 4.2 series. I upgraded by
adding the 4.3 repo and doing the steps on the upgrade guide page
https://www.ovirt.org/release/4.3.0/#centos--rhel
Den man. 11. feb. 2019 kl. 23:35 skrev Greg Sheremeta :
> Hi,
>
> Is this an upgrade or a fresh
Hi,
Is this an upgrade or a fresh installation? What version? What installation
or upgrade commands / methods did you use?
Best wishes,
Greg
On Mon, Feb 11, 2019 at 5:11 PM Endre Karlson
wrote:
> https://paste.ubuntu.com/p/BrmPYRKmzT/
>
6 matches
Mail list logo
