[Fixed] Issue deploying apps: "no provisioned machines" with two machines ready

juju
1

Using 2.6.2-bionic-amd64 from snap store

When trying to deploy any charm on my local environment, I get the following error (log shortened)

[...]
09:59:57 INFO  cmd deploy.go:1566 Located charm "cs:trusty/mariadb-7".
09:59:57 INFO  cmd deploy.go:1567 Deploying charm "cs:trusty/mariadb-7".
09:59:57 DEBUG juju.api monitor.go:35 RPC connection died
ERROR cannot add application "mariadb": use "juju add-machine ssh:[user@]<host>" to provision machines
09:59:57 DEBUG cmd supercommand.go:496 error stack: 
cannot add application "mariadb": use "juju add-machine ssh:[user@]<host>" to provision machines
/build/juju/parts/juju/go/src/github.com/juju/juju/api/application/client.go:161: 
/build/juju/parts/juju/go/src/github.com/juju/juju/cmd/juju/application/deploy.go:209: 
/build/juju/parts/juju/go/src/github.com/juju/juju/cmd/juju/application/deploy.go:1064: 
/build/juju/parts/juju/go/src/github.com/juju/juju/cmd/juju/application/deploy.go:1572:

My env is comprised of an LXD container and a multipass VM, all reachable (tried with ping + ssh)
Below is the output of juju status --format=yaml

model:
  name: default
  type: iaas
  controller: dev-ctrl0
  cloud: manual
  version: 2.6.2
  model-status:
    current: available
    since: 21 May 2019 08:24:27+02:00
  sla: unsupported
machines:
  "0":
    juju-status:
      current: started
      since: 21 May 2019 08:25:43+02:00
      version: 2.6.2
    dns-name: 10.233.237.185
    ip-addresses:
    - 10.233.237.185
    - fd42:1ff:2c28:5841:216:3eff:fe49:ae07
    instance-id: manual:10.233.237.185
    machine-status:
      current: running
      message: Manually provisioned machine
      since: 21 May 2019 08:24:57+02:00
    modification-status:
      current: idle
      since: 21 May 2019 08:24:54+02:00
    series: bionic
    network-interfaces:
      eth0:
        ip-addresses:
        - 10.233.237.185
        - fd42:1ff:2c28:5841:216:3eff:fe49:ae07
        mac-address: 00:16:3e:49:ae:07
        gateway: 10.233.237.1 10.233.237.1
        is-up: true
    hardware: arch=amd64 cores=12 mem=16035M
  "1":
    juju-status:
      current: started
      since: 21 May 2019 08:29:54+02:00
      version: 2.6.2
    dns-name: 10.48.61.243
    ip-addresses:
    - 10.48.61.243
    instance-id: manual:10.48.61.243
    machine-status:
      current: running
      message: Manually provisioned machine
      since: 21 May 2019 08:29:08+02:00
    modification-status:
      current: idle
      since: 21 May 2019 08:29:04+02:00
    series: bionic
    network-interfaces:
      ens3:
        ip-addresses:
        - 10.48.61.243
        mac-address: 52:54:00:80:eb:b8
        gateway: 10.48.61.1
        is-up: true
    hardware: arch=amd64 cores=4 mem=3944M
applications: {}
storage: {}
controller:
  timestamp: 09:55:46+02:00

Any idea what could have gone wrong ? This is a fresh install of Juju and both machines have been freshly recreated for that deployment

Thanks

2

I believe it’s a replica of the follow #1829559, which currently being worked on.

3

Could be, but I have the exact same behavior with juju/2.5.7-bionic-amd64, so I think it’s more about a local configuration issue, I’m just not sure where to look

4

Can you deploy targeting those machines?

e.g.

juju deploy --to 0
5

juju deploy cs:elasticsearch-37 --to 0 does indeed work, so that might be related to the bug @simonrichardson mentionned

6

The bugs were indeed the same.
Fixed by https://github.com/juju/juju/pull/10209

1 Like
7

Thanks for checking. Glad we’re getting it straightening out.