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

Various failures when working with unsupported agents #2836

Closed
jctello opened this issue Jan 25, 2021 · 5 comments · Fixed by #2959
Closed

Various failures when working with unsupported agents #2836

jctello opened this issue Jan 25, 2021 · 5 comments · Fixed by #2959
Assignees
Labels
request/operational Operational requests type/bug Bug issue

Comments

@jctello
Copy link
Contributor

jctello commented Jan 25, 2021

Wazuh Elastic Rev
4.0.3 7.9.1 4013
4.0.4 7.10.0 4016

Description
If an agent that is not officially supported, but compiled from sources, is pinned the app will fail in various places including:

  • Clicking on the Wazuh drop-down menu (makes the top bar disappear)
  • Clicking on More in the agent's summary page (makes the content blank)
  • Selecting Inventory data provides an almost blank page (but generating a report does provide information)

Steps to reproduce

Menu disappearance

  1. Register and connect an OpenBSD agent
  2. Select the Security Configuration Assessment dashboard (easy way to pin an agent)
  3. Select the OpenBSD
  4. Click on the Wazuh drop-down menu and it disappears

openBSD-menu-disappearance
Console output can be found here:
openBSD-menu-disappearance.log

Agent summary page disappearance

  1. Select the openBSD agent from the Agents section
  2. Select More menu (that would give quick access to the various dashboards) and see the page go blank
    openBSD-modules-directory
    Corresponding console logs are here:
    openBSD-Modules-Load.log
    And they show: Uncaught TypeError: UnsupportedComponents[platform] is undefined

Blank inventory data page

  1. Select the openBSD agent from the Agents section

  2. Select Inventory data (view almost blank page)
    image

  3. Select Generate report to see some data is available.
    image

Additional context
Although this operating system is not officially supported, the user interface should be able to handle errors gracefully and indicate the limitations.

@jctello jctello added type/bug Bug issue request/operational Operational requests labels Jan 25, 2021
@Desvelao Desvelao self-assigned this Feb 1, 2021
@frankeros frankeros added this to the Sprint 124 - WUI milestone Feb 1, 2021
@Desvelao
Copy link
Member

Desvelao commented Feb 1, 2021

I checked with an OpenBSD VM and this problem is happening.

The problem is caused due to other OS types differents of Linux (includes Linux in his os.uname, Darwin, Windows or SunOs are not managed correctly.

@Desvelao
Copy link
Member

Desvelao commented Feb 1, 2021

Changes

  • Moved OS types to constants
  • Refactor fo UnsupportedComponentes object
  • Restructuring the logic to show the available modules for the selected agent in the main menu

@Desvelao
Copy link
Member

Desvelao commented Feb 11, 2021

Changes

  • Fixed main menu
  • Fixed More menu in the agent view
  • Added a prompt to Modules to show when the module is not supported by the selected agent

Screenshots

image

@Desvelao
Copy link
Member

TODO

  • Fix main menu
  • Fix More menu in the agent view
  • Added a prompt to the de module view to show when the module is not supported by the selected agent

@Desvelao
Copy link
Member

I checked the Inventory data view for the agent, and some information is displayed
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request/operational Operational requests type/bug Bug issue
Projects
None yet
3 participants