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

Bug 1046330

Summary: [vdsm] manage storage connection of file based storage fails with StorageDomainAccessError
Product: Red Hat Enterprise Virtualization Manager Reporter: Elad <ebenahar>
Component: vdsmAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: abaron, acanan, amureini, bazulay, hateya, iheim, lpeer, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-24 16:03:26 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
posix and nfs scenarios logs none

Description Elad 2013-12-24 15:20:29 UTC
Created attachment 841273 [details]
posix and nfs scenarios logs

Description of problem:
VDSM fails to change storage connection details (the storage path) with the following error:

Thread-72403::ERROR::2013-12-24 16:57:06,208::task::850::TaskManager.Task::(_setError) Task=`e04401b1-da7c-4901-8d21-98b211ec12c0`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 857, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2803, in getStorageDomainStats
    stats = dom.getStats()
  File "/usr/share/vdsm/storage/fileSD.py", line 527, in getStats
    raise se.StorageDomainAccessError(self.sdUUID)
StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('d136bc03-5cb4-4dce-a2c2-e439d6453867',)

Version-Release number of selected component (if applicable):
vdsm-4.13.2-0.3.el6ev.x86_64
rhevm-3.3.0-0.41.el6ev.noarch


How reproducible:
Always 

Steps to Reproduce:
On NFS/POSIXFS DC:
1. maintenance the domain 
2. change the domain's storage path to another mount point


Actual results:
VDSM fails to change the storage connection path with the mentioned error message

Expected results:
Changing the storage connection path should succeed

Additional info: posix and nfs scenarios logs

Comment 2 Elad 2013-12-24 16:03:26 UTC
Storage domain's data wasn't replicated during the test, so closing this as NOTABUG