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.
Description of problem:
reconstruct master domain fails during conection problem from host to storage when the domains are located on 2 different storage servers.
Version-Release number of selected component (if applicable):
vdsm-4.9.6-10.el6.x86_64
si4
How reproducible:
100%
Steps to Reproduce:
1. create two domains each domain should be located on a different storage server
2. block connectivity to the master domain from the host using iptables
3.
Actual results:
reconstruct master domain will fail
Expected results:
we should succeed to reconstruct master
Additional info: logs attached
after speaking with Edu, this was probably caused by a patch which was reverted and we will probably not see it in vdsm-14.
but, we need to test this once the new vdsm will come out and this issue is also a TestBlocker for current vdsm.
600: Input/output error\n WARNING: Error counts reached a limit of 3. Device /dev/sdk was disabled\n Couldn't find device with uuid KERvf0-hvTO-AEGm-pFui-bQLd-UNTY-7kTExm.\n"; <rc> = 0
MainThread::DEBUG::2012-06-03 19:56:51,704::lvm::356::OperationMutex::(_reloadpvs) Operation 'lvm reload operation' released the operation mutex
MainThread::ERROR::2012-06-03 19:56:51,704::clientIF::162::vds::(_initIRS) Error initializing IRS
Traceback (most recent call last):
File "/usr/share/vdsm/clientIF.py", line 160, in _initIRS
self.irs = Dispatcher(HSM())
File "/usr/share/vdsm/storage/hsm.py", line 298, in __init__
lvm._lvminfo.bootstrap()
File "/usr/share/vdsm/storage/lvm.py", line 324, in bootstrap
self._reloadpvs()
File "/usr/share/vdsm/storage/lvm.py", line 346, in _reloadpvs
pv = makePV(*fields)
File "/usr/share/vdsm/storage/lvm.py", line 200, in makePV
name = fixPVName(args[1])
File "/usr/share/vdsm/storage/lvm.py", line 195, in fixPVName
dmId = devicemapper.getDmIdFromFile(devPath)
File "/usr/share/vdsm/storage/devicemapper.py", line 35, in getDmIdFromFile
raise OSError(errno.ENODEV, "Could not find dm device named `%s`" % path)
Description of problem: reconstruct master domain fails during conection problem from host to storage when the domains are located on 2 different storage servers. Version-Release number of selected component (if applicable): vdsm-4.9.6-10.el6.x86_64 si4 How reproducible: 100% Steps to Reproduce: 1. create two domains each domain should be located on a different storage server 2. block connectivity to the master domain from the host using iptables 3. Actual results: reconstruct master domain will fail Expected results: we should succeed to reconstruct master Additional info: logs attached after speaking with Edu, this was probably caused by a patch which was reverted and we will probably not see it in vdsm-14. but, we need to test this once the new vdsm will come out and this issue is also a TestBlocker for current vdsm. 600: Input/output error\n WARNING: Error counts reached a limit of 3. Device /dev/sdk was disabled\n Couldn't find device with uuid KERvf0-hvTO-AEGm-pFui-bQLd-UNTY-7kTExm.\n"; <rc> = 0 MainThread::DEBUG::2012-06-03 19:56:51,704::lvm::356::OperationMutex::(_reloadpvs) Operation 'lvm reload operation' released the operation mutex MainThread::ERROR::2012-06-03 19:56:51,704::clientIF::162::vds::(_initIRS) Error initializing IRS Traceback (most recent call last): File "/usr/share/vdsm/clientIF.py", line 160, in _initIRS self.irs = Dispatcher(HSM()) File "/usr/share/vdsm/storage/hsm.py", line 298, in __init__ lvm._lvminfo.bootstrap() File "/usr/share/vdsm/storage/lvm.py", line 324, in bootstrap self._reloadpvs() File "/usr/share/vdsm/storage/lvm.py", line 346, in _reloadpvs pv = makePV(*fields) File "/usr/share/vdsm/storage/lvm.py", line 200, in makePV name = fixPVName(args[1]) File "/usr/share/vdsm/storage/lvm.py", line 195, in fixPVName dmId = devicemapper.getDmIdFromFile(devPath) File "/usr/share/vdsm/storage/devicemapper.py", line 35, in getDmIdFromFile raise OSError(errno.ENODEV, "Could not find dm device named `%s`" % path)