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.
Previously, VDSM attempted to to release the hostId lock on an unreachable storage domain, and wrote potentially confusing messages to the vdsm.log file.
Attempts to release hostId lock are no longer made for unreachable storage, and the potentially confusing error messages aren't written to the vdsm.log file.
Created attachment 610271[details]
vdsm logs
Description of problem:
When a domain is not reachable, during the attempt to stop the domain monitor for that domain, the following is visible in the vdsm logs:
Thread-45::DEBUG::2012-09-06 13:01:15,768::domainMonitor::150::Storage.DomainMonitorThread::(_monitorLoop) Stopping domain monitor for 64bfae48-2ccd-4c05-b523-1fdeb90f4d2c
Thread-45::DEBUG::2012-09-06 13:01:15,768::domainMonitor::159::Storage.DomainMonitorThread::(_monitorLoop) Unable to release the host id 1 for domain 64bfae48-2ccd-4c05-b523-1fdeb90f4d2c
Traceback (most recent call last):
File "/usr/share/vdsm/storage/domainMonitor.py", line 156, in _monitorLoop
self.domain.releaseHostId(self.hostId, unused=True)
AttributeError: 'NoneType' object has no attribute 'releaseHostId'
Thread-318::DEBUG::2012-09-06 13:01:15,769::sp::1555::Storage.StoragePool::(updateMonitoringThreads) Storage Pool `8877b085-e5c5-4962-a15e-105cf6829bc7` stopped monitoring domain `64bfae48-2ccd-4c05-b523-1fdeb90f4
d2c
This error does not seem to affect the operation itself, but should probably not be written to the log
Version-Release number of selected component (if applicable):
vdsm-4.9.6-32.0.el6_3.x86_64
Steps to Reproduce:
1. Block connection between host and non-master storage domain
2. AttributeError should be visible in the logs
Actual results:
AttributeError is visible in the logs
Expected results:
AttributeError should not be printed to the logs
Additional info:
Comment 2Federico Simoncelli
2012-09-13 15:48:59 UTC
DomainMonitor shouldn't releaseHostId if the domain is missing
In this patch:
* do not release releaseHostId if the domain is missing
* improve the checks for produce() and isIsoDomain()
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=854953
Signed-off-by: Federico Simoncelli <fsimonce>
Change-Id: I7b2d97f95d682ea00079cee0c0587243ed56651c
http://gerrit.ovirt.org/#/c/7833/
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/RHSA-2012-1508.html
Created attachment 610271 [details] vdsm logs Description of problem: When a domain is not reachable, during the attempt to stop the domain monitor for that domain, the following is visible in the vdsm logs: Thread-45::DEBUG::2012-09-06 13:01:15,768::domainMonitor::150::Storage.DomainMonitorThread::(_monitorLoop) Stopping domain monitor for 64bfae48-2ccd-4c05-b523-1fdeb90f4d2c Thread-45::DEBUG::2012-09-06 13:01:15,768::domainMonitor::159::Storage.DomainMonitorThread::(_monitorLoop) Unable to release the host id 1 for domain 64bfae48-2ccd-4c05-b523-1fdeb90f4d2c Traceback (most recent call last): File "/usr/share/vdsm/storage/domainMonitor.py", line 156, in _monitorLoop self.domain.releaseHostId(self.hostId, unused=True) AttributeError: 'NoneType' object has no attribute 'releaseHostId' Thread-318::DEBUG::2012-09-06 13:01:15,769::sp::1555::Storage.StoragePool::(updateMonitoringThreads) Storage Pool `8877b085-e5c5-4962-a15e-105cf6829bc7` stopped monitoring domain `64bfae48-2ccd-4c05-b523-1fdeb90f4 d2c This error does not seem to affect the operation itself, but should probably not be written to the log Version-Release number of selected component (if applicable): vdsm-4.9.6-32.0.el6_3.x86_64 Steps to Reproduce: 1. Block connection between host and non-master storage domain 2. AttributeError should be visible in the logs Actual results: AttributeError is visible in the logs Expected results: AttributeError should not be printed to the logs Additional info: