Hi Christopher,

Thanks for raising the issue. It sounds like the issue you are referring to is related to the fix of https://bugzilla.redhat.com/show_bug.cgi?id=1261996.

Adding some more people who should be involved.

On Fri, Oct 9, 2015 at 9:42 PM, Christopher Miersma <miersma@ualberta.ca> wrote:

Hi All,

I'm having an issue with the current release candidate for 3.6, running on CentOS 7. I'm trying to install the hosted engine on fibre channel storage. I can successfully install the VM, and get everything up and running, but the hosted engine VM itself does not appear in the web interface, nor does the storage domain on which the hosted engine's disks reside appear. When I create a new storage domain on the SAN, I can see the LUN on which the hosted engine resides, but it is greyed out. When I first started the cluster and got the host and engine VM installed and running, it gave me the message " The Hosted Engine Storage Domain doesn't exist. It shoudl be imported into the setup." I've tried importing and attaching the storage domain, but it simply doesn't appear in the interface to allow me to import it. I've tired every Attach/Import/Activate screen that I could find. I've also opened a bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1267337), but with no success so far.

Has anyone else had a similar issue? Can you import the hosted engine storage domain after setup, and if so on what kind of storage? From some of the posts I've seen, it looks like people are getting it to work with NFS and maybe iSCSI, but I haven't seen anyone else mention Fibre Channel.

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