Bug 1154425

Summary: [BLOCKED] When creating iSCSI storage domain, receive warning noting "The operation might be unrecoverable and destructive!" on only one of the hosts, the list of LUNs grows with Storage domain being added and then removed
Product: Red Hat Enterprise Virtualization Manager Reporter: Gilad Lazarovich <glazarov>
Component: vdsmAssignee: Daniel Erez <derez>
Status: CLOSED WONTFIX QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, amureini, bazulay, ecohen, gklein, glazarov, iheim, lpeer, lsurette, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-31 13:36:24 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: 1163890    
Bug Blocks:    
Attachments:
Description Flags
Engine and VDSM logs
none
LUN listing from both hosts, host capabilities and sanlock.log
none
full set of logs from a new setup none

Description Gilad Lazarovich 2014-10-19 15:53:05 UTC
Created attachment 948300 [details]
Engine and VDSM logs

Description of problem:
When creating iSCSI storage domain, receive warning noting "The operation might be unrecoverable and destructive!" on only one of the hosts.  The UI displays "The following LUNs are already in use" and then lists the LUNs, the list grows with Storage domain being added and then removed

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

How reproducible:
100%

Steps to Reproduce:
1. Using a setup with 2 hosts that have the same set of iSCSI LUNs, attempt to add an iSCSI Storage Domain using all available LUNs (first using one host, and then the next host - removing the Storage domain in between)

Actual results:
In my case, one of the 2 hosts shows a warning noting 5 out of the 10 available LUNs are available, while the second host shows no such warning and creates the Storage domain right away.  After removing the Storage domain, then trying again, the number of LUNs in use appears to increase (though not 100% consistent for this)

Additional information:
See attached logs

Comment 1 Daniel Erez 2014-10-20 21:23:37 UTC
Hi Gilad,

The warning is displayed based on the 'status' (used/free/unusable) property of each LUN. Can you please attach the output of getDeviceList for each host (after reproducing the described scenario)? Any difference between the hosts (vdsm build/os version/etc)?

Comment 2 Gilad Lazarovich 2014-10-21 14:42:02 UTC
Created attachment 949000 [details]
LUN listing from both hosts, host capabilities and sanlock.log

Comment 3 Daniel Erez 2014-10-22 10:58:23 UTC
According the logs [1], same lun appears as status 'free' in vdsd host, whereas, in status 'used' in vdsc host. Since the status should be identical from both hosts, moving component to vdsm for further investigation.

@Gilad - can you please check the described scenario with another set of hosts to understand if the issue is isolated to a specific host?

[1] 
* vdsd_deviceList:
 "{'GUID': '360060160f4a030000fa06fb98edbe311',
  ...
  'status': 'free',
  ...}"

* vdsc_deviceList:
 "{'GUID': '360060160f4a030000fa06fb98edbe311',
  ...
  'status': 'used',
  ...}"

Comment 4 Gilad Lazarovich 2014-11-12 10:10:00 UTC
Created attachment 956673 [details]
full set of logs from a new setup

Comment 5 Gilad Lazarovich 2014-11-12 10:10:27 UTC
Please note that this is fully reproducible on the original environment and also on a newly build vt9 environment (different hosts, engine), please find the full complement of logs in the new attachment

Comment 6 Allon Mureinik 2015-05-31 13:36:24 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.