And thanks for the shell tip! (found it a bit earlier, and was able to git it working \o/):
I'm crossing query.latest_query_rev with query_revision, that shrinks the number quite considerably:
I did a preliminary check on all quarry queries, and found 42 that seem to use cross DB (I have to check a bit more the code to see if I'm missing any).
Sun, Nov 22
Fri, Nov 20
Wed, Nov 18
Mon, Nov 16
Isn't it better to put this one as 'depends on'? That way when we check for issues with the host cloudbackup2002 we will find an open task, that still will depend on the actual switch task, and that too allows us to track if the host is up again correctly after the switch is up no?
Tue, Nov 10
As a workaround if needed and worst case scenario, you can try running bare/non-hardware backed qemu (really slow though :S)
Fri, Nov 6
A different fix would be to have the k8s backend send a message to the front proxy on process start telling the front proxy to clear any and all registered routes for the tool. This feels like a more robust solution.
Thu, Nov 5
Here is a new one:
Wed, Nov 4
Tue, Nov 3
Note to myself, puppetdb02 hiera has puppetdb02 as master as overwrite, check and