failure to migrate a model -- meter status "" is not valid

Bug #1696828 reported by Richard Harding
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Status tracked in Trunk
2.2
Fix Released
Undecided
Casey Marshall
Trunk
Fix Released
High
Casey Marshall

Bug Description

I'm attempting to perform an upgrade migration of models from current stable juju (2.1.3) to the latest RC (2.2-rc1).

I've bootstrapped on AWS and created two models. In one is kubernetes-core and in the other is cs:~spiculecharms/bundle/gitlab-ssl

I then bootstrapped an rc1 model and attempted to migrate.

juju migrate devcode aws-2-2

I also tried to migrate the k8 model

juju migrate k8s aws-2-2

Both failed. debug-log from the devmode model shows:

machine-0: 14:29:19 ERROR juju.worker.migrationmaster.ebb58a model data transfer failed, failed to import model into target controller: meter status "" not valid

The migration of the k8s model failed with:

machine-0: 14:35:37 ERROR juju.worker.migrationmaster.854ca8 model data transfer failed, failed to import model into target controller: meter status "" not valid
machine-0: 14:35:44 ERROR juju.worker.firewaller failed to lookup "unit-kubernetes-master-0", skipping port change

I'm not yet sure if the second line here is a second failure path or not.

Changed in juju:
assignee: nobody → Casey Marshall (cmars)
Casey Marshall (cmars)
Changed in juju:
status: New → In Progress
Revision history for this message
Casey Marshall (cmars) wrote :
Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

This is still happening when migrating a model from 2.1 controller to current upstream/develop (2.3) controller. I was migrating a model with a single unit of the "ubuntu" charm.

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

Of course, I've now just tried to reproduce and it didn't happen... maybe I was using an older 2.3 before without the fix. I'll dig some more.

Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I suspect that the fix for this has been already ported into 2.3 (develop) as part of one of the larger merge we have undertaken recently.

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.