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 known issue for stuck agent upgrade (8.12.0, 8.12.1) #908

Merged
merged 2 commits into from
Feb 12, 2024

Conversation

kilfoyle
Copy link
Contributor

@kilfoyle kilfoyle commented Feb 9, 2024

This adds a known issue for the stuck agent upgrades to the 8.12.0 and 8.12.1 Release Notes.

Thanks @julia for the really clear explanation!

Closes: #907


screen1
screen2

@kilfoyle kilfoyle requested a review from a team as a code owner February 9, 2024 15:47
Copy link

github-actions bot commented Feb 9, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

juliaElastic
juliaElastic previously approved these changes Feb 9, 2024
Copy link
Contributor

@juliaElastic juliaElastic left a comment

Choose a reason for hiding this comment

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

Looks great, thanks for the quick pr!

@juliaElastic
Copy link
Contributor

Unfortunately it looks like the force flag doesn't work as a workaround here, we have to come up with another one.

@juliaElastic
Copy link
Contributor

This is the new tested workaround: elastic/fleet-server#3264 (comment)

@kilfoyle
Copy link
Contributor Author

Thanks @juliaElastic! I've updated the steps, and also the PR description to show how it looks with the changes.

Copy link
Contributor

@juliaElastic juliaElastic left a comment

Choose a reason for hiding this comment

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

Looks good, thanks for the update!

@kilfoyle kilfoyle merged commit c29d352 into elastic:main Feb 12, 2024
3 checks passed
kilfoyle added a commit to kilfoyle/ingest-docs that referenced this pull request Feb 12, 2024
* Add known issue for stuck agent upgrade (8.12.0, 8.12.1)

* Fix workaround steps

(cherry picked from commit c29d352)
@kilfoyle
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.12

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

mergify bot pushed a commit that referenced this pull request Feb 12, 2024
* Add known issue for stuck agent upgrade (8.12.0, 8.12.1)

* Fix workaround steps

(cherry picked from commit c29d352)
kilfoyle added a commit that referenced this pull request Feb 12, 2024
* Add known issue for stuck agent upgrade (8.12.0, 8.12.1)

* Fix workaround steps

(cherry picked from commit c29d352)
kilfoyle added a commit that referenced this pull request Feb 14, 2024
* Add known issue for stuck agent upgrade (8.12.0, 8.12.1)

* Fix workaround steps

(cherry picked from commit c29d352)

Co-authored-by: David Kilfoyle <[email protected]>
Co-authored-by: David Kilfoyle <[email protected]>
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.

[REQUEST]: Create a known issue in fleet-server 8.12.0 and 8.12.1
3 participants