Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 921544

Summary:	PRD33 - LUNs 'In Use' field is confusing
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Daniele <dconsoli>
Component:	RFEs	Assignee:	Daniel Erez <derez>
Status:	CLOSED ERRATA	QA Contact:	yeylon <yeylon>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.1.1	CC:	abaron, aburden, acanan, acathrow, amureini, derez, iheim, jentrena, jkt, lpeer, lyarwood, perobins, Rhev-m-bugs, srevivo, ukar, yeylon
Target Milestone:	---	Keywords:	Improvement
Target Release:	3.3.0	Flags:	scohen: needinfo+
Hardware:	All
OS:	All
Whiteboard:	storage
Fixed In Version:	is3	Doc Type:	Enhancement
Doc Text:	The 'In Use' column indicated the LUN is a part of a VG (which contains data), but it was confused with being used by the engine (the LUN is a part of an existing storage domain). This column has been removed to decrease ambiguity.	Story Points:	---
Clone Of:
Clones:	976611 (view as bug list)		Environment:
Last Closed:	2014-01-21 17:15:13 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:
Bug Depends On:
Bug Blocks:	889053, 976611, 977679, 977681

Description Daniele 2013-03-14 12:10:47 UTC

Description of problem:
Storage --> Edit Domain shows some LUNS' status as "Free" even when they have already assigned to storage domain and are no longer available. 
The "In Use" status should read "Used".

Also, LUNS which _do_ show as used, sometimes are shown as an available to be added to a FC type storage domain in Storage --> Edit Domain.

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


How reproducible:


Steps to Reproduce:
1. Assign a LUN to a storage domain
2. Navigate to Storage --> Edit Domain and check the LUN's "In Use" status
3. It will be "Free", it should be "Used"
  
Actual results:
The LUN's status is not reported correctly.
LUN's marked as "Used" are shown as available to be added to a SD.

Expected results:
The LUN's status on the UI gets updated properly so that it reflects the real status of the LUN.
LUN's marked as "Used" should not be shown as available to be added to a SD.

Additional info:
Apparently, putting the SPM into Maintenance Mode and triggering a new election, forces an update of the status and marks used LUN's as "Used".
They "Used" ones, could still be visible as available to be added to a SD, though, which is also wrong.

Comment 1 Haim 2013-03-17 18:48:03 UTC

SPM\HSM has no direct impact on host with regards of lun status, lun status is a direct result of engine issue getDeviceList on the selected host when admin lunched the edit storage domain window.

please attach full SOS report to include all logs on both engine and hypervisor.

note: title should be changed (let's wait after RCA).

Comment 2 Ayal Baron 2013-03-17 21:18:46 UTC

This is a usability issue.
The 'in use' field simply states whether the LUN has a VG/partitions on it.
The fact that it already belongs to a storage domain or not is specified in a different way in the GUI.

Daniel, anything you'd like to add?

Comment 4 Daniele 2013-03-18 16:00:54 UTC

The logcollector should be attached now.
Do you need me to do something else? Should we change this ticket to a RFE?

How is the fat that a disk belongs to a storage domain specified? Buy the "V" sign?

Comment 5 Daniel Erez 2013-03-24 09:13:10 UTC

(In reply to comment #4)
> The logcollector should be attached now.
> Do you need me to do something else? Should we change this ticket to a RFE?
> 
> How is the fat that a disk belongs to a storage domain specified? Buy the
> "V" sign?

Yes, the "V" sign indicates the the LUN is a part of a storage domain.

Comment 6 Ayal Baron 2013-03-26 22:00:04 UTC

*** Bug 927594 has been marked as a duplicate of this bug. ***

Comment 10 Ayal Baron 2013-03-28 09:43:52 UTC

*** Bug 924187 has been marked as a duplicate of this bug. ***

Comment 16 Ayal Baron 2013-05-01 09:16:40 UTC

*** Bug 951030 has been marked as a duplicate of this bug. ***

Comment 17 Ayal Baron 2013-05-12 11:01:22 UTC

*** Bug 951025 has been marked as a duplicate of this bug. ***

Comment 22 Ayal Baron 2013-07-07 08:00:40 UTC

*** Bug 910990 has been marked as a duplicate of this bug. ***

Comment 24 Aharon Canan 2013-07-30 13:04:42 UTC


Column doesn't exist anymore.
all used luns are greyed out 

no test cases needed, remove external TCMS link

Comment 27 Charlie 2013-11-28 00:09:20 UTC

This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 30 errata-xmlrpc 2014-01-21 17:15:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHSA-2014-0038.html