Modify

Ticket #621 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

Improper TLSError handling in Proxy.py

Reported by: kisielk Owned by: desai
Priority: major Milestone:
Component: bcfg2-client Version:
Keywords: Cc:

Description

A traceback from the bcfg2 client:

Traceback (most recent call last):
  File "/usr/sbin/bcfg2", line 453, in ?
    client.run()
  File "/usr/sbin/bcfg2", line 335, in run
    proxy.RecvStats(Bcfg2.Client.XML.tostring(feedback, encoding='UTF-8', xml_declaration=True))
  File "/usr/sbin/bcfg2", line 45, in __call__
    return self.method(*args)
  File "/usr/lib64/python2.4/site-packages/Bcfg2/Proxy.py", line 41, in __call__
    self.log.error("Unexpected TLS Error: %s. Retrying" % \
AttributeError: TLSAbruptCloseError instance has no attribute 'message'

The offending line in Proxy.py:

except Bcfg2.tlslite.errors.TLSError, err:
                self.log.error("Unexpected TLS Error: %s. Retrying" % \
                               (err.message))

I believe that replacing err.message with just err fixes the problem (although for my particular error the message is just "Unexpected TLS Error: . Retrying" and I don't know why that is happening, but that's a separate issue).

Attachments

Change History

comment:1 Changed 13 years ago by desai

  • Status changed from new to closed
  • Resolution set to fixed

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.