Just to make sure we're talking about the same thing, when I ask maas
for a machine without the 'virtual' tag, it gives me a machine with
the 'virtual' tag.

I wasn't asking for a pod machine at all - that would be filtering on
pods and I agree that would be a feature request. I was specifically
trying to get a non virtual machine, and as a side effect of having a
pod on the same MAAS, it didn't work.

I consider that a bug, but feel free to consider it a missing feature
- I don't really care about that part ;).

On Mon, Feb 26, 2018 at 7:37 PM, Andres Rodriguez
<email address hidden> wrote:
> FWIW,
>
> This is now part of 2.4 pod improvements among other requested features.
>
> On Mon, Feb 26, 2018 at 8:10 PM Andres Rodriguez <email address hidden>
> wrote:
>
>> @Jason,
>>
>> As you described in the bug report, you were hoping to use a 'no_tag'
>> constraint to prevent allocating machines from a pod. A pod has no
>> knowledge whatsoever of the concept of tags, so you can't really use
>> 'tags' or 'no_tags' to constraint allocation. The fact that MAAS tags
>> machines coming from a pod a specific way is completely irrelevant and
>> unrelated to /allocation/ from pods. As per your use case and
>> expectation, it then means that you have a use case that's currently not
>> supported, and to do so, MAAS would need to gain such feature.
>>
>> That said, I agree with you; cdo-qa-blocker means this causes tests
>> failures when a /supported/ use case results in failures. In this
>> particular case, the expected use case is /not/ supported, and the
>> output is expected.
>>
>> As such, the tag doesn't apply because you are using it in an
>> unsupported way. If you were to be using it in a supported way and it
>> would be failing, then the tag does apply.
>>
>> That said, I think we both agree that gaining such support would be
>> nice!
>>
>> --
>> You received this bug notification because you are subscribed to MAAS.
>> https://bugs.launchpad.net/bugs/1751907
>>
>> Title:
>>   [2.3, wishlist] Support tag filtering (via tag/no_tag) in pods.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1751907/+subscriptions
>>
>> Launchpad-Notification-Type: bug
>> Launchpad-Bug: product=maas; milestone=2.4.x; status=Triaged;
>> importance=Medium; assignee=None;
>> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine kvm pod
>> Launchpad-Bug-Information-Type: Public
>> Launchpad-Bug-Private: no
>> Launchpad-Bug-Security-Vulnerability: no
>> Launchpad-Bug-Commenters: andreserl jason-hobbs
>> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
>> Launchpad-Bug-Modifier: Andres Rodriguez (andreserl)
>> Launchpad-Message-Rationale: Subscriber (MAAS)
>> Launchpad-Message-For: andreserl
>>
> --
> Andres Rodriguez (RoAkSoAx)
> Ubuntu Server Developer
> MSc. Telecom & Networking
> Systems Engineer
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1751907
>
> Title:
>   [2.3, wishlist] Support tag filtering (via tag/no_tag) in pods.
>
> Status in MAAS:
>   Triaged
>
> Bug description:
>   To reproduce:
>   1) Setup a maas and add a KVM pod to it, without any other machines added to it.
>   2) With no machines available, try to allocate a machine with the not_tags parameter set to virtual:
>
>   maas <profile> machines allocate not_tags=virtual
>   3) Since any pod KVM created will have the tag 'virtual' after it's commissioned, the expected behavior is that maas returns an error stating no machines are available. Instead, MAAS creates a KVM machine from its pod and returns it.
>
>   This is with MAAS 2.3.0 (6434-gd354690-0ubuntu1~16.04.1).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1751907/+subscriptions