openstack: juju failed to launch instance, remains pending forever

[Andreas Hasenack]

Juju 1.24.2 failed to launch an instance in openstack:
(...)
  "2":
    agent-state-info: |-
      cannot run instance: failed to run a server with nova.RunServerOpts{Name:"juju-cistack-crew-machine-2", FlavorId:"1", ImageId:"4fd9d081-4454-4356-a779-ecc5d88c3520", UserData:[]uint8{0x1f, 0x8b....0xf2,
      caused by: request (http://10.96.10.161:8774/v2/7351c067e10243bead6ee92da14f7986/servers) returned unexpected status: 400; error info: {"badRequest": {"message": "Flavor's disk is too small for requested image.", "code": 400}}
    instance-id: pending
    series: trusty
(...)
  landscape-server:
    charm: local:trusty/landscape-server-0
    exposed: false
    service-status:
      current: unknown
      message: Waiting for agent initialization to finish
      since: 09 Jul 2015 16:31:08-03:00
    units:
      landscape-server/0:
        workload-status:
          current: unknown
          message: Waiting for agent initialization to finish
          since: 09 Jul 2015 16:31:08-03:00
        agent-status:
          current: allocating
          since: 09 Jul 2015 16:31:08-03:00
        agent-state: pending
        machine: "2"

It's really not launched, nova list confirms it. Yet juju happily waits forever, instead of transitioning it to a failed state. That charm will never deploy.

[Andreas Hasenack (ahasenack)]

Are you sure it's a duplicate? There it's a bootstrap problem, here it's post-bootstrap. In bug #1472711 Ian said that Bootstrap and StartInstance were different cases.

[Ian Booth (wallyworld)]

This is slightly different to bug 1472711. In that bug, Juju didn't know there was an error deploying the maas instance because it never asks. In this case, Juju does know that there is a problem. There error is reported. The machine state shows the error. But the unit states remaining pending. Perhaps the unit states should indicate if their host machine can't start.

[Heather Lanigan (hmlanigan)]

Two questions:

1) Are there specific steps to reproduce this bug?
2) Can it be reproduced with the latest version of juju 2?

[Launchpad Janitor (janitor)]

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