Bug 1415078 - direct lun disk status is not available via GUI/RestAPI
Summary: direct lun disk status is not available via GUI/RestAPI
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Allon Mureinik
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-20 07:53 UTC by Avihai
Modified: 2017-01-22 11:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-22 09:50:56 UTC
oVirt Team: Storage


Attachments (Terms of Use)
Print screen of GUI and RestApi of the direct lun vs image disk (333.96 KB, image/jpeg)
2017-01-20 07:53 UTC, Avihai
no flags Details
GUI view of direct lun vs image disk (316.39 KB, image/jpeg)
2017-01-20 07:55 UTC, Avihai
no flags Details

Description Avihai 2017-01-20 07:53:28 UTC
Created attachment 1242662 [details]
Print screen of GUI and RestApi of the direct lun vs image disk

Description of problem:
Direct lun disk status is not available via GUI/RestAPI 
On Same fc/iscsi domain an image disk status is available.


Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0.1-0.4.master.20170118134729.gitf34da1f.el7.centos.noarch

How reproducible:
100%


Steps to Reproduce:
1.create block(iscsi/fc) domain
2.create a direct lun disk
3.check out via GUI/RestAPI what is the disk status.

Actual results:
Direct lun disk status is not available.
Via GUI I get N/A.
Via RestAPI "status" field does not exist .


Expected results:
Direct lun disk status should be shown the same as an image disk .

Additional info:
On Same fc/iscsi domain an image disk status is available.

Comment 1 Avihai 2017-01-20 07:55:01 UTC
Created attachment 1242663 [details]
GUI view of direct lun vs image disk

Comment 2 Yaniv Kaul 2017-01-22 09:50:56 UTC
AFAIR, we don't know the status of a direct LUN. We don't monitor or check it.
There's no real status for it either (what does it means 'not OK' ?)

Comment 3 Avihai 2017-01-22 11:56:23 UTC
(In reply to Yaniv Kaul from comment #2)
> AFAIR, we don't know the status of a direct LUN. We don't monitor or check
> it.
> There's no real status for it either (what does it means 'not OK' ?)

"OK" is taken from an image disk status field both in GUI/RestAPI.
In direct lun disk you see in GUI "N/A" .

In direct lun disk I would expect it to have the same status as any other disk.

I understand its a different kind of disk that we can only know its status from the lun connectivity state.

Can we monitor the lun state & apply it to the direct disk state ?
Maybe an RFE is in order here ?


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