Cherry-pick #21461 to 7.x: Send updating state #21530
Merged
michalpristas merged 1 commit intoelastic:7.xfrom Oct 5, 2020
Merged
Cherry-pick #21461 to 7.x: Send updating state #21530michalpristas merged 1 commit intoelastic:7.xfrom
michalpristas merged 1 commit intoelastic:7.xfrom
Conversation
[Ingest Manager] Send updating state (elastic#21461)
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #21461 to 7.x branch. Original message:
What does this PR do?
This PR reports updating state of application after update process is started and error in case it is finished with failure
Tested with elastic/kibana#78810 after suggested changes (i did them manually) i started agent without starting a file server so UPDATE fails i got this (as expected)
UPDATE is ACK-ed and Error there is reported, under ACK there is line saying STATE was switched to UPDATING
after i started server and rekicked UPDATE action
update was ACKed and state switched to RUNNING after it finished.
Status on list page was
ONLINEthenUPDATINGand then backONLINE. Even though there were errors, so i guess this will be an object of next iteration.Why is it important?
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.