Comment 7 for bug 1936218

Having followed along with Jiri's train of thought I'm inclined to agree that this points to the validation itself.

The error message is slightly misleading; the initial part of the error is a warning that the validations dir does not exist is actually informational rather than worrying (and perhaps we should rethink this) but this is not the actual key part of the message.

The key part is the final bit: "No validation has been run" - this is caused because conditions in the validation are not such that it can run.

In particular it looks like a hostname doesn't get found in the logs perhaps due to an inventory issue, so nothing was available to run.