static controller_ip_port_list approach doesn't adapt to changes in controllers
Bug #1685225 reported by
Brent Eagles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| octavia |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Once an amphora has been instantiated, the nodes referenced in the controller_ip_port list are fixed according to the controllers that were configured at that time. If more controllers are added and the original controllers are retired or shutdown temporarily, the amphora will not be able to communicate with the new controllers.
Revision history for this message
| Michael Johnson (johnsom) wrote | #1 |
| Changed in octavia: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Gregory Thiemonge (gthiemonge) wrote auto-abandon-script | #2 |
| Changed in octavia: | |
| status: | Triaged → Invalid |
| tags: | added: auto-abandon |
To post a comment you must log in.
Yes, we intend to have a method to update the configurations inside the amphora. We ran into a problem with flask/werkzeug failing when a new configuration was adopted. We have replaced that code with gunicorn and this issue should now be resolved. We just need to circle back and complete the code that allows configuration updates. Thank you for opening the bug to track it.