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

Shown Wazuh API version is wrong or empty after upgrade #440

Closed
jnasselle opened this issue Dec 11, 2024 · 2 comments · Fixed by wazuh/wazuh-dashboard-plugins#7203
Closed
Assignees
Labels
level/task Task issue type/bug Bug issue

Comments

@jnasselle
Copy link
Member

Describe the bug

During wazuh/wazuh#27183, it was found that Wazuh API version shown is not the current one after upgrading from v4.9.2 to v4.10.0-rc1

image

After cleaning the cache, the error is worse

image

To Reproduce

See wazuh/wazuh#27183

Expected behavior

Wazuh API is v4.10.0

image

OpenSearch Version
Please list the version of OpenSearch being used.

Dashboards Version
Please list the version of OpenSearch Dashboards being used.

Plugins

Please list all plugins currently enabled.

Screenshots

If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • OS: [e.g. iOS]
  • Browser and version [e.g. 22]

Additional context

Add any other context about the problem here.

@Tostti
Copy link
Member

Tostti commented Dec 12, 2024

The problem was reproducible.

before
after

@guidomodarelli guidomodarelli self-assigned this Dec 13, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 4.10.0 Dec 13, 2024
@guidomodarelli
Copy link

I have been reviewing where the data in the Version column of the table comes from, and I found that the information originates from a request made to the server (GET /manager/version/check?force_query=${forceQuery}), which in turn makes a request to the CTI. In this case, since v4.10.0-rc1 is not yet in production, CTI is unaware of the existence of this version and does not return the expected information, including the current API details. To address this issue, considering that a failure in the request to CTI occurs, I plan to resolve this directly by making a direct request to the server at / to inquire about the version.

@wazuhci wazuhci moved this from In progress to Pending review in Release 4.10.0 Dec 16, 2024
@wazuhci wazuhci moved this from Pending review to In review in Release 4.10.0 Dec 17, 2024
@wazuhci wazuhci moved this from In review to Done in Release 4.10.0 Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/bug Bug issue
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants