-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add upgrade option to the unattended script #862
Comments
UPDATE
|
Take into account Wazuh documentation. |
UpdateImprove mechanism to check if the upgrade is available, now for apt we use:
to check if we can upgrade to the version of the script. And for yum we use:
To make a test installation and check if the upgrade is possible. |
Update
We found that the yum command takes a bit too long so we have decided to use:
To get the packages that upgrade the installed one in a faster way.
|
UpdateTest changes and apply some improvements:
|
UpdateFix minor errors:
Fixed by removing revision from apt command:
instead of:
As we can see here the package upgraded Filebeat to 7.10.2, this was fixed by removing the first line in the command:
Add improvements:
TestingTest script in various systems:
|
UpdateWork on documentation:
|
@DFolchA
For this version, the argument must be I was able to check that for version 3.4.3 of yum the --show-duplicates argument was available |
I found some more messages in the Ubuntu Bionic and Ubuntu Jammy upgrade, despite these messages the upgrade was done:
|
Errors are also found in the confirmation request to replace files when updating indexer:
|
UpdateInvestigate errors: Comment 1Tested command:
in CentOS 7 and verified that it returns the same output as when using
Tested the same command in RHEL 8 and RHEL 9. Comment 2This is an error coming from the command Sources: Comment 3Currently investigating but it seems that it is more related to the |
UpdateDisable shard allocation before upgrading Wazuh indexer.
Start testing changes. |
UpdateWe added a second parameter to the commit: f68ffc1 Test changes
|
UpdateAfter discussing with the team we have decided to add a check before upgrading any component. Indexer
Server
Dashboard
This will be run before and after the upgrade, if the checks fail before upgrading we will stop the script with an error. To do this the script will need credentials that will be provided in a file with the same format as the one used for Indexer
Server
Dashboard
If credentials are incorrect we will stop the script with an error before updating. |
UpdateTest the latest changes with the upgrade check forcing errors. |
On Hold due to: https://github.com/wazuh/support/issues/4 |
UpdateAdd a function to get the Wazuh API password for a specific user. Continue testing. |
UpdateTest PoC to simulate a real environment for testing generating fake indexes in wazuh indexer |
UpdateMerge the latest changes and apply necessary modifications Test resulting wazuh-install script. |
UpdateWork on the testing environment:
The next step would be to get the index for a day of alerts from the demo environment and use it to simulate a real environment. |
UpdateContinue working on the test environment design: Copy index:
Set index to read-only:
Reindex changing the date:
This should result in a new index being created with a different timestamp. |
Hello team!
The aim of this issue is to add the option of upgrading the installation.
The script will check if any of the components of Wazuh are installed, if so, will check the version of then. If the version of the components is not the latest, will prompt a message to inform the user to run the script with the option
-u
, this will create a backup of the user data and upgrade the present components.Regards,
David
The text was updated successfully, but these errors were encountered: