https://github.com/theforeman/foreman/commit/3f8e6c33624f33acd65b371bf67549606397286e this looks like the culprit - investigating...

Despite the fact that it changed previous behaviour, isn't this actually expected?

Marek Hulán wrote:

Despite the fact that it changed previous behaviour, isn't this actually expected?

I can't follow. Why should this be expected behavior? Searching for hosts by two or more facts seems a reasonable requirement for me. For example I might want to search for hosts that have jruby and mysql installed. This is an arbitrary example, but - unfortunately - currently broken.

Ah sorry, I misunderstood what you try to search for, I thought you were trying to search facts, not hosts. Ok, sounds as a valid bug.

I believe this is happening when having a two joins on the same table, this was fixed in the past on scoped search at https://github.com/wvanbergen/scoped_search/commit/a7666e4b0a44cf1c066848cc8ab2f57301a7a218.

the solution should be to add aliases to table join, per condition set (name / value), however from a quick glance I'm not sure how to resolve it within the current implementation of external method.

AFAIR forcing a join should trigger the join aliasing code in scoped search.

I think the right way to solve it is probably via a patch to scoped_search, as there is no way to control the join statement from within the ext_method.