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

Fixes on editing cluster configuration #564

Merged
merged 3 commits into from
Feb 18, 2019
Merged

Fixes on editing cluster configuration #564

merged 3 commits into from
Feb 18, 2019

Conversation

adri9valle
Copy link
Contributor

Hi team,

Testing this issue #551, if set in the ossec.conf:

<cluster>
...
<disabled>yes</disabled>
...
</cluster>

On the master node when the cluster status is running yet, if the configuration is saved and click on the restart button from the confirm dialog, is launched an error because the APP tries to check the node configuration with this API call: /cluster/{node_master_name}/configuration/validation this are incorrect because in the ossec.conf the cluster is disabled, then the API won't answer to this call launching an error. This was fixed checking if the cluster is disabled the check is launched against the manager.

Also, have been removed the abstract state of management fixing that sometimes the Edit configuration button disappear.

Regards,

@adri9valle adri9valle self-assigned this Feb 18, 2019
@adri9valle adri9valle added this to Needs review in Wazuh 3.9.0 - 7.2.x via automation Feb 18, 2019
@jesusgn90 jesusgn90 merged commit ee6b713 into 3.9 Feb 18, 2019
Wazuh 3.9.0 - 7.2.x automation moved this from Needs review to Done Feb 18, 2019
@jesusgn90 jesusgn90 deleted the testing-edit-conf branch February 18, 2019 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants