Closed tnesztler closed 5 years ago
@tnesztler this issue came about when I changed from using the agent_uuid to identity which is more appropriate in the alerting system. Shortly I will be submitting a pull request for this issue.
@tnesztler please see pull request #2010
@tnesztler reopen if you see this issue again.
Description of Issue
In our custom Historian agent, there seem to be a bug relating to the Health subsystem of the BaseHistorianAgent. When the agent goes from GOOD to BAD, it tries to send a message to the ALERTS topic. This doesn't work anymore due to the switch from Agent UUID to Identity (https://github.com/VOLTTRON/volttron/blob/develop/volttron/platform/vip/agent/subsystems/health.py#L91). I believe the latter cannot be serializable by looking at the Traceback we got when the agent couldn't push data. This however resulting in the agent crashing altogether vs skipping this round of publishing.
NOTE We are not running any Platform agent, only BACnetProxy, MasterDriverAgent and a custom Historian. This could explain the error we see in the first part of the Traceback.
Affected Version
Develop
Screenshots
Expected
Alerts are sent to the appropriate topic which can be picked up by another agent later on.
Actual
The BaseHistorian agent is unable to send the alert and crashes.
Steps to Reproduce
Use an agent that is based on BaseHistorianAgent, or probably BaseHistorianAgent itself, make it run into a publishing fault.
Additional Details