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.
Created attachment 512904[details]
vdsm log
Description of problem:
After fencing vdsm it takes it 4 minutes to come up - issue happened on 50 SDs FC deployment, sending an offline status to master domain. caused the vdsm to be fenced and afterwards it took it 4 minutes to come up.
Version-Release number of selected component (if applicable):
vdsm-4.9-81.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.make master SD offline- make sure all paths are offline( echo offline > /sys/block/sdby/device/state)
2.vdsm will then fence.
3.
Actual results:
Expected results:
Additional info:
MainThread::INFO::2011-07-14 15:19:43,268::vdsm::71::vds::(run) I am the actual
vdsm 4.9-81
Thread-11::DEBUG::2011-07-14 15:23:45,274::supervdsm::43::SuperVdsmProxy::(__init__) Connected to Super Vdsm
I don't think there's anything we can do about it, as most of the time is wasted inside pvs:
MainThread::DEBUG::2011-07-14 15:19:43,512::lvm::359::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvs --config " devices { pref
MainThread::DEBUG::2011-07-14 15:23:38,006::lvm::359::Storage.Misc.excCmd::(cmd) SUCCESS: <err> = ' /dev/mapper/36006016066102900184f9fa5
However, connectStoragePool keeps taking ages (6 minutes) to complete, which confuses rhevm. The log shows 34 connectStoragePool interlaced with 10 disconnectStoragePool. Omer, why are disconnectStoragePool sent at all?
its hard to say without rhevm log, but guessing the possible flow, i'd say this is the only up host in the pool, so trying to select spm every 10 secs will do the connectStoragePool.
about the disconnectStoragePool - since there are only 10, i can guess they are caused or by the user with maintenance, or reconstruct master which requires disconnectStoragePool, or user tries to activate a host (not the first one - less likely), and it moves to non-operational
Comment 5Eduardo Warszawski
2011-08-02 10:39:45 UTC
(In reply to comment #5)
> http://gerrit.usersys.redhat.com/#change,775
verified on 4.9-104.
vdsm now initialize faster by responding to getVdsCaps with regardless of storage connection, this ease the pain described above.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2011-1782.html
Created attachment 512904 [details] vdsm log Description of problem: After fencing vdsm it takes it 4 minutes to come up - issue happened on 50 SDs FC deployment, sending an offline status to master domain. caused the vdsm to be fenced and afterwards it took it 4 minutes to come up. Version-Release number of selected component (if applicable): vdsm-4.9-81.el6.x86_64 How reproducible: always Steps to Reproduce: 1.make master SD offline- make sure all paths are offline( echo offline > /sys/block/sdby/device/state) 2.vdsm will then fence. 3. Actual results: Expected results: Additional info: MainThread::INFO::2011-07-14 15:19:43,268::vdsm::71::vds::(run) I am the actual vdsm 4.9-81 Thread-11::DEBUG::2011-07-14 15:23:45,274::supervdsm::43::SuperVdsmProxy::(__init__) Connected to Super Vdsm