Re: [ovirt-users] ovirt4.0.1 and new node, migration fails

ok, I will raise a bug. Yes it is very frustrating just having button not work without explanation. I don't know if this is related, the new host that I am having troubles with is running 4.0.1.1-1, other other host is running 4.0.0.6-1 I was planning on migrating VMs then upgrade the older host. Also Cluster is still in 3.6 mode, also waiting for upgrade of older node. All storage domains are on older node, its the NFS server. hmm, just retried migration so I could get vdsm logs from both hosts. 1 VM worked, the other 3 failed. And I still can't assign VMs to new node. VM that worked: f4cd4891-977d-44c2-8554-750ce86da7c9 Not sure what's special about it. It and 45f4f24b-2dfa-401b-8557-314055a4662c are clones from same template. Attaching logs from 2 nodes and engine now. On 7/29/16 4:00 AM, Michal Skrivanek wrote: Cloud Services for Business www.j2.com j2 | eFax | eVoice | FuseMail | Campaigner | KeepItSafe | Onebox This email, its contents and attachments contain information from j2 Global, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is prohibited. If you have received this email in error please notify the sender by reply e-mail and delete the original message and any copies. (c) 2015 j2 Global, Inc. All rights reserved. eFax, eVoice, Campaigner, FuseMail, KeepItSafe, and Onebox are registered trademarks of j2 Global, Inc. and its affiliates.