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

[jira] Incorrect connector Dockerfile path #2535

Closed
gileri opened this issue Aug 27, 2024 · 2 comments
Closed

[jira] Incorrect connector Dockerfile path #2535

gileri opened this issue Aug 27, 2024 · 2 comments
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@gileri
Copy link
Member

gileri commented Aug 27, 2024

Description

Error during startup of Jira connector

Environment

  1. OS (where OpenCTI server runs):
  2. OpenCTI version: 6.2.15
  3. OpenCTI client:
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Run connector connector container

Expected Output

No error/crash

Actual Output

Connector crashes with a path not existing

Additional information

Looks like a typo here.

Screenshots (optional)

@gileri gileri added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Aug 27, 2024
@damians-filigran
Copy link
Contributor

Also here, presumably

@damians-filigran
Copy link
Contributor

Have edited lines 5 and 8 in a local build and tested, runs OK.

@SamuelHassine SamuelHassine added this to the Release 6.3.0 milestone Aug 27, 2024
@SamuelHassine SamuelHassine added solved use to identify issue that has been solved (must be linked to the solving PR) and removed needs triage use to identify issue needing triage from Filigran Product team labels Aug 27, 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 use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants