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

add integration test for install via RPM on SLES #4461

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

leehinman
Copy link
Contributor

What does this PR do?

Adds Integration test that uses SLES 15 AMD to test fleet managed elastic-agent installed via RPM.

Only AMD was added because at the moment ogc doesn't support SLES ARM on GCP. Also looked at implementing #4301 (comment) This was skipped because adding a slice of strings (for supported package formats) to the OS struct broke comparison of OS structs. I think this is still worth doing, just in a separate PR because it is likely to change a fair number of things.

Why is it important?

Need to test our RPM builds

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Author's Checklist

  • [ ]

How to test this PR locally

mage integration:single TestRpmLogIngestFleetManaged

Related issues

Use cases

Screenshots

Logs

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@leehinman leehinman requested a review from a team as a code owner March 21, 2024 20:25
@leehinman leehinman requested review from AndersonQ and pchila March 21, 2024 20:25
Copy link
Contributor

mergify bot commented Mar 21, 2024

This pull request does not have a backport label. Could you fix it @leehinman? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

Copy link

Quality Gate passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No Coverage information No data about Coverage
0.0% 0.0% Duplication on New Code

See analysis details on SonarQube

@leehinman leehinman changed the title add SLES as supported platform add integration test for install via RPM on SLES Mar 22, 2024
@pierrehilbert pierrehilbert added the Team:Elastic-Agent Label for the Agent team label Mar 22, 2024
@elasticmachine
Copy link
Contributor

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

@pierrehilbert pierrehilbert requested a review from rdner March 22, 2024 09:09
@@ -125,7 +125,75 @@ func TestDebLogIngestFleetManaged(t *testing.T) {
// name. This policy does not contain any integration.
t.Log("Enrolling agent in Fleet with a test policy")
createPolicyReq := kibana.AgentPolicy{
Name: fmt.Sprintf("test-policy-enroll-%d", time.Now().Unix()),
Name: fmt.Sprintf("test-policy-enroll-%s", uuid.New().String()),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!
Related to #4421
I guess this test was not there when I fixed it 🙂

@leehinman leehinman merged commit 1921306 into elastic:main Mar 22, 2024
10 checks passed
rdner added a commit that referenced this pull request Mar 23, 2024
rdner added a commit that referenced this pull request Mar 25, 2024
@leehinman leehinman mentioned this pull request Mar 28, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants