Closed Selutario closed 1 week ago
I tried to reproduce the error using a multi-node wazuh-docker environment with the tag 4.8.0-rc1
, but the configuration was updated successfully the 10 times I tried. I tested saving both changed and unchanged configuration files.
The issue was likely caused by the file ossec.conf
not having proper permissions and ownership set.
We would need further information about the environment or steps to reproduce to continue with the investigation.
Made the same tests in the Demo environment but couldn't reproduce the failure. I also analyzed the API logs from previous days but no internal errors were found.
A pull request has been opened to include the exception message in the error thrown by the API to aid the debugging in the future.
The provided tests are clear, compelling, and demonstrate the correct operation when editing the ossec.conf
from the UI.
As mentioned in the investigation, the issue likely stemmed from the ossec.conf
file not having the proper permissions and ownership set.
I agree, LGTM!
GJ. Although it could not be reproduced, we will obtain more information in the future in case it happens again after this issue's PR.
Description
We have been reported that, in 4.8.0-rc1, an error like the following sometimes appears when trying to edit the
ossec.conf
through the UI:Checks
The following elements have been updated or reviewed (should also be checked if no modification is required):
api/test/integration/mapping/_test_mapping.py
).