Bug 1069173

Summary:	[RFE] Mark disks with inaccessible(maintenance) Storage Domain
Product:	[oVirt] ovirt-engine	Reporter:	Maor <mlipchuk>
Component:	Frontend.WebAdmin	Assignee:	Maor <mlipchuk>
Status:	CLOSED DUPLICATE	QA Contact:	Raz Tamir <ratamir>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	---	CC:	amureini, bugs, gklein, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-05 07:54:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2014-02-24 12:05:07 UTC

Description of problem:
There is no indication if the disk's Storage Domain is active or not.
When the user run a VM or try to use the disk, the engine sends a CDA message indicating that the Storage Domain is inaccessible, though it would be great if the user could see that before in the disks subtab under vms or in the main tab of disks.

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


How reproducible:
100%

Steps to Reproduce:
1. Create a VM
2. Add a disk on Storage Domain A
3. Add another disk on Storage Domain B
4. Move Storage Domain B to maintenance
5. Try to run the VM

Actual results:
You will get a message that the Storage Domain is not accessable

Expected results:
We should also have an indication in the GUI that the Storage Domain which the disk is based on is not accessible (Something like an explanation mark)

Additional info:
We should add an attribute in the disk business entity of the Storage domain status

Comment 1 Yaniv Lavi 2016-12-05 07:54:44 UTC


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