modeloperator configmap not updated after initial creation
Bug #2036849 reported by
James Simpson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Committed
|
Medium
|
Harry Pidcock | ||
Bug Description
Hi,
After recently scaling up one of our controller models (2.9.44), I've noticed that the "modeloperator" configmap for caas models hosted on the controller hasn't been updated to include the new controller IP addresses.
It looks like this configmap is never updated after it's created.
Please let me know if any other information is required.
Thanks!
| tags: | added: canonical-is |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #1 |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #2 |
| Changed in juju: | |
| importance: | Undecided → Medium |
| milestone: | none → 2.9.46 |
| status: | New → In Progress |
| assignee: | nobody → Harry Pidcock (hpidcock) |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
The caasmodeloperator worker never updates the agent config for the model operator. This means that it never receives new api addresses. A fix here would be to change the worker to watch all the inputs to the provisioning info, if it changes, update the agent config and re-ensure the model operator.