Skip to content

[Fleet] Backport retry/logging changes#241144

Closed
Supplementing wants to merge 2 commits intoelastic:9.0from
Supplementing:retry-fix-for-tests
Closed

[Fleet] Backport retry/logging changes#241144
Supplementing wants to merge 2 commits intoelastic:9.0from
Supplementing:retry-fix-for-tests

Conversation

@Supplementing
Copy link
Contributor

@Supplementing Supplementing commented Oct 29, 2025 •
edited
Loading

Summary

This is a manual backport PR for adding the retry and error logging changes into 9.0 to stop smoke test failures.

We are aware there are no planned patches, but the changes made in #240342 solved the failing smoke tests on everything but 9.0.x, and we cant automatically backport, so this PR is needed. Also included are some error logging fixes that might be useful for solving issues with tests in the future.

Additional context: https://elastic.slack.com/archives/C01G6A31JMD/p1761235645302459

cc: @MichelLosier @kpollich @isaacaflores2

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
@MichelLosier @Supplementing
Allow fleet-setup retries for all environments (elastic#240342)
35c41c1 
non-serverless environments relied on integrations-server triggering
fleet setup retries externally. This change allows fleet setup retries
in all environments
@Supplementing Supplementing added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Fleet Team label for Observability Data Collection Fleet team labels Oct 29, 2025
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 29, 2025

Pinging @elastic/fleet (Team:Fleet)
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 29, 2025

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17
1 similar comment
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 29, 2025

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 29, 2025

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17
1 similar comment
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 29, 2025

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17
@Supplementing Supplementing changed the title [Fleet] Backport retry changes Oct 29, 2025
nchaulet
nchaulet approved these changes Oct 29, 2025
View reviewed changes
Copy link
Member

@nchaulet nchaulet left a comment

Choose a reason for hiding this comment

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

🚀
@Supplementing
Copy link
Contributor Author

Supplementing commented Oct 30, 2025

Closed as there are no future releases planned and the branch is closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team

4 participants

@Supplementing @elasticmachine @nchaulet @MichelLosier