restore-backup ignores constrains; impossible to recover rackspace/dfw

Bug #1641232 reported by Curtis Hovey
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Seyeong Kim

Bug Description

I cannot restore my controller in rackspace. Juju selects a favor with no disk (compute1-4)! The bootstrap command just works. It selected a "1GB Standard Instance" flavor with 40G disk. I can also pass the root-disk constrain the bootastrap to get a bigger disk. The restore-backup command ignores the root-disk constraint.

...
Launching controller instance(s) on rackspace/dfw...
ERROR cannot bootstrap new instance: cannot start bootstrap instance: cannot run instance: failed to run a server with nova.RunServerOpts{Name:"juju-c9e07e-controller-0", FlavorId:"compute1-4", ImageId:"d25e277b-e279-490b-b8f1-5293add22ec0" ...

And passing "--constraints root-disk=40G" does *not* direct juju to select different flavor.

$ juju restore-backup -m bc-test:controller -b --constraints root-disk=40G --file bc-backup.tar.gz
...
Launching controller instance(s) on rackspace/dfw...
ERROR cannot bootstrap new instance: cannot start bootstrap instance: cannot run instance: failed to run a server with nova.RunServerOpts{Name:"juju-c9e07e-controller-0", FlavorId:"compute1-4", ImageId:"d25e277b-e279-490b-b8f1-5293add22ec0" ...

Because of bug 1641224, I cannot specify instance-type "1GB Standard Instance", so it is not possible to restore in dfw. The flavors in iad are different, and Horatio reported he could restore there.

Revision history for this message
Tim Penhey (thumper) wrote :
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Seyeong Kim (xtrusia)
milestone: none → 2.3-alpha1
Changed in juju:
milestone: 2.3-beta1 → 2.3-beta2
Changed in juju:
milestone: 2.3-beta2 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR linked in comment # 1 has been merged since 2.3-beta1. I will mark this report as Fix Released.

Changed in juju:
milestone: none → 2.3-beta1
status: In Progress → Fix Released
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.