manual provider shows started machine as "pending"

Bug #1606709 reported by Tim Penhey
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

From:
http://reports.vapour.ws/releases/4175/job/manual-deploy-precise-amd64/attempt/3743

machines:
  "0":
    juju-status:
      current: started
      since: 26 Jul 2016 20:50:10Z
      version: 2.0-beta14
    dns-name: ec2-52-91-58-145.compute-1.amazonaws.com
    instance-id: manual:ec2-52-91-58-145.compute-1.amazonaws.com
    machine-status:
      current: pending
      since: 26 Jul 2016 20:48:51Z
    series: precise
    hardware: arch=amd64 cpu-cores=1 mem=7450M
  "1":
    juju-status:
      current: started
      since: 26 Jul 2016 20:50:48Z
      version: 2.0-beta14
    dns-name: ec2-54-87-148-186.compute-1.amazonaws.com
    instance-id: manual:ec2-54-87-148-186.compute-1.amazonaws.com
    machine-status:
      current: pending
      since: 26 Jul 2016 20:50:14Z
    series: precise
    hardware: arch=amd64 cpu-cores=1 mem=7450M

affects: juju-core → juju
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.