[Security Solution] Add known issue for date selection in Protection Updates #4228
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.
We discovered an issue in the Protection Updates feature released in
8.11.0
that we will fix for8.11.1
. We'd like to add another entry to known issues for8.11.0
before the fix goes out in the next patch.The issue is that if the user picks the current date, it's possible that we haven't released a protection update yet for that date, so the Agent will go to an Unhealthy state. The workaround is to pick a previous date like the day before. The upcoming fix will simply disallow users from selecting the current date from the UI to reduce the user confusion
Related bug ticket: elastic/kibana#170847