Manually executing check - no matching entities about sensu-go HOT 3 OPEN

Resources:

resources.zip

from sensu-go.

Verified that an edge condition where requesting an adhoc execution of a check with proxy_requests configured results in incorrect behavior scheduling. This should be a relatively simple patch to fix.

diff --git a/backend/schedulerd/executor.go b/backend/schedulerd/executor.go
index a6b30570e..0675b4b9c 100644
--- a/backend/schedulerd/executor.go
+++ b/backend/schedulerd/executor.go
@@ -198,7 +198,8 @@ func (a *AdhocRequestExecutor) listenQueue(ctx context.Context) {
                        continue
                }

-               if err = a.processCheck(ctx, &check); err != nil {
+               checkCtx := corev2.SetContextFromResource(ctx, &check)
+               if err = a.processCheck(checkCtx, &check); err != nil {
                        select {
                        case a.listenQueueErr <- err:
                        case <-ctx.Done():

As pointed out in the sensu-engineering slack thread, this use case isn't very obviously useful, and isn't something users are very likely to run into.

from sensu-go.

Steps of execution of issue:

1. Run sensuctl entity list and note the name of your agent entity (typically your hostname).
2. Edit the provided check.yaml at line 34 to add the entity name. The line should be something like - entity:agentname.
3. sensuctl create -f ./check.yaml
4. sensuctl create -f ./proxy.yaml
5. Wait a little bit and run
   sensuctl event info backend-entity prom-metrics
   and make sure an event is present.
6. Once the event is present run
   sensuctl check execute prom-metrics
   It should print Issued.
7. Verify the logs in backend logs , the "no matching entity " error must not be seen inspite the matched entity should be reflected.

from sensu-go.