Bug 1304611

Summary:

Manager displays "The Hosted Engine Storage Domain doesn't exist. It should be imported into the setup."

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

Sistemas Amtega <sistemas-soporte-linux>

Component:

ovirt-engine

Assignee:

Roy Golan <rgolan>

Status:

CLOSED DUPLICATE

QA Contact:

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

3.6.0

CC:

ahoness, amureini, dfediuck, gklein, lsurette, rbalakri, rgolan, Rhev-m-bugs, sistemas-soporte-linux, yeylon, ykaul

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2016-02-07 08:03:30 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

SLA

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
sosreport from manager	none

Description Sistemas Amtega 2016-02-04 07:37:38 UTC

Description of problem:

Once the hosted engine is setup and running, the manager displays this message: "The Hosted Engine Storage Domain doesn't exist. It should be imported into the setup."

Version-Release number of selected component (if applicable):

rhev-hypervisor7-7.2-20160120.0.iso

How reproducible:

In our test platform this message is displayed from time to time in the event window.

Steps to Reproduce:
1. Setup hosted engine with RHEV-M appliance.

Actual results:

Te manager displays this message: "The Hosted Engine Storage Domain doesn't exist. It should be imported into the setup."

Expected results:

We don't know if this message is caused by a bad setup/config or by a bug in the manager.

Comment 1 Doron Fediuck 2016-02-04 09:24:58 UTC

Hi,
this is a standard message which indicates you need to create your first data storage domain. Once created, you'll be able to see more information (such as
the hosted engine VM).
Can you please try and report back?

Comment 2 Sistemas Amtega 2016-02-04 09:51:29 UTC

We already have created a data storage domain. In fact, we haver 192 virtual machines running on the Beta test platform.

Comment 3 Doron Fediuck 2016-02-04 13:09:41 UTC

The engine should import the HE VM after the first storage data domain is created and cluster compatibility level is changed to 3.6. This will make the HE VM visible if installation was completed correctly.
Can you please verify the cluster compatibility level is 3.6 and provide the engine log files?

Comment 4 Sistemas Amtega 2016-02-05 10:28:15 UTC

We are installing the beta from scratch, so logic says that by default the cluster should be created with 3.6 compatibility level. 

In any case, we have looked the cluster config and it is with 3.6 compatibility level.

I attach sosreport from manager.

Comment 5 Sistemas Amtega 2016-02-05 10:29:26 UTC

Created attachment 1121323 [details]
sosreport from manager

Comment 6 Roy Golan 2016-02-07 08:03:30 UTC

The name of the hosted engine storage domain according to the log is *stg-data-fc-he-0001* and the engine still expects *hosted_storage*. Bug 1294457 handles that already.

This can be quickly corrected with:

  psql --dbname=engine -U engine <<EOF
      select fn_db_add_config_value('HostedEngineStorageDomainName','stg-data-fc-he-0001', 'general');
      EOF

and a restart to ovirt-engine

*** This bug has been marked as a duplicate of bug 1294457 ***