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

Bug 838521

Summary: [ovirt][engine]can't attach an iso nfs domain to iscsi pool
Product: [Retired] oVirt Reporter: Royce Lv <lvroyce>
Component: ovirt-engine-coreAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED NOTABUG QA Contact: Haim <hateya>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, amureini, dyasny, hateya, iheim, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-13 10:02:52 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
engine-log
none
vdsm-log none

Description Royce Lv 2012-07-09 10:47:50 UTC
Created attachment 597037 [details]
engine-log

Description of problem:
had an iscsi pool with an iscsi domain
attach a iso nfs domain to this pool result in:
nfs domain created successfully,
but soon nfs path umounted and storageServer disconnected
then iso domain keep status maintainence.


Version-Release number of selected component (if applicable):
ovirt-engine-3.1.0-0.2.20120704git1df1ba.fc17.noarch
vdsm-4.10.0-0.132.git0d79b72.fc17.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
ISO domain status maintainence, 
nfs path umounted from host

Expected results:
attach ISO domain succeed

Additional info:

Comment 1 Royce Lv 2012-07-09 10:51:52 UTC
Created attachment 597038 [details]
vdsm-log

Comment 2 Haim 2012-07-09 14:01:01 UTC
(In reply to comment #1)
> Created attachment 597038 [details]
> vdsm-log

Royce, 

what is your problem exactly ? what happens if you click on activate button ? if operation succeeds, then I suspect that this behavior (as described above) is by design.

Comment 3 Royce Lv 2012-07-13 10:02:52 UTC
It turned to be directory permission problem , close