Re: hosted-engine --deploy --restore-from-file fails with error "Domain format is different from master storage domain format"
Hi Shani, on the productive cluster (Default) the compat level is 4.3 and on the cluster it's 4.3 too so I can't raise the level to update the format to V5. I added some screenshots. Regards Marcel On Tuesday, February 18, 2020 10:51:29 AM CET you wrote:
Hi Marcel, Can you make sure the DC and Cluster formats are V5? Maybe try to "update" them by editing the cluster first, and selecting the newest Compatibility Version available. Then, do the same for the DC.
If all versions/formats are of V5, and it still occurs, can you please share some screenshots so I'll have a look?
*Regards,*
*Shani Leviim*
On Mon, Feb 17, 2020 at 5:08 PM djagoo <dev@djagoo.io> wrote:
Hi Shani,
I just tried it.
I created a new DC and cluster, added a temporary host to this cluster which served as SPM. The new DC showed up as V5. Then I activated maintenance on one of the V4 SDs and detached it from my production domain. After I attached it to the V5 dummy domain it was updated to V5 format as you predicted. I detached it again but could not reattach it to the production domain "There are no compatible Storage Domains to attach to this Data Center". So this seems not to be the solution :(
Do you have another idea or am I doing something wrong?
Regards,
Marcel _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XV6WQNGS3LQU 3GWMR62MNZ5ENQA4BJQZ/
Hi Marcel, Before ovirt-engine-4.3.3.2, the 4.3 compatibility version was considered as V4, and from that version, it was considered as V5. Therefore, it seems that since your Default DC was created before that version, it was considered as V4. You can try to make it V5 by doing the following: - Edit the Default cluster, re-choose the 4.3 option on the 'Compatibility Version' field and press OK. - Do the same for the Default Data Center. I believe that your newer engine, which considers 4.3 as V5 format, will do the relevant update on your environment. *Regards,* *Shani Leviim* On Tue, Feb 18, 2020 at 12:08 PM <dev@djagoo.io> wrote:
Hi Shani,
on the productive cluster (Default) the compat level is 4.3 and on the cluster it's 4.3 too so I can't raise the level to update the format to V5.
I added some screenshots.
Regards
Marcel
Hi Marcel, Can you make sure the DC and Cluster formats are V5? Maybe try to "update" them by editing the cluster first, and selecting
On Tuesday, February 18, 2020 10:51:29 AM CET you wrote: the
newest Compatibility Version available. Then, do the same for the DC.
If all versions/formats are of V5, and it still occurs, can you please share some screenshots so I'll have a look?
*Regards,*
*Shani Leviim*
On Mon, Feb 17, 2020 at 5:08 PM djagoo <dev@djagoo.io> wrote:
Hi Shani,
I just tried it.
I created a new DC and cluster, added a temporary host to this cluster which served as SPM. The new DC showed up as V5. Then I activated maintenance on one of the V4 SDs and detached it from my production domain. After I attached it to the V5 dummy domain it was updated to V5 format as you predicted. I detached it again but could not reattach it to the production domain "There are no compatible Storage Domains to attach to this Data Center". So this seems not to be the solution :(
Do you have another idea or am I doing something wrong?
Regards,
Marcel _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XV6WQNGS3LQU
3GWMR62MNZ5ENQA4BJQZ/
Hi Shani, that didn't work. I edited the cluster, re-chose 4.3 and saved it, and then edited the DC, re-chose 4.3 and saved it. The SDs are still on V4 and V5 is not attachable. Regards Marcel
After three weeks the only possible solution I can see is - undeploying hosted engine from one of the hosts - removing the host from the cluster - creating a new DC - creating a new Cluster - recreate all networks etc. from the old DC in the new one - add the host - add a new temporary V5 SD serving as MasterSD - backup of the hosted-engine - enable global ha maintenance - shutdown of the hosted-engine - hosted-engine --deploy --restore-from-file using the new datacenter and cluster on the one host in the new DC - unattach V4 storage vom old DC reattach to the new DC and hope that all vm's are showing up on the new DC - adding the remaining 2 hosts to the new DC and reinstall/redeploy hosted-engine to them Do you think this could be the solution? Is it possible to move everything from the old DC to the new one by attaching the storage to it or am I loosing information about the vms (assigned MAC Addresses and so on)? Regards Marcel
Hi Marcel, That's basically it. Adding +Martin Perina <mperina@redhat.com>. Martin is there a way to keep the VM's assigned MAC addresses while migrating their SD? *Regards,* *Shani Leviim* On Wed, Feb 19, 2020 at 7:14 AM djagoo <dev@djagoo.io> wrote:
After three weeks the only possible solution I can see is
- undeploying hosted engine from one of the hosts - removing the host from the cluster - creating a new DC - creating a new Cluster - recreate all networks etc. from the old DC in the new one - add the host - add a new temporary V5 SD serving as MasterSD - backup of the hosted-engine - enable global ha maintenance - shutdown of the hosted-engine - hosted-engine --deploy --restore-from-file using the new datacenter and cluster on the one host in the new DC - unattach V4 storage vom old DC reattach to the new DC and hope that all vm's are showing up on the new DC - adding the remaining 2 hosts to the new DC and reinstall/redeploy hosted-engine to them
Do you think this could be the solution? Is it possible to move everything from the old DC to the new one by attaching the storage to it or am I loosing information about the vms (assigned MAC Addresses and so on)?
Regards
Marcel _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GDEK2BRBYFZ77O...
participants (3)
-
dev＠djagoo.io -
djagoo
-
Shani Leviim