https://outerbounds.com/ logo
Join Slack
Powered by
Hello team, I'm having trouble triggering a flow ...
# ask-metaflow
a
Hello team, I'm having trouble triggering a flow from another flow through Argo Events triggering. I am using an ingress for the eventsource webhook. Any help would be greatly appreciated.
✅ 1
s
What’s the issue that you are running into?
a
Just don't trigger when the flow is complete. Not sure where to check for any error. Config looks like this:
Copy code
"METAFLOW_ARGO_EVENTS_EVENT": "metaflow-event",
    "METAFLOW_ARGO_EVENTS_EVENT_BUS": "jetstream-eb",
    "METAFLOW_ARGO_EVENTS_EVENT_SOURCE": "argo-events-webhook",
    "METAFLOW_ARGO_EVENTS_SERVICE_ACCOUNT": "operate-workflow-sa",
    "METAFLOW_ARGO_EVENTS_WEBHOOK_URL": "<https://argo-events-webhook>.<HOST_NAME>.com",
s
Do you see the event in the event bus?
Also do the sensor logs show that the sensor was reading the event?
a
Yeah -
Copy code
{
  "level": "info",
  "ts": 1738805390.1061919,
  "logger": "argo-events.eventsource",
  "caller": "webhook/start.go:96",
  "msg": "a request received, processing it...",
  "eventSourceName": "argo-events-webhook",
  "eventSourceType": "webhook",
  "eventName": "metaflow-event",
  "endpoint": "/",
  "port": "12000",
  "http-method": "POST"
}
Actually, It might be RBAC related w/ regards to the argo events service account. Let me check. I ran into that issue earlier when running argo workflows regularly. Was missing 
workflowtaskresults
Hmm no RBAC looks correct I think
s
Yeah the first thing would be to verify that the event is making its way into the jetstream
a
Maybe this is the issue? https://outerbounds-community.slack.com/archives/C02116BBNTU/p1719996645689499?thread_ts=1719858152.600319&amp;cid=C02116BBNTU The ingress, eventsource, and eventbus are in the 
argo-events
namespace. While everything else is in a different namespace
Our pattern is a little unorthodox in that we isolate the K8s cluster resources into project namespaces. So Argo Workflow jobs run in these namespaces depending on the user's team. But we deployed all the argo events components into the 
argo-events
namespace, and we hoped would trigger flows from any of the project namespaces
Okay it's as I suspected. It's looking for the eventbus in the 
cagepart
namespace (the namespace in the metaflowconfig), but the eventbus is in the 
argo-events
namespace
Copy code
{
  "level": "error",
  "ts": 1738813226.778638,
  "logger": "argo-events.eventbus-controller",
  "caller": "sensor/controller.go:72",
  "msg": "reconcile error",
  "namespace": "cagepart",
  "sensor": "demoforeachflow",
  "error": "eventbus jetstream-eb not found",
  "stacktrace": "<http://github.com/argoproj/argo-events/pkg/reconciler/sensor.(*reconciler).Reconcile|github.com/argoproj/argo-events/pkg/reconciler/sensor.(*reconciler).Reconcile>\n\t/home/runner/work/argo-events/argo-events/pkg/reconciler/sensor/controller.go:72\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:227"
}
Open in Slack
PreviousNext
Powered by