Rollover + alias E2E testing #53
Assignees
Labels
Comments
Test resultsconfig.yml
nodes:
# Wazuh indexer nodes
indexer:
- name: node-1
ip: "192.168.56.10"
- name: node-2
ip: "192.168.56.11"🟢 03 - Cluster installation (assistant)Vagrantfile
Vagrant.configure("2") do |config|
config.vm.provider "virtualbox" do |vb|
vb.memory = "4096"
vb.cpus = "4"
end
config.vm.define "node1" do |node1|
node1.vm.box = "generic/rhel7"
node1.vm.synced_folder ".", "/vagrant"
node1.vm.network "private_network", ip: "192.168.56.10"
node1.vm.provision "shell", inline: <<-SHELL
# Disable firewall
systemctl stop firewalld
systemctl disable firewalld
SHELL
end
config.vm.define "node2" do |node2|
node2.vm.box = "generic/rhel7"
node2.vm.synced_folder ".", "/vagrant"
node2.vm.network "private_network", ip: "192.168.56.11"
node2.vm.provision "shell", inline: <<-SHELL
# Disable firewall
systemctl stop firewalld
systemctl disable firewalld
SHELL
end
end
🟢 04 - Cluster installation (step-by-step)I've used the SSL certificates generated by the assistant.
🟢 06 - Cluster upgrade without existing rollover policy
🔴 08 - Cluster upgrade with existing rollover policy
|
gdiazlo
added
request/operational
6 tasks
|
Issues created
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test description
In order to test wazuh/wazuh#18999, these manual tests must pass:
*AIO: all-in-one
All methods must verify that:
Using the documentation for each deployed method, the installation is successful.
Details
The installation completes without errors.
The ISM policy
rollover_policyis created*.Details
Use
GET _plugins/_ism/policies/rollover_policyto verify the policy exists.The
wazuh-alertsandwazuh-archivesindex templates are created.Details
Use
GET _template/wazuh*rolloverto verify the templates exist.The
wazuh-alertsandwazuh-archivesaliases are created.Details
Use
GET _alias/wazuh-a*to verify the aliases exist.The initial indices are created and being managed by the
rollover_policypolicy*.Details
For tests number 07 and 08, see the special checks below.
Use
GET _plugins/_ism/explain/wazuh-*-000001to check if the indices are being managed by the policy.The
manage_ismaction group and role are created.Details
Use
GET _plugins/_security/api/roles/manage_ismto check if the action group and role exists.{ "manage_ism": { "reserved": true, "hidden": false, "cluster_permissions": [ "manage_ism" ], "index_permissions": [], "tenant_permissions": [], "static": false } }For tests number 07 and 08, these additional checks must be performed:
The policy with the highest priority takes precedence to manage the indices.
Details
Steps:
Test report procedure
All test results must have one of the following statuses:
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause.
An extended report of the test results must be attached as a ZIP or TXT file. Please attach any documents, screenshots, or tables to the issue update with the results. This report can be used by the auditors to dig deeper into any possible failures and details.
Conclusions
All tests have been executed and the results can be found here.
All tests have passed and the fails have been reported or justified. Therefore, I conclude that this issue is finished and OK for this release candidate.
Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
The text was updated successfully, but these errors were encountered: