Restore cannot detect whether old instance is still running

Bug #1556167 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 in
    http://reports.vapour.ws/releases/issue/56e2d71f749a56463a44a285

Restore cannot detect whether old instance is still running. This issues was seen ling ago in bug 1425807.

We can see that each controller was deleted by the provider and the script waited for the port to close to be certain the machine didn't exist before calling restore

Restore failed:
2016-03-10 22:18:52 INFO juju.cmd supercommand.go:59 running juju [2.0-beta2 gc go1.2.1]
2016-03-10 22:18:52 INFO juju.environs.local/share config.go:521 Based on your "provisioner-safe-mode" setting, configuring "provisioner-harvest-mode" to "destroyed".
2016-03-10 22:18:52 INFO juju.provider.ec2 provider.go:48 opening model "functional-ha-backup-restore"
2016-03-10 22:18:57 ERROR cmd supercommand.go:448 cannot detect whether old instance is still running: only some instances were found

affects: juju-core → juju
Revision history for this message
John A Meinel (jameinel) wrote :

This hasn't seen changes on it for >1year. If it happens again, we can certainly reopen this issue.

Changed in juju:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
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.