No way to force placement on machines other than 0

[Jacek Nykis]

I can't find a way to force placement to specific machiens with "to:" key.

Test deployer config I used:
myservice:
  series: trusty
  services:
    test-stuff:
      charm: ubuntu
      num_units: 2
      to: [14,15]

Which I then execute like this:
jacek@trusty1:~$ juju-deployer -c <filename> myservice
2015-10-26 15:44:35 Starting deployment of myservice
2015-10-26 15:44:35 Service placement to machinenot supported test-stuff to 14
2015-10-26 15:44:35 Service placement to machinenot supported test-stuff to 15
2015-10-26 15:44:35 Deployment stopped. run time: 0.26

This should be possible in deployer 0.5.0 and newer as per LP1454720

juju-deployer 0.6.0-1
Ubuntu 14.04.3 LTS

[Nuno Santos (nunosantos)]

I've seen this too, but only happens with named bundles (with a top-level identifier -- "myservice" in the original bug report). Removing that allows service placement to work as expected.

[Tim Van Steenburgh (tvansteenburgh)]

Nuno or Jacek, I haven't tested it yet, but just pushed a probable fix for this to the linked branch. If either or you want to try it, please let me know if it fixes this problem for you.

[Nuno Santos (nunosantos)]

I've tested the branch and it does fix the issue for me -- thank you!