Unhandled error stopping pybal: 'RunCommandMonitoringProtocol' object has no attribute 'checkCall'
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• ema
	Feb 10 2017, 9:57 AM

Description

On LVS hosts with RunCommand monitors configured, stopping pybal causes the following unhandled exception to be logged several times:

Feb 09 16:19:00 lvs1012 pybal[2034]: File "/usr/lib/python2.7/dist-packages/pybal/monitors/runcommand.py", line 123, in stop
Feb 09 16:19:00 lvs1012 pybal[2034]: if self.checkCall and self.checkCall.active():
Feb 09 16:19:00 lvs1012 pybal[2034]: exceptions.AttributeError: 'RunCommandMonitoringProtocol' object has no attribute 'checkCall'

Related Objects

Mentioned Here: rODCBacdd0ebf74e5: Implement common base class for "looping check" monitors

Event Timeline

• ema created this task.Feb 10 2017, 9:57 AM

Restricted Application added a project: SRE. · View Herald TranscriptFeb 10 2017, 9:57 AM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

• ema triaged this task as Medium priority.Feb 10 2017, 9:57 AM

• ema moved this task from Backlog to LoadBalancer on the Traffic board.Feb 10 2017, 12:02 PM

This has been addressed in acdd0ebf74e5dd9e06c3216b9a93063ab8e91574

Unhandled error stopping pybal: 'RunCommandMonitoringProtocol' object has no attribute 'checkCall'Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Unhandled error stopping pybal: 'RunCommandMonitoringProtocol' object has no attribute 'checkCall'
Closed, ResolvedPublic
Actions