Skip to content
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

Agent deployment URLs don't work for some versions or architectures #2652

Closed
jctello opened this issue Nov 23, 2020 · 1 comment · Fixed by #2677
Closed

Agent deployment URLs don't work for some versions or architectures #2652

jctello opened this issue Nov 23, 2020 · 1 comment · Fixed by #2677
Assignees
Labels
request/operational Operational requests type/bug Bug issue

Comments

@jctello
Copy link
Contributor

jctello commented Nov 23, 2020

Wazuh Elastic Rev
4.0.1 7.9.1 4010

Description
URLs provided in the agent deployment don't fully cover the possible versions and architectures that Wazuh supports. Notably CentOS/RHEL5 use a different URL than the one provided as do all Linux architectures other than x86_64

Steps to reproduce

  1. Go to the Agents section
  2. Click on Deploy New Agent
  3. Select RedHat / CentOS
  4. Attempt to use on RHEL5, a 32-bit, aarch64 or armhf computer.

Screenshots
image

Additional context
For agents with CentOS/RHEL5 the valid URLs are:

The package provided for the CentOS/RHEL 6 and above would not work for the following architectures:

For Debian/Ubuntu and similar:

@Desvelao
Copy link
Member

Changes

  • Added OS version and OS architecture steps.
  • Modified the package URL which depends on OS, OS version, and OS architecture selected
  • Modified the OS selection button by a button group
  • Improved the logic to generate the install agent command
  • Added a message in the install agent step when some OS options are not selected
  • Hid the start agent step when there are OS options not selected
  • Improved some texts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request/operational Operational requests type/bug Bug issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants