Description of problem: If during hosted-engine --deploy a different name than hosted_storage is chosen for the Storage Domain Name, this SD does not get imported to RHEV-M. Even after importing manually the Hosted Engine does not get imported to the Virtual Machines Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.3.1.4-1.el7ev.noarch ovirt-hosted-engine-ha-1.3.3.6-1.el7ev.noarch How reproducible: always Steps to Reproduce: 1. Create new hosted engine environment with hosted-engine --deploy 2. Chose a different name for hosted_storage, e.g. HE_storage 3. Create a Master Storage Domain in RHEV after the setup is complete Actual results: The HE_storage domain is not shown in Storage Tab. Even after importing it manually the Hosted Engine is not imported and not shown in the Virtual Machines Tab. Unfortunately even a VM Import is not available on that Storage Domain. Expected results: After the Datacenter is initialized the Storage Domain should get automatically activated and the Hosted Engine VM should get automatically imported. Additional info: Even if the name of the Storage Domain is not changed, you still need to activate it manually. But in this case the Hosted Engine VM is imported.
On 3.6.3 you can use engine-config -s HostedEngineStorageDomainName=SD_NAME and restart the engine. all should be imported. (you would need to destroy the current import domain and not wipe of course) The long run fix should be to stop depending on the name and that could be done easily by the auto-import - - vm monitoring detects a vm from vdsm with name hostedEngine - looking at the disk list we can see the domain ID - auto import flow should be invoked with that domain ID (rather than a config key) - engine must 'label' that domain as a hosted engine domain - either by config value keeping the id or extra metadata on the domain column in db. Using a config value means we would have to set the config value during runtime, on detecting it from vm details. Using domain extra data on domain is unsupported. Don't know if storage are planning extra metadata on domains on storage_domain_static This would solve Bug 1294457 as well.
I'm pretty sure there might be a slightly different but similar issue if you rename the cluster.
If you still think it should be fixed quickly let me know. Meanwhile you can use the engine-config key to make the engine look for you renamed storage domain. See https://bugzilla.redhat.com/show_bug.cgi?id=1294457#c14
Hi Roy, I will test the workaround as soon as I find some time and if it works, I am fine for a short term fix. I would create a KBase then as well describing the workaround in C#14. Thanks, Martin
Thanks, waiting for your feedback.
Somehow my update got lost. So I provide it again: As hosted-engine --deploy does no longer ask for the HE-StorageDomain Name, there can be no loonger any confusion. So I tried to install a current RHEV 3.6 environment, and that did no longer even allow me to supply a name for the HE-SD. As such I think this case can no longer be hit (besides by forcefully changing things in the SD itself before it gets imported). As such I think this Bug can be closed. Kind regards, Martin
*** Bug 1294457 has been marked as a duplicate of this bug. ***
Verified on rhevm-4.0.1.1-0.1.el7ev.noarch 1) Deploy hosted-engine with answer file that include: ... OVEHOSTED_STORAGE/storageDomainName=str:test_storage ... 2) Add master storage domain 3) Wait for HE auto import PASS
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html