Mixing colocation and multiple unit leads to unexpected result
Bug #1687663 reported by
Vincenzo Di Somma
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Menno Finlay-Smits |
Bug Description
juju add-unit ubuntu -n 4 --to 0 resulted in one new unit on machine 0 and 3 new machines created.
https:/
juju version 2.2-beta2-
Changed in juju: | |
milestone: | 2.2.0 → 2.2-rc1 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
That is intended behavior. If you want to create 4 instances on one machine
you would have to specify:
juju add-unit ubuntu -n4 --to 0,0,0,0
as you might actually want:
juju add-unit ubuntu -n4 --to 0,1,2,3
or any other number of combinations, the logic is to accept the arguments
of '--to' but provide the rest of the machines in the same fashion we would
provide them without any --to argument (e.g. request new instances).
There is an argument that we should require the number of arguments in
'--to' to match the -nX value, but we would need a way to specify a 'new
machine' in the --to argument.
On Tue, May 2, 2017 at 12:25 PM, Vincenzo Di Somma <
<email address hidden>> wrote:
> Public bug reported: /paste. ubuntu. com/24497481/ xenial- amd64 with Openstack Ocata /bugs.launchpad .net/bugs/ 1687663 /bugs.launchpad .net/juju/ +bug/1687663/ +subscriptions
>
> juju add-unit ubuntu -n 4 --to 0 resulted in one new unit on machine 0
> and 3 new machines created.
>
>
> https:/
>
> juju version 2.2-beta2-
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Mixing colocation and multiple unit leads to unexpected result
>
> To manage notifications about this bug go to:
> https:/
>