Looks like this bug was introduced back in Queens with this change:
https://review.opendev.org/511358
There is one call site where MaxRetriesExceeded is raised that is not inside a try-except block. This is why the proper notification and setting of instance to ERROR state does not occur in that case.
Looks like this bug was introduced back in Queens with this change:
https:/ /review. opendev. org/511358
There is one call site where MaxRetriesExceeded is raised that is not inside a try-except block. This is why the proper notification and setting of instance to ERROR state does not occur in that case.