juju2 manually provisioned units stuck in machine-status pending

Hi,

When manually provisioning a machine in juju2, it will be reported as "Started" in juju status (tabular format by default), but machine-status will remain forever pending in yaml output.
To reproduce:

$ juju add-machine ssh:10.213.76.211

$ juju status
[...]
Machine State DNS Inst id Series AZ
0 started 10.213.76.211 manual:10.213.76.211 xenial

$ juju status --format=yaml
[...]
model:
  name: default
  controller: local-controller
  cloud: localhost
  region: localhost
  version: 2.1.2.1
machines:
  "0":
    juju-status:
      current: started
      since: 03 Apr 2017 08:15:31Z
      version: 2.1.2.1
    dns-name: 10.213.76.211
    ip-addresses:
    - 10.213.76.211
    instance-id: manual:10.213.76.211
    machine-status:
      current: pending
      since: 31 Mar 2017 08:15:36Z
    series: xenial
    hardware: arch=amd64 cores=2 mem=7881M
applications: {}

This is blocking mojo deployments using juju-check-wait, because 'pending' is not considered a 'ready' state (understandably).

Thanks,
Laurent