Interesting.
You are right but :-)
Scenario:
1. Empty DC and Cluster.
2. Creation of the storage domain type data based on gluster. This domain storage as first becomes a master storage domain.
3. After previous step, ovirt manager imports domain storage where resides hosted engine.
Thats all.

After reboot of the hypervisor (vm hosted engine power off state  before) situation has changed because as I've wrote earlier appeared a problem with access to gluster service.

Right now I don't know how to becomes my original master storage domain as previously.
 Even If I've made new data storage domain master DS not floating from hosted_storage.
Master SD will stay on the hosted_storage for ever :-(
Am I right?
Maybe not, but I don't know the different procedure then create new domain and master SD amend to maintenance mode.

2016-02-23 17:13 GMT+01:00 Simone Tiraboschi <stirabos@redhat.com>:


On Tue, Feb 23, 2016 at 4:19 PM, Dariusz Kryszak <dariusz.kryszak@gmail.com> wrote:
Hi folks,
I have a question about master domain when I'm using hosted engine deployment.
At the beginning I've made deployment on NUC (small home installation) with hosted engine on the nfs share from NUC host. I've configured FS gluster on the same machine and used it for master domain and iso domain. Lets say All-in-ONE.
After reboot happened something strange. Log says that master domain is not available and has to become on the hosted_storage. This is not ok in my opinion. I know that behavior because master doamin is not available, has been migrated to other shareable (in this case hosted_domain is nfs ).
Do you thing, that should be locked in this particular case means when available is only hosted_storage? Right now it is not possible to change this situation because hosted engine resides on the hosted_storage. I Can't migrate it. 


It could happen only after the hosted-engine storage domain got imported by the engine but to do that you need an additional storage domain which will become the master storage domain.
In the past we had a bug that let you remove the last regular storage domain and it the case the hosted-engine would become the master storage domain and as you pointed out that was an issue.

Now it should be fixed. If it just happened again just because you gluster regular storage domain wasn't available is not really fixed.
Adding Roy here.
Dariusz, which release are you using? 


 
jezyk

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





--
Dariusz Kryszak