Comment 5 for bug 1684049

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")'