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

The integration test framework should test the DEB and RPM installations of the agent #4086

Closed
cmacknz opened this issue Jan 15, 2024 · 2 comments · Fixed by #4301
Closed
Assignees
Labels
Team:Elastic-Agent Label for the Agent team test-debt Label for missing test we need to implement

Comments

@cmacknz
Copy link
Member

cmacknz commented Jan 15, 2024

At minimum we need to ensure that these packages install and can be enrolled in Fleet. The RPM and DEB tests should run in their own test group to ensure they run in parallel with other installation types.

The Fleet log ingestion test could be used for this purpose. https://github.com/elastic/elastic-agent/blob/main/testing/integration/logs_ingestion_test.go#L40

We should also test that they can be upgraded, see #3784. This will require dedicated test as this is a new upgrade path, this part of the work could be split into a separate issue if needed.

@cmacknz cmacknz added the Team:Elastic-Agent Label for the Agent team label Jan 15, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@pierrehilbert pierrehilbert added the test-debt Label for missing test we need to implement label Feb 1, 2024
@pierrehilbert pierrehilbert linked a pull request Mar 7, 2024 that will close this issue
6 tasks
@pierrehilbert pierrehilbert reopened this Mar 13, 2024
@pierrehilbert
Copy link
Contributor

Reopening as only the DEB part has been done for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent Label for the Agent team test-debt Label for missing test we need to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants