Just created a test data center. Now, when I try to add/create a new storage
domain there is V4 format for the existing domain and V5 for the new data
center.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.or
Hi Marcel,
For the 4.3 DC version, since 4.3.3, the storage format was changed to V5.
Till that version, the storage format for 4.3 DCs was V4.
Since your SDs were created before 4.3.3, their storage format should be V4.
In order to upgrade this format, you can try to detach those storage
domains
Hi Shani,
thanks for your help. The master SD is the one the hosted engine is on. I can't
put it to maintenance and attach it to another domain. But I`ll try this
procedure with one of the oder SDs. If it works: is there a way to change the
master domain to one of the others or is it always the
Basically, in case the Master SD is down, that function should move to the
other SD on the same DC.
Taken from [1]:
To change the Master Storage Domain to another specific Storage Domain, the
below steps need to be followed:
* Put all storage domains except the Master storage domain and the one t
Hi Shani,
in theory it's exactly you have quoted.
In reality ... that's not what we all thought about :)
I had issues with the master domain role.
Djagoo,
if you have issues - just poweroff and power on the engine.
Upon 5-6th time it will decide to change it :)
Best Regards,
Strahil Nikolov
I tried to implement gluster post install. For me it was a disaster. I rebuilt
the engine host and deployed without gluster. I will try it in the future but
it will be a ground up deployment.
I f you disable gluster and the update the cluster again with all hosts, it
may come back to life.
I
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 updat
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:
- E
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
___
Users mailing list -- users@ovirt.org
To unsubscribe
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 serv
Hi Marcel,
That's basically it.
Adding +Martin Perina .
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 wrote:
> After three weeks the only possible solution I can see is
>
> - undeployi
11 matches
Mail list logo
