Comment 1 for bug 1628504

Yeah, that's a common issue with some scheduler filters where the precedence is not really clarified between an image metadata and a flavor extraspec. We have a couple of filters that very poorly mention that.

From a pure process perspective, I tho think that the proposed fix would require some behavioural change (about we now agree and what we now refuse) that would require some upgrade note mentioning the new UX. For that specific reason, I actually wonder whether it shouldn't be better to write a blueprint for that and track it spec-less (if agreed by consensus).

For the moment, tracking the bug as Low, but I'm very tempted into turning it into Wishlist.