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

OpenBAS server user interface does not show agent version #2247

Closed
neutneutneut opened this issue Jan 20, 2025 · 2 comments · Fixed by #2258 or #2261
Closed

OpenBAS server user interface does not show agent version #2247

neutneutneut opened this issue Jan 20, 2025 · 2 comments · Fixed by #2258 or #2261
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature solved The issue has been solved

Comments

@neutneutneut
Copy link

neutneutneut commented Jan 20, 2025

Description

When updating OpenBAS server, previously installed agents no longer function. The agents user interface still shows the agents as 'active' however if you go to the log files on the system that the agent is installed, there is a 'fail getting jobs' error. An improvement would be to update the OpenBAS server UI to show the agent version vs server version to show if agents are compatible / correctly configured.

Environment

  1. OS (where OpenBAS server runs): Docker
  2. OpenBAS version: 1.11.1
  3. OpenBAS client: Native
  4. Other environment details: N/A

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Install OpenBAS version 1.10.1
  2. Install agents for 1.10.1
  3. Update server to 1.11.1
  4. Agents from step 2 no longer function, but appear in the UI as 'active'

Expected Output

Non-compatible agents should show an error message.

Actual Output

Non-compatible agents appear as 'active' but they do not function

Additional information

N/A

Screenshots (optional)

N/A

@neutneutneut neutneutneut added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 20, 2025
@jborozco jborozco added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Jan 20, 2025
@jborozco jborozco added this to the Bugs backlog milestone Jan 20, 2025
@jborozco jborozco added the regression Label to identify the bug as a regression of previously working feature label Jan 20, 2025
@jborozco
Copy link

This bug is critical, it is blocking all use of the OBAS agent.

@guillaumejparis
Copy link
Member

We fixed the "fail getting jobs" in this PR : #2258
I will open a new issue to show the agent version in the interface

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 critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature solved The issue has been solved
Projects
None yet
4 participants