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

Bug 1157221

Summary: Attempting a discovery operation of a wrong iSCSi ip takes too long to fail, the operation also unstoppable
Product: Red Hat Enterprise Virtualization Manager Reporter: Ori Gofen <ogofen>
Component: ovirt-engineAssignee: Idan Shaby <ishaby>
Status: CLOSED WORKSFORME QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, ecohen, gklein, iheim, lpeer, lsurette, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 10:35:02 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:
Attachments:
Description Flags
logs none

Description Ori Gofen 2014-10-26 10:20:32 UTC
Created attachment 950766 [details]
logs

Description of problem:
When giving oVirt the wrong iSCSi ip to discover, the operation takes way too long to fail, in addition when I'm realizing that a false ip had been given, pressing "x" on the creation window doesn't roll back this operation, it continues for several minutes until it fails with several exceptions on engine logs.

ui message:
"No new devices were found. This may be due to either: incorrect multipath configuration on the Host or wrong address of the iscsi target or a failure to authenticate on the target device. Please consult your Storage Administrator."

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

How reproducible:
100%

Steps to Reproduce:
1.discover a false iSCSi ip via oVirt's create domain window

Actual results:
The operation takes way to long to fail, when pressing the "x" button the operation doesn't stop

Expected results:
The operation should not take more than several seconds, when pressing the "x" button it should stop.

Additional info:

Comment 1 Idan Shaby 2014-11-24 10:35:02 UTC
Checked it on vt11 and it works fine.