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

Error message of Caldera executor not responding when there is no Caldera config #1550

Closed
johanah29 opened this issue Sep 27, 2024 · 0 comments · Fixed by #1559
Closed

Error message of Caldera executor not responding when there is no Caldera config #1550

johanah29 opened this issue Sep 27, 2024 · 0 comments · Fixed by #1559
Assignees
Labels
bug use for describing something not working as expected solved The issue has been solved
Milestone

Comments

@johanah29
Copy link
Member

Description

There is a message saying Caldera executor is not responding, even when there is no configuration for it in the docker-compose file.
image

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Delete the Caldera config from the docker-compose file
  2. Delete/stop the Caldera container
  3. Run the openbas backend
@johanah29 johanah29 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Sep 27, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Sep 27, 2024
@MarineLeM MarineLeM self-assigned this Sep 27, 2024
MarineLeM added a commit that referenced this issue Sep 30, 2024
Signed-off-by: Marine LM <marine.lemezo@filigran.io>
@MarineLeM MarineLeM added the solved The issue has been solved label Sep 30, 2024
@RomuDeuxfois RomuDeuxfois added this to the Release 1.7.0 milestone Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved The issue has been solved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants