[Bug 1773765] Fix proposed to masakari (stable/ussuri)

OpenStack Infra 1773765 at bugs.launchpad.net
Thu Sep 24 03:01:36 UTC 2020


Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/753921

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to masakari in Ubuntu.
https://bugs.launchpad.net/bugs/1773765

Title:
  There is a possibility that 'running' notification will remain

Status in masakari:
  In Progress
Status in masakari package in Ubuntu:
  New

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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/masakari/+bug/1773765/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list