Bug 1014203

Summary: storage connection is created when import domain fails
Product: Red Hat Enterprise Virtualization Manager Reporter: movciari
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Aharon Canan <acanan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, amureini, asegundo, derez, iheim, istein, lpeer, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Flags: amureini: Triaged+
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-12 14:03:41 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:
Attachments:
Description Flags
'tail -f' from engine.log while i was reproducing this bug none

Description movciari 2013-10-01 14:09:11 UTC
Description of problem:
when importing storage domain fails under some conditions, for example when mount point is an empty directory, storage connection is still created,
so from the user perspective - when you are trying to create new storage domain on the same mount point because import failed, it fails with dialog window saying:
    Error while executing action: Cannot add Storage Connection. Storage connection already exists.


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

How reproducible:
always

Steps to Reproduce:
1. create empty nfs export
2. try to import this export as storage domain, this should fail, saying there is no storage domain
3. just click 'OK' button again, or hit 'Cancel' and try to create new storage domain on this export

Actual results:
you will get an error saying storage connection already exists, you have to delete this connection manually via api or in database

Expected results:
storage connection should not be created when import fails

Additional info:
this happens when import fails under some other contitions than those in steps to reproduce, too

Comment 1 movciari 2013-10-01 14:53:19 UTC
Created attachment 806036 [details]
'tail -f' from engine.log while i was reproducing this bug

Comment 2 Ayal Baron 2013-10-02 08:43:35 UTC
Allon, is this a dup?

Comment 3 Allon Mureinik 2013-10-17 12:47:54 UTC
(In reply to Ayal Baron from comment #2)
> Allon, is this a dup?
No. It is similar to bug 991470, but the usecase and code-path are different.

Comment 4 Ilanit Stein 2013-11-20 14:48:59 UTC
Also encountered it on is23, when import iso domain failed, on domain name already existing in the setup.

Comment 5 Ayal Baron 2014-02-16 08:51:08 UTC
Allon, is this resolved?

Comment 6 Allon Mureinik 2014-03-12 10:20:28 UTC
Daniel, is this resolved?

Comment 7 Daniel Erez 2014-04-13 07:30:32 UTC
This seems like a duplicate of bug 1020812 which has been resolved for 3.3. The described scenario doesn't appear to reproduce any longer. Moving to ON_QA for re-verification.

Comment 8 Itamar Heim 2014-06-12 14:03:41 UTC
Closing as part of 3.4.0