Bug 987833
Summary: | dumpStorageTable produces an avoidable traceback if vdsmd is down. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lee Yarwood <lyarwood> |
Component: | vdsm | Assignee: | Lee Yarwood <lyarwood> |
Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.2.0 | CC: | abaron, acathrow, amureini, bazulay, hchiramm, iheim, lpeer, lyarwood, yeylon |
Target Milestone: | --- | ||
Target Release: | 3.3.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | storage | ||
Fixed In Version: | v4.12.0 | Doc Type: | Bug Fix |
Doc Text: |
When vdsmd was down the first getConnectedStoragePoolsList call resulted in a 'Connection Refused' trace being shown. To avoid this trace being picked up by the automatic bug reporting tool, the connection is now tested first, catching any errors before continuing.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-21 16:29:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lee Yarwood
2013-07-24 09:14:32 UTC
verified using is10 according to above steps [root@camel-vdsb ~]# /etc/init.d/vdsmd stop Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm stop [ OK ] [root@camel-vdsb ~]# python /usr/share/vdsm/dumpStorageTable.py Unable to connect to vdsmd [Errno 111] Connection refused This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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/RHBA-2014-0040.html |