Bug 1739134 - Error creating local storage domain: Internal Engine Error.
Summary: Error creating local storage domain: Internal Engine Error.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.3.5.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.3.6
: 4.3.6.3
Assignee: shani
QA Contact: Evelina Shames
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-08 15:13 UTC by christian_barr
Modified: 2019-09-26 19:43 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.3.6.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:28 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.3+


Attachments (Terms of Use)
Engine log containing errors. (246.60 KB, text/plain)
2019-08-08 15:13 UTC, christian_barr
no flags Details
Engine log - New flow (1.03 MB, text/plain)
2019-08-28 07:50 UTC, Evelina Shames
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 102616 0 'None' MERGED webadmin: Set value of storage format for a local SD 2020-02-06 13:57:04 UTC
oVirt gerrit 102626 0 'None' MERGED webadmin: Set value of storage format for a local SD 2020-02-06 13:57:04 UTC

Description christian_barr 2019-08-08 15:13:25 UTC
Created attachment 1601822 [details]
Engine log containing errors.

Description of problem:
I have created a 4.2 Compatible DC and Cluster. I'm able to add the host and that checks in OK. Its an older system hence going with 4.2 for processor support. When I try to a local storage domain, it fails. The error returned to the screen is : Error while executing action New Local Storage Domain: Internal Engine Error The process gets as far as creating some files and directories in the directory I'm trying to configure as a local storage domain. I notice in the UI, the format of the domain is specified as v4. (This option is greyed out and I cannot modify it).

It appears to be trying to use V5 format .... according to the engine log.


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


How reproducible:

Always


Steps to Reproduce:

1. Atteempt to add a local storage domain to a new DC and Cluster
2.
3.

Actual results:

Error is returned in the GUI.
"Error while executing New Local Storage Domain: Internal Engine Error"

Domain fails to add.


Expected results:

Domain is added.


Additional info:

Comment 1 shani 2019-08-14 09:03:32 UTC
The format field is grayed out since, for 4.2 compatibility value, there's only 1 supported format - V4.
Therefore, enabling a selection list for only 1 item is redundant.

Regarding setting the format to V4 (as listed on the popup) instead of V5 - a fixing patch will be available soon.

Comment 2 Evelina Shames 2019-08-27 08:59:41 UTC
Verified on engine: 4.3.6.3

I also tried a different flow to create local storage and saw the same error in the GUI:
"Error while executing New Local Storage Domain: Internal Engine Error"

Flow (UI):
- put host in maintenance
- create new directory on the host:
 mkdir -p /tst_dir
 chown 36:36 /tst_dir
 chmod 0755 /tst_dir
- Management > Configure Local Storage:
  Data Center - click edit and change Compatibility Version to 4.2
  path to local storage - /tst_dir
- click 'ok' -> "Error while executing New Local Storage Domain: Internal Engine Error"

Looks like the same issue.. Tal, what do you think? Open a new bug?

Comment 3 Evelina Shames 2019-08-28 07:50:05 UTC
Created attachment 1608874 [details]
Engine log - New flow

Comment 4 Fred Rolland 2019-08-28 08:31:26 UTC
Evelina,
If the flow described by the opener is working now, mark this one as Verified and open a new one.
Thanks

Comment 5 Evelina Shames 2019-08-28 10:44:29 UTC
Verified on ovirt-engine-4.3.6.3

Comment 6 Sandro Bonazzola 2019-09-26 19:43:28 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.