NahuFigueroa97
commented
1 month ago Initial Deployment :red_circle:
Vagrant Amazon Linux 2023 x86_64
Vagrant.configure("2") do |config|
config.vm.box = "gbailey/amzn2"
config.vm.hostname = "E2E-SERVER"
config.vm.define "E2E-SERVER" do |e2e|
end
config.vm.network "public_network"
config.vm.synced_folder ".", "/vagrant", disabled: true
config.vm.provider "virtualbox" do |vm|
vm.name = "E2E-SERVER"
vm.check_guest_additions = false
vm.memory = 8192
vm.cpus = 8
end
config.ssh.forward_agent = true
end
Vagrant Debian 11 x86_64
Vagrant.configure("2") do |config|
config.vm.box = "generic/debian11"
end
Note :orange_circle:
When trying to run the installer I saw this result:
[root@E2E-SERVER vagrant]# curl -sO https://packages.wazuh.com/4.9/wazuh-install.sh && sudo bash ./wazuh-install.sh -a
./wazuh-install.sh: line 1: syntax error near unexpected element `newline'
./wazuh-install.sh: line 1: `<?xml version="1.0" encoding="UTF-8"?>'Even if you try to upgrade from 4.8 to 4.9 a problem occurs
[root@E2E-SERVER-WORKER vagrant]# curl -s https://packages.wazuh.com/4.x/filebeat/wazuh-filebeat-0.4.tar.gz | sudo tar -xvz -C /usr/share/filebeat/module
wazuh/
wazuh/_meta/
wazuh/_meta/docs.asciidoc
wazuh/_meta/fields.yml
wazuh/_meta/config.yml
wazuh/alerts/
wazuh/alerts/config/
wazuh/alerts/config/alerts.yml
wazuh/alerts/manifest.yml
wazuh/alerts/ingest/
wazuh/alerts/ingest/pipeline.json
wazuh/module.yml
wazuh/archives/
wazuh/archives/config/
wazuh/archives/config/archives.yml
wazuh/archives/manifest.yml
wazuh/archives/ingest/
wazuh/archives/ingest/pipeline.json
[root@E2E-SERVER-WORKER vagrant]# curl -so /etc/filebeat/wazuh-template.json https://raw.githubusercontent.com/wazuh/wazuh/v4.9.0/extensions/elasticsearch/7.x/wazuh-template.json
[root@E2E-SERVER-WORKER vagrant]# chmod go+r /etc/filebeat/wazuh-template.json
[root@E2E-SERVER-WORKER vagrant]# systemctl daemon-reload
[root@E2E-SERVER-WORKER vagrant]# systemctl enable filebeat
[root@E2E-SERVER-WORKER vagrant]# systemctl start filebeat
[root@E2E-SERVER-WORKER vagrant]# filebeat setup --pipelines
Loaded Ingest pipelines
[root@E2E-SERVER-WORKER vagrant]# filebeat setup --index-management -E output.logstash.enabled=false
ILM policy and write alias loading not enabled.
Exiting: error loading template: could not unmarshal json template: invalid character ':' after top-level valueThe other tests were run with 4.8 to see that there were no inconsistencies
rauldpm
pro-akim
juliamagan
End-to-End (E2E) Testing Guideline
Release testingobjective andUrgentpriority. Communicate these to the team and QA via the c-release Slack channel.For the conclusions and the issue testing and updates, use the following legend:
Status legend
Issue delivery and completion
review_assigneefield in the project. The reviewer must then review the test steps and results. Ensure that all iteration cycles are completed by Jul 25, 2024 date (issue must be inPending final reviewstatus) and notify the QA team via Slack using the c-release channel.Deployment requirements
Test description
1. Initial Deployment:
2. Validation of Initial Deployment:
3. Upgrade of Central Components:
4. Post-Upgrade Validation:
5. Reporting:
Expected Results
Known issues
There are no known issues.
Conclusions
Summarize the errors detected (Known Issues included). Illustrate using the table below. REMOVE CURRENT EXAMPLES:
Feedback
We value your feedback. Please provide insights on your testing experience.
Reviewers validation
The criteria for completing this task is based on the validation of the conclusions and the test results by all reviewers.
All the checkboxes below must be marked in order to close this issue.