Unimportant API resource updates get sent to the queue
Bug #1415283 reported by
Brandon Logan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| octavia |
Invalid
|
Low
|
Unassigned | ||
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 |
| Changed in octavia: | |
| assignee: | nobody → Atul Pandey (atul-4you) |
Revision history for this message
| Atul Pandey (atul-4you) wrote | #1 |
| Changed in octavia: | |
| status: | Confirmed → Incomplete |
Revision history for this message
| Gregory Thiemonge (gthiemonge) wrote auto-abandon-script | #2 |
| Changed in octavia: | |
| assignee: | Atul Pandey (atul-4you) → nobody |
| status: | Incomplete → Invalid |
| tags: | added: auto-abandon |
To post a comment you must log in.
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.