Unimportant API resource updates get sent to the queue

Bug #1415283 reported by Brandon Logan on 2015-01-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Incomplete
Low
Atul Pandey

Bug Description

If a user updates just the name or description of an object, then it would probably be best to just do the update and at the API layer and not send it to the queue because a name or description change shouldn't need any changes after the database is updated.

Changed in octavia:
importance: Undecided → Low
Changed in octavia:
status: New → Confirmed
Atul Pandey (atul-4you) on 2016-09-22
Changed in octavia:
assignee: nobody → Atul Pandey (atul-4you)
Atul Pandey (atul-4you) wrote :

AFAIK , it looks like during db changes the status gets updated to pending_updates and sent to queue for further processing. Once the message is processed in queue that notification is sent back to loadbalancer to change it to active state. Do we want this Status updates to be done without sending it to the queues?

In my setup when i prevent these updates to be sent to queues it remains in pending_update state.

Please let me know if this understanding is incorrect.

Atul Pandey (atul-4you) on 2016-09-27
Changed in octavia:
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers