You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the WPKs are the Agents compiled. Thus, when we upgrade an Agent we "replace the files" of the Agents.
For that reason, despite the Agent is properly upgraded and it shows the correct version, the package of the Agent is still in the old version. Thus, the management of that package from repositories changes completely.
For example:
I have the following Agent in version 3.9:
DIRECTORY="/var/ossec"
NAME="Wazuh"
VERSION="v3.9.0"
REVISION="3918"
DATE="Wed May 22 08:48:05 UTC 2019"
TYPE="agent"
But the package is in version 3.8.1:
Resolving Dependencies
--> Running transaction check
---> Package wazuh-agent.x86_64 0:3.8.1-1 will be updated
---> Package wazuh-agent.x86_64 0:3.9.1-1 will be an update
Solution:
The WPKs should contain a package of the Agent (deb, rpm, p5p, etc...)
Regards,
Miguel Casares
The text was updated successfully, but these errors were encountered:
Hello team,
Right now, the WPKs are the Agents compiled. Thus, when we upgrade an Agent we "replace the files" of the Agents.
For that reason, despite the Agent is properly upgraded and it shows the correct version, the package of the Agent is still in the old version. Thus, the management of that package from repositories changes completely.
For example:
I have the following Agent in version 3.9:
But the package is in version 3.8.1:
Solution:
The WPKs should contain a package of the Agent (deb, rpm, p5p, etc...)
Regards,
Miguel Casares
The text was updated successfully, but these errors were encountered: