Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 890110

Summary: 3.1.z failed to add NFS domain on vdsm-4.10.2-2.0.el6.x86_64.rpm
Product: Red Hat Enterprise Linux 6 Reporter: Chao Yang <chayang>
Component: vdsmAssignee: Yeela Kaplan <ykaplan>
Status: CLOSED NOTABUG QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.4CC: abaron, amureini, bazulay, cpelland, iheim, juzhang, lpeer, michen, oourfali, sgrinber, ykaul
Target Milestone: rcKeywords: Regression
Target Release: 6.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-30 10:33:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm log none

Description Chao Yang 2012-12-25 07:39:05 UTC
Created attachment 668763 [details]
vdsm log

Description of problem:
Trying to add NFS domain to data centre, but it failed as:

Thread-3122::DEBUG::2012-12-24 18:19:04,453::persistentDict::185::Storage.PersistentDict::(__init__) Created a persistant dict with FileMetadataRW backend
Thread-3122::WARNING::2012-12-24 18:19:04,459::remoteFileHandler::185::Storage.CrabRPCProxy::(callCrabRPCFunction) Problem with handler, treating as timeout
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/remoteFileHandler.py", line 177, in callCrabRPCFunction
    rawLength = self._recvAll(LENGTH_STRUCT_LENGTH, timeout)
  File "/usr/share/vdsm/storage/remoteFileHandler.py", line 146, in _recvAll
    timeLeft):
  File "/usr/lib64/python2.6/contextlib.py", line 83, in helper
    return GeneratorContextManager(func(*args, **kwds))
  File "/usr/share/vdsm/storage/remoteFileHandler.py", line 133, in _poll
    raise Timeout()
Timeout
Thread-3122::ERROR::2012-12-24 18:19:04,459::task::853::TaskManager.Task::(_setError) Task=`f47c91a4-ef48-4ba8-b537-7c86c6bae1d3`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 861, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2297, in createStorageDomain
    typeSpecificArg, storageType, domVersion)
  File "/usr/share/vdsm/storage/nfsSD.py", line 93, in create
    fsd = cls(os.path.join(mntPoint, sdUUID))
  File "/usr/share/vdsm/storage/fileSD.py", line 130, in __init__
    sdUUID = metadata[sd.DMDK_SDUUID]
  File "/usr/share/vdsm/storage/persistentDict.py", line 85, in __getitem__
    return dec(self._dict[key])
  File "/usr/share/vdsm/storage/persistentDict.py", line 193, in __getitem__
    with self._accessWrapper():
  File "/usr/lib64/python2.6/contextlib.py", line 16, in __enter__
    return self.gen.next()
  File "/usr/share/vdsm/storage/persistentDict.py", line 147, in _accessWrapper
    self.refresh()
  File "/usr/share/vdsm/storage/persistentDict.py", line 224, in refresh
    lines = self._metaRW.readlines()
  File "/usr/share/vdsm/storage/fileSD.py", line 99, in readlines
    return misc.stripNewLines(self._oop.directReadLines(self._metafile))
  File "/usr/share/vdsm/storage/remoteFileHandler.py", line 286, in callCrabRPCFunction
    raise Timeout("Operation stuck on remote handler")
Timeout: Operation stuck on remote handler

Version-Release number of selected component (if applicable):
vdsm-4.10.2-2.0.el6.x86_64.rpm

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
This failure doesn't happen on vdsm-4.10.2-1.0.el6.x86_64. So, this is regression bug.

Comment 3 Yeela Kaplan 2013-01-29 13:30:37 UTC
chayang, can you please give us the contents of the /home/data directory?
From the log you see that the error happens because the directory is not empty.

Thread-2941::INFO::2012-12-24 18:14:10,921::logUtils::37::dispatcher::(wrapper) Run and protect: createStorageDomain(storageType=1, sdUUID='503f07e7-fccc-445b-9bcb-6769d3de6783', domainName='test',
 typeSpecificArg='10.66.11.172:/home/data', domClass=1, domVersion='3', options=None)

Thread-2941::ERROR::2012-12-24 18:14:14,662::task::853::TaskManager.Task::(_setError) Task=`7fa1e3c7-3f91-46f8-bd41-c63813de1ca1`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 861, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 2297, in createStorageDomain
    typeSpecificArg, storageType, domVersion)
  File "/usr/share/vdsm/storage/nfsSD.py", line 78, in create
    version)
  File "/usr/share/vdsm/storage/nfsSD.py", line 54, in _preCreateValidation
    raise se.StorageDomainNotEmpty(typeSpecificArg)

maybe run the 'ls -ltr' command?
thanks.

Comment 4 Allon Mureinik 2013-01-30 09:43:32 UTC
Does this reproduce on RHEL, or only on RHEV-H?

Comment 5 Chao Yang 2013-01-30 10:28:33 UTC
(In reply to comment #3)
> chayang, can you please give us the contents of the /home/data directory?
> From the log you see that the error happens because the directory is not
> empty.
> 
> Thread-2941::INFO::2012-12-24
> 18:14:10,921::logUtils::37::dispatcher::(wrapper) Run and protect:
> createStorageDomain(storageType=1,
> sdUUID='503f07e7-fccc-445b-9bcb-6769d3de6783', domainName='test',
>  typeSpecificArg='10.66.11.172:/home/data', domClass=1, domVersion='3',
> options=None)
> 
> Thread-2941::ERROR::2012-12-24
> 18:14:14,662::task::853::TaskManager.Task::(_setError)
> Task=`7fa1e3c7-3f91-46f8-bd41-c63813de1ca1`::Unexpected error
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/task.py", line 861, in _run
>     return fn(*args, **kargs)
>   File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
>     res = f(*args, **kwargs)
>   File "/usr/share/vdsm/storage/hsm.py", line 2297, in createStorageDomain
>     typeSpecificArg, storageType, domVersion)
>   File "/usr/share/vdsm/storage/nfsSD.py", line 78, in create
>     version)
>   File "/usr/share/vdsm/storage/nfsSD.py", line 54, in _preCreateValidation
>     raise se.StorageDomainNotEmpty(typeSpecificArg)
> 
> maybe run the 'ls -ltr' command?
> thanks.

I also noticed this storage domain not empty error, then retried with a clean storage domain by creating an empty directory, but this didn't work, so I opened this bug.

But now I cannot reproduce this bug on vdsm-4.10.2-5.0.el6ev.x86_64.

Comment 6 Chao Yang 2013-01-30 10:29:10 UTC
(In reply to comment #4)
> Does this reproduce on RHEL, or only on RHEV-H?

I tested on RHEL.

Comment 7 Yaniv Kaul 2013-01-30 10:33:09 UTC
(In reply to comment #5)
> 
> But now I cannot reproduce this bug on vdsm-4.10.2-5.0.el6ev.x86_64.

Closing the bug. Please re-open when you can reproduce.
I suspect the mount was not clean.