Canonical Juju

migration import fails with subordinate charms

Bug #1650249 reported by Menno Finlay-Smits
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Christian Muirhead
Canonical Juju 2.1-rc1

Bug Description

Model migrations can fail if subordinate units are imported before the principal. I saw this when attempting to migrate a kubernetes deployment.

Here's the error from the migrationmaster worker:

ERROR juju.worker.migrationmaster:baed22 model data transfer failed, failed to import model into target controller: applications: filebeat: principal unit "kubernetes-master/0" of "filebeat/0" not found (not found)

Revision history for this message
Christian Muirhead (2-xtian) wrote :

PR: https://github.com/juju/juju/pull/6731

Changed in juju:
status: New → In Progress
assignee: Tim Penhey (thumper) → Christian Muirhead (2-xtian)
Christian Muirhead (2-xtian)
Changed in juju:
status: In Progress → Fix Committed
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Backport to 2.1 branch: https://github.com/juju/juju/pull/6734

Anastasia (anastasia-macmood)
Changed in juju:
milestone: 2.1.0 → 2.1-rc1
Curtis Hovey (sinzui)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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