Wrong error message on manager's disk space issues

[dariommr]

Wazuh	Elastic	Rev	Security
4.2.5	7.10.2	4xxx	ODFE

Browser
Any

Description Hello Team! The error messages that the Wazuh App is showing when there is no space left in the Wazuh Manager is wrong, showing the message:

There was an error: 3013 - Corrupted RBAC Database

And the RBAC database is ok, the real issue: no space left on the device.

Steps to reproduce The Wazuh app gives this error when trying to modify a Wazuh API Role through the UI:

Expected Result

1. More precise message regarding the real issue.

Actual Result

1. There was an error: 3013 - Corrupted RBAC Database

Thank you in advance!

[AlexRuiz7]

That's the message we get from the API as a result of a request.

This issue should be transferred to the @wazuh/framework team.

[davidjiglesias]

The Wazuh API is capturing an OperationalError raised by sqlalchemy when trying to access the RBAC database. There is no way to differentiate between a corrupted database or a no space left problem.

All we can do is improve the exception to something more generic, and improve the remediation.

[gdiazlo]

If we changed that message when the disk is full, any other exception could be thrown, depending on the operation we're doing on that instant. So it will not ensure a consistent error message.

I would let the error as it is. And I would add a troubleshooting guide about possible causes for errors out of context.