On Mon, Oct 26, 2015 at 6:26 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
tried latest version with http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm that used ovirt-hosted-engine-setup-1.3.0-1.el7.centos.noarch vdsm-4.17.10-0.el7.centos.noarch
I presume it is the latest RC available.
after install, inside the sh engine webadmin portal I see:
oVirt Engine Version: 3.6.0.1-1.el7.centos
During storage configuration I choose:
--== STORAGE CONFIGURATION ==--
During customization use CTRL-D to abort. Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:
Please specify the full shared storage connection path to use (example: host:/path): ovc71 .localdomain.local:/SHE_DOMAIN ESC[92m[ INFO ]ESC[0m Installing on first host Please provide storage domain name. [hosted_storage]: she_sdomain Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI. Please enter local datacenter name [hosted_datacenter]: she_datacenter
I don't understand the meaning of the sentence above:
Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.
It's just an internal label. I think we can just remove that question always using the default value and nothing will change.
How is the chosen "she_datacenter" name related with the "Default" datacenter where the hypervisor is put in? Do I have to manually create it (I don't see this se_datacenter in webadmin portal)?
Also, I know there is open bug
https://bugzilla.redhat.com/show_bug.cgi?id=1269768
But it seems I'm not able to to import the storage domain... In events, when I import, I have the sequence
Storage Domain she_sdomain was added by admin@internal VDSM ovc71.localdomain.local command failed: Cannot acquire host id: (u'9f1ec45d-0c32-4bfc-8b67-372d6f204fd1', SanlockException(22, 'Sanlock lockspace add failure', 'Invalid argument')) Failed to attach Storage Domains to Data Center Default. (User: admin@internal) Failed to attach Storage Domain she_sdomain to Data Center Default. (User: admin@internal)
What should be the flow to compensate the bug? Do I have actually to attache it to "Default" datacenter or what? Is it expected to be fixed before 3.6?
Postponing to 3.6.1 not being identified as a blocker. You can try to add the first additional storage domain for other VMs. The datacenter should came up and at that point you try importing the hosted-engine storage domain. You cannot add other VMs to that storage domain neither you'll can when the auto-import will work.
Thanks, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users