f670f704f3
Heartbeat connection errors are often a sign of a transitory network failures which may resolve themselves. But an operator looking at the screen doesn't necessarilly know that. They don't understand that there could have been a network failure, or a misconfiguration that caused the connectivity failure and soft of kind of default to "well it failed" without further clarification. As such, this patch adds explicit catching of the requests ConnectionError exception and rasies a new internal error with a more verbose error message in that event to provide operators with additional clarity. Change-Id: I4cb2c0d1f577df1c4451308bd86efa8f94390b0c Story: 2008046 Task: 40709
11 lines
481 B
YAML
11 lines
481 B
YAML
---
|
|
other:
|
|
- |
|
|
Adds an explicit capture of connectivity failures in the heartbeat
|
|
process to provide a more verbose error message in line with what is
|
|
occuring as opposed to just indicating that an error occured. This
|
|
new exception is called ``HeartbeatConnectionError`` and is likely only
|
|
going to be visible if there is a local connectivity failure such as a
|
|
router failure, switchport in a blocking state, or connection centered
|
|
transient failure.
|