There is a possibility that 'running' notification will remain

Bug #1773765 reported by takahara.kengo on 2018-05-28
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

masakari-engine has two periodic tasks, one for processing 'new' notifications and the other for processing 'error' notifications But it doesn't have a periodic task for processing 'running' notifications.

Looking at the code of masakari-engine, if the process of it goes down immediately after it changes notification status from 'new' to 'running', then the notification which status is 'running' will remain will not be processed by periodic tasks.

So, should masakari-engine's periodic task process the 'running' notification?
(Although it need to make such a logic that main process doesn't compete with periodic tasks.)
Or should the 'running' notification be handled by the operator?

Peter De Sousa (pjds) wrote :

Hit this bug yesterday, I was unable to reset my compute node status using

`openstack segment host update $SEGMENT_UUID node01 --on_maintenance False`.

After much digging I noticed that there was still a notification with "running".

I worked around this by logging into the DB and deleting the running record from the notifications table.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers