
If an user sends host notification without host status: openstack notification create COMPUTE_HOST <host> <date> '{"event": "STOPPED"}' logging registers silly error like object None has not method 'upper' and notification gets status 'running', host is set in maintenance status. It's impossible to set manually host status to non-maintanence until there are host-related running notifications. Running notifications are expired in 24 hours by default. The patch makes engine to set 'ignore' status for such notifications. Closes-Bug: 1960619 Change-Id: Id873b3300b6de49082805654c85414a8868dd925
9 lines
326 B
YAML
9 lines
326 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue that could be caused by a user sending a malformed
|
|
host notification missing host status. Such notification would
|
|
block the host from being added back from maintenance until
|
|
manual intervention or notification expiration.
|
|
`LP#1960619 <https://launchpad.net/bugs/1960619>`__
|