Bug 987833

Summary: dumpStorageTable produces an avoidable traceback if vdsmd is down.
Product: Red Hat Enterprise Virtualization Manager Reporter: Lee Yarwood <lyarwood>
Component: vdsmAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: low Docs Contact:
Priority: low    
Version: 3.2.0CC: 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
Description of problem:

dumpStorageTable produces an avoidable traceback if vdsmd is down. This is in turn picked up by abrt and can worry users.

# service vdsmd stop
Shutting down vdsm daemon: 
vdsm watchdog stop                                         [  OK  ]
vdsm stop                                                  [  OK  ]
# python /usr/share/vdsm/dumpStorageTable.py
Traceback (most recent call last):
  File "/usr/share/vdsm/dumpStorageTable.py", line 307, in <module>
    rc, msg = StorageTable(vdscli.connect()).show()
  File "/usr/share/vdsm/dumpStorageTable.py", line 34, in __init__
    self._buildStorageTable()
  File "/usr/share/vdsm/dumpStorageTable.py", line 164, in _buildStorageTable
    pools = self.serverConncetion.getConnectedStoragePoolsList()
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
    self.send_content(h, request_body)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
    connection.endheaders()
  File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
    self._send_output()
  File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
    self.send(msg)
  File "/usr/lib64/python2.6/httplib.py", line 739, in send
    self.connect()
  File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 165, in connect
    sock = socket.create_connection((self.host, self.port), self.timeout)
  File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
    raise error, msg
socket.error: [Errno 111] Connection refused

Version-Release number of selected component (if applicable):
vdsm-4.10.2-23.0.el6ev.x86_64


How reproducible:
Always.

Steps to Reproduce:
1. Stop vdsmd.
2. Run dumpStorageTable.py.
3.

Actual results:
Connection refused traceback displayed and captured by abrt.

Expected results:
No traceback displayed or captured by abrt.

Additional info:

Comment 4 Aharon Canan 2013-08-15 12:27:12 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

Comment 5 Charlie 2013-11-28 00:26:30 UTC
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.

Comment 6 errata-xmlrpc 2014-01-21 16:29:45 UTC
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