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 885747 - [vdsm] connectStorageServer is failing as super vdsm object get lazy in initialization
Summary: [vdsm] connectStorageServer is failing as super vdsm object get lazy in initi...
Keywords:
Status: CLOSED DUPLICATE of bug 890365
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 6.3
Assignee: Yaniv Bronhaim
QA Contact: Haim
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 14:25 UTC by Tareq Alayan
Modified: 2018-11-30 20:27 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-17 10:40:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdsm.log (4.08 MB, text/x-log)
2012-12-10 14:26 UTC, Tareq Alayan
no flags Details

Description Tareq Alayan 2012-12-10 14:25:05 UTC
Description of problem:
vdsm fails to connect to storage server immediately after startup.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-44.2.el6_3.x86_64

How reproducible:
always

Steps to Reproduce:
1. Add 2 hosts
2. start host1 and then stop host1
3. start host1 again

host2 will be the proxy for the fencing command
  
Actual results:
host1 becomes non-operationl for ~3 minutes then become UP

Expected results:
host1 should become UP from the down state instantly

Additional info:
log snippet
Thread-16::INFO::2012-12-10 14:38:46,569::logUtils::37::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=1, spUUID='ec83eff2-331d-4b80-8fc5-fd5c4ed212bd', conList=[{'connection': '10.35.64.106:/export/jenkins-vm-13_nfs_2012_12_10_14_25_55_291252', 'iqn': '', 'portal': '', 'user': '', 'password': '******', 'id': '581f836e-c149-4f69-90a1-4dde6652d2cd', 'port': ''}], options=None)
Thread-16::DEBUG::2012-12-10 14:38:46,572::__init__::1164::Storage.Misc.excCmd::(_log) '/usr/bin/sudo -n /bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 10.35.64.106:/export/jenkins-vm-13_nfs_2012_12_10_14_25_55_291252 /rhev/data-center/mnt/10.35.64.106:_export_jenkins-vm-13__nfs__2012__12__10__14__25__55__291252' (cwd None)
Thread-16::ERROR::2012-12-10 14:38:46,757::hsm::2096::Storage.HSM::(connectStorageServer) Could not connect to storageServer
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/hsm.py", line 2093, in connectStorageServer
    conObj.connect()
  File "/usr/share/vdsm/storage/storageServer.py", line 280, in connect
    return self._mountCon.connect()
  File "/usr/share/vdsm/storage/storageServer.py", line 187, in connect
    fileSD.validateDirAccess(self.getMountObj().getRecord().fs_file)
  File "/usr/share/vdsm/storage/fileSD.py", line 51, in validateDirAccess
    (os.R_OK | os.X_OK))
  File "/usr/share/vdsm/supervdsm.py", line 69, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 59, in <lambda>
    getattr(self._supervdsmProxy._svdsm, self._funcName)(*args,
AttributeError: 'ProxyCaller' object has no attribute 'validateAccess'
Thread-16::INFO::2012-12-10 14:38:46,820::logUtils::39::dispatcher::(wrapper) Run and protect: connectStorageServer, Return response: {'statuslist': [{'status': 100, 'id': '581f836e-c149-4f69-90a1-4dde6652d2cd'}]}
Thread-16::DEBUG::2012-12-10 14:38:46,820::task::1172::TaskManager.Task::(prepare) Task=`213a08a7-6c25-4a22-8dec-fb314ca325fb`::finished: {'statuslist': [{'status': 100, 'id': '581f836e-c149-4f69-90a1-4dde6652d2cd'}]}

Comment 1 Tareq Alayan 2012-12-10 14:26:13 UTC
Created attachment 660901 [details]
vdsm.log

Comment 3 Yaniv Bronhaim 2012-12-10 16:13:59 UTC
http://gerrit.ovirt.org/#/c/9691/
making svdsm starts at start-up

Comment 4 RHEL Program Management 2012-12-14 07:59:29 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Yaniv Bronhaim 2013-02-17 10:40:04 UTC
That was fixed as part of https://bugzilla.redhat.com/show_bug.cgi?id=890365

Comment 6 Yaniv Bronhaim 2013-02-17 10:40:34 UTC

*** This bug has been marked as a duplicate of bug 890365 ***


Note You need to log in before you can comment on or make changes to this bug.