Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sensor with Kafka EventBus does not trigger if depend on 2 events #3063

Closed
ammarar opened this issue Mar 12, 2024 · 1 comment
Closed

Sensor with Kafka EventBus does not trigger if depend on 2 events #3063

ammarar opened this issue Mar 12, 2024 · 1 comment
Labels
bug Something isn't working stale

Comments

@ammarar
Copy link

ammarar commented Mar 12, 2024

Describe the bug
A sensor that uses Kafka as the Event bus would not trigger an Argo Workflow if it depends on 2 events.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Kafka cluster

  2. Create a Kafka EventBus, HTTP EventSource, and a Sensor by running kubectl apply -f on the attached file
    events-bug.zip.

  3. Trigger metaflow-event with metaflow.FlowB2.end

{
    "name": "metaflow.FlowB2.end",
    "payload": {
      "name": "metaflow.FlowB2.end",
      "auto-generated-by-metaflow": "True"
    }
}
  1. Trigger metaflow-event with metaflow.FlowC2.end
{
    "name": "metaflow.FlowC2.end",
    "payload": {
      "name": "metaflow.FlowC2.end",
      "auto-generated-by-metaflow": "True"
    }
}

Expected behavior
The Argo Workflow should submit.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • Kubernetes: v1.27.9
  • Argo: v3.5.1
  • Argo Events: v1.9.0

Additional context
This works correctly on JetStream without any issue.


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@ammarar ammarar added the bug Something isn't working label Mar 12, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has not had
any activity in the last 60 days. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label May 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant