Hide Forgot
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.
Created attachment 1242663 [details] GUI view of direct lun vs image disk
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' ?)
(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 ?