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

[8.12] Add known issue for stuck agent upgrade (8.12.0, 8.12.1) (backport #908) #912

Merged
merged 2 commits into from
Feb 14, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 12, 2024

This is an automatic backport of pull request #908 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Add known issue for stuck agent upgrade (8.12.0, 8.12.1)

* Fix workaround steps

(cherry picked from commit c29d352)
@mergify mergify bot requested a review from a team as a code owner February 12, 2024 18:12
@mergify mergify bot added the backport label Feb 12, 2024
Copy link

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.

Copy link
Contributor Author

mergify bot commented Feb 14, 2024

This pull request is now in conflict. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b mergify/bp/8.12/pr-908 <remote-repo>/mergify/bp/8.12/pr-908
git merge <remote-repo>/8.12
git push <remote-repo> mergify/bp/8.12/pr-908

@kilfoyle kilfoyle merged commit 60a6208 into 8.12 Feb 14, 2024
3 checks passed
@mergify mergify bot deleted the mergify/bp/8.12/pr-908 branch February 14, 2024 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant