-
Notifications
You must be signed in to change notification settings - Fork 32
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
WPK Update on ALAS 2022 #3415
Comments
@Deblintrake09 finally the issue was related to upgrading any agent with |
Review data
Testing environment
Tested packages
Conclusion 🟡Everything works as expected after the fix however there was an Issue found with the steps taken for the wpk package generation and the agent upgrade through CLI:
Status
|
Testing resultsWork on unfixed Branch 4.3.9-1Build WPK and upgrade agent 🔴In Manager
In Agent
Work on Fixed BranchBuild WPK and upgrade agent 🟡**In the manager ** . Install Manager
**In Agent **
In the agent
In Manager
In Agent
Note: The error present in the Issue is not present but the agent takes too long to update and the manager timeouts, while the agent continues to receive information, it then receives the stop command, to update, but does not update or restart. |
Update 2022/10/17
|
Update 2022/10/18
|
Update 2022/10/19
|
Testing resultsBuild WPK and upgrade agent 🔴
Work on Fixed BranchBuild WPK and upgrade agent through CLI - Service Active 🟡
Build WPK and upgrade agent through CLI - Service Inactive 🟡
Build WPK and upgrade agent through API 🟢
|
Closing conclusion 👍🏼
After talking with the team, the testing has been approved taking into account the following considerations proposed in the QA review: (1) The steps indicated in the documentation for WPK generation are not correct. 🔵 This is a known bug and it will be fixed in this PR wazuh/wazuh-documentation#5701 |
Description
This development fixes WPK upgrade process for ALAS2022 agents. Testing needs to be done in order to verify it works properly.
Proposed checks
Steps to reproduce
Expected results
Agent upgrades to 4.4.0 and works properly.
The text was updated successfully, but these errors were encountered: