Comment 6 for bug 1684049

That seems to fairly clearly say that --to was turned into a name
constraint and joined with constraints rather than overriding.
I wonder if it would be different if it was an already added machine. eg
 juju add-machine nuc4.maas
 juju enable-ha -n3 --to 1

John
=:->

On Jul 26, 2017 13:11, "Anastasia" <email address hidden> wrote:

> I've tried to verify the fix but.
>
> My setup included nuc1.maas and nuc2.maas nodes tagged with "wanted" and
> nuc4.maas node untagged.
>
> For all 3 versions of Juju that I have tested, I followed this scenario:
>
> a. bootstrapped one controller with '--constraints "tags=wanted"' in
> command;
> b. ran 'juju enable-ha -n 3 --to nuc4.maas'
>
> In all 3 runs, nuc1.maas and nuc2.maas (tagged) came up without an
> issue. nuc4.maas (untagged) did not come up and gave a similar error.
>
> On develop (v2.3-alpha1) and 2.2 tip (v2.2.3):
>
> machine-status:
> current: provisioning error
> message: 'cannot run instances: cannot run instance: No available
> machine matches
> constraints: [(''agent_name'', [''c539ce51-c26a-4375-8ad8-
> b5a79cc1d2ca'']),
> (''name'', [''nuc4.maas'']), (''tags'', [''wanted''])] (resolved
> to "name=nuc4.maas
> tags=wanted")'
>
> On 2.1 tip (v2.1.4):
>
> machine-status:
> current: provisioning error
> message: 'cannot run instances: cannot run instance: No available
> machine matches
> constraints: [(''agent_name'', [''c75ba7e8-132c-42c0-8c88-
> 260e4c83197e'']),
> (''mem'', [''3584'']), (''name'', [''nuc4.maas'']), (''tags'',
> [''wanted''])]
> (resolved to "mem=3584.0 name=nuc4.maas tags=wanted")'
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1684049
>
> Title:
> enable-ha to specific machine should ignore 'tags' constraints
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1684049/+subscriptions
>