Juju model migration fails during validation phase
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
When trying to migrate a model between 2 controllers on Juju version
2.8.0, the migration fails due to error:
ERROR agents failed phase "validating" (machines: 1,2,3,5,8,9,10; units: calico/
ERROR validating, some agents reported failure
This happens due to the rate-limiting on the target controller rejecting
the stampede of connections as all the agents start up again. This is
something model migration has not specifically been coded to handle.
To work around this issue, you need to set the following config on the
destination controller:
agent-ratelimit-max (default is 10): Should be set to a value at least equal
to the number of units (including subordinates) on the model being migrated.
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in juju: | |
milestone: | none → 2.8-next |
tags: | added: model-migration |
Changed in juju: | |
assignee: | nobody → Joseph Phillips (manadart) |
milestone: | 2.8-next → 2.8.8 |
status: | Confirmed → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
How "agent- ratelimit- max" can be changed, can't find it in the controller or model config?