controller migration is very hard when dealing with large deployments
Bug #1918680 reported by
Aymen Frikha
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips | ||
2.8 |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
Hello trying to do the controller migration from xenial controller to bionic one with a big openstack environment.
The migration keep failing because there is some units are in executing mode.
Is it possible to add a feature for juju to prevent all the agents from executing to be able to do the migration smoothly ?
We are using juju 2.8.9
Changed in juju: | |
assignee: | nobody → Joseph Phillips (manadart) |
milestone: | none → 2.8.11 |
Changed in juju: | |
milestone: | 2.8.11 → 2.9-next |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.5 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There is something odd happening here. We should be allowing migration to proceed if the agent status is "idle" or "executing".
It is others that we stop for: allocating/ rebooting/ failed/ lost.
If we encounter this again, I would very much like to see what the status actually is.