model marked as removed after migration aborted

Bug #1989050 reported by Yang Kelvin Liu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

The model marked as removed in statepool after a model migration failed and aborted.

# 1st migration failed and aborted
$ juju migrate k1:default k2
Migration started with ID "0d8e1385-66cd-4d44-8b0f-0af4bb524ac1:2"
# 2nd try failed again: the source controller thinks the model already migrated but actually the model is still on the source. It seems the StatePool out of sync `p.pool[modelUUID].remove == true` now
$ juju migrate k1:default k2
ERROR target prechecks failed: model 0d8e1385-66cd-4d44-8b0f-0af4bb524ac1 has been removed (not found)

$ juju models
Controller: k1

Model Cloud/Region Type Status Machines Units Access Last connection
controller localhost/localhost lxd available 1 1 admin just now
default* localhost/localhost lxd available 2 2 admin just now

Changed in juju:
milestone: none → 3.0-rc1
description: updated
Changed in juju:
status: New → Triaged
importance: Undecided → High
tags: added: model-migration
Changed in juju:
milestone: 3.0-rc1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.