Migration failed because controller was intermittently down

Bug #1629961 reported by Curtis Hovey
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

As seen at
    http://reports.vapour.ws/releases/issue/57f297ce749a560c8380894d

We can see from the progress of the test and status that the controller on machine 0 was up before migrate was called. It is up after the failure, but migrate reports:

ERROR cmd supercommand.go:458 source prechecks failed: controller: machine 0 agent not functioning at this time (down)
2016-10-03 12:00:38 ERROR Command '('juju', '--show-log', 'migrate', '-c', 'functional-model-migration', 'example-model', 'functional-model-migration-b')' returned non-zero exit status 1

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
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.