On Tue, Aug 3, 2021 at 5:51 PM Sketch <[email protected]> wrote:
>
> I currently have two clusters up and running under one engine.  An old
> cluster on 4.3, and a new cluster on 4.4.  In addition to migrating from
> 4.3 to 4.4, we are also migrating from glusterfs to cephfs mounted as
> POSIX storage (not cinderlib, though we may make that conversion after
> moving to 4.4).  I have run into a strange issue, though.
>
> On the 4.3 cluster, migration works fine with any storage backend.  On
> 4.4, migration works against gluster or NFS, but fails when the VM is
> hosted on POSIX cephfs.

What do you mean by "fails"?

What is the failing operation (move disk when vm is running or not?)
and how does it fail?

...
> It appears that the VM fails to start on the new host, but it's not
> obvious why from the logs.  Can anyone shed some light or suggest further
> debugging?

You move the disk when the vm is not running, and after the move the vm will
not start?

If this is the issue, you can check if the disk was copied correctly by creating
a checksum of the disk before the move and after the move.

Here is example run from my system:

$ cat ~/.config/ovirt.conf
[myengine]
engine_url = https://engine-dev
username = admin@internal
password = mypassword
cafile = /etc/pki/vdsm/certs/cacert.pem

$ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/checksum_disk.py
-c myengine 3649d84b-6f35-4314-900a-5e8024e3905c
{
    "algorithm": "blake2b",
    "block_size": 4194304,
    "checksum":
"d92a2491f797c148e9a6c90830ed7bd2f471099a70e931f7dd9d86853d650ece"
}

See 
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/checksum_disk.py

Nir
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/KLD5NMFNJGBXEXUPVQCD4BHQXZXO4RHF/

Reply via email to