Juju-deployer skips deployment to some machines when multiple are specified with 'to:'

Bug #1630383 reported by Tim Kuhlman
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-deployer
New
Undecided
Unassigned

Bug Description

Using a bundle file like the following simplified version:

controllers:
  series: "xenial"
  machines:
    "0":
      series: "xenial"
      constraints: arch=amd64
    "1":
      series: "xenial"
      constraints: arch=amd64
    "2":
      series: "xenial"
      constraints: arch=amd64
  services:
     ubuntu:
      charm: ubuntu
      to: ["0", "1", "2"]

After a deploy the ubuntu service is running on machine 0 but not on machine 1 or 2.

Revision history for this message
Tim Kuhlman (timkuhlman) wrote :

This is running with Juju 2.0-rc1 and the latest juju-deployer from the ppa ppa:tvansteenburgh/ppa

Revision history for this message
Junaid Ali (junaidali) wrote :

It affected me too, in my case it was picking the machines randomly where I also specified 3 units. Sometimes it deploys all the units to one machine and sometimes it deploys on two machines with two units on a single machine.

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.