Wazuh remote upgrade for RHEL5 agent

[Veera]

Hi,

We are encountering the following error when attempting a remote upgrade for a RHEL 5 agent:

No upgrade task was created (1819) - The WPK for this platform is not available

Based on this, it appears that RHEL 5 agents cannot be upgraded through Wazuh remote upgrade because no WPK package is available for that platform. If this understanding is correct, these systems would need to be excluded from the standard upgrade workflow and treated as legacy agents.

Could you please confirm whether the same approach should also be applied to other legacy platforms such as CentOS 5, Ubuntu 14/16, and SLES 11—that is, exclude them from the regular upgrade process and retain them on the highest Wazuh agent version that can be installed initially and supported on those platforms?

Current versions:

• Wazuh server version: 4.14.4-1
• RHEL 5 agent version: 4.14.2-1

Please confirm if this is the recommended approach for handling these legacy operating systems.

[Nikhil Gurjar]

Hi Veera,

I'm working on your request and will provide an update shortly with my findings and the next steps.

Best regards,
Nikhil

[Veera]

Hi Nikhil,

Thanks , Waiting for your update.

Do we need to add-on/additional settings on the master/wazuh-server side to support for the wpk support for el5 or euivalent packages?

[Nikhil Gurjar]

Hi Veera,

Thank you for your patience while I investigated this issue.

I reviewed the reported behaviour on the RHEL 5 agent and performed additional validation in our lab environment to determine whether the issue was related to a missing WPK package or a limitation in the remote upgrade mechanism itself.

Environment Details

• Wazuh manager version: 4.14.5
• Customer agent version: 4.12.0
• Lab setup:
  • Red Hat Enterprise Linux Server release 5.1 (Tikanga)
  • Kernel: 2.6.18-53.el5
  • Architecture: x86_64

I first deployed a RHEL 5.1 system in the lab and successfully installed the Wazuh agent. The agent registered with the manager and remained active without issues. The manager correctly identified the agent as:

Operating system: Linux | localhost.localdomain | 2.6.18-53.el5 | x86_64
Client version: Wazuh v4.12.0
Status: Active

I then carried out the following tests.

Test A – Official WPK Package:  I attempted a remote upgrade using Remote upgrade and  the official WPK package(reference document: https://documentation.wazuh.com/current/user-manual/agent/agent-management/remote-upgrading/wpk-files/wpk-list.html):

/var/ossec/bin/agent_upgrade -a <agent_id> -f wazuh_agent_v4.14.5_linux_x86_64.rpm.wpk

Both are returning the same error: Error 1819 - The WPK for this platform is not available


Test B – Custom EL5 WPK Package

Next, I followed the official Wazuh documentation to rule out any packaging limitations and generated a custom WPK using the EL5-specific RPM: wazuh-agent-4.14.5-1.el5.x86_64.rpm

References documents:

• https://documentation.wazuh.com/current/installation-guide/packages-list.html#wazuh-agent
• https://documentation.wazuh.com/current/user-manual/agent/agent-management/remote-upgrading/wpk-files/wpk-list.html
• https://documentation.wazuh.com/current/user-manual/agent/agent-management/remote-upgrading/wpk-files/create-custom-wpk.html

After deploying the custom WPK, the result remained unchanged: Error 1819 - The WPK for this platform is not available

In addition, the manager's logs showed:

wazuh-modulesd:agent-upgrade: WARNING: (8160): There are no valid agents to upgrade.

Conclusion

From my testing, I observed the following:

• The RHEL 5 agent installs and communicates with the Wazuh manager without issues.
• Both official and custom WPK-based upgrade attempts fail with Error 1819.
• The manager does not create an upgrade task and indicates that there are no valid agents for the upgrade.

Based on this behaviour, the issue does not appear to be caused simply by the absence of a WPK package. Instead, the RHEL 5 agent is not being accepted as a valid target for the remote upgrade workflow.

Recommendation

For legacy operating systems such as RHEL 5, it is recommended to handle upgrades manually using the appropriate agent package for the platform(reference documents: https://documentation.wazuh.com/current/upgrade-guide/wazuh-agent/linux.html, https://documentation.wazuh.com/current/deployment-options/wazuh-from-sources/wazuh-agent/index.html ) as these systems are outside the modern support scope and may not fully support the remote upgrade mechanism.

The same approach may be required for other end-of-life systems such as CentOS 5, Ubuntu 14/16, and SLES 11, depending on whether they exhibit similar behaviour with Error 1819.

Hope this information is helpful for you and clarifies your concern. Please let us know if you have any other queries & questions here. 

Best regards,
Nikhil