You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on elastic/elastic-package#279 to enable the Fleet Server and during the weekly status check for all blockers, I found this additional one. It seems that the agent can't pick up the right policy (even though it's marked as healthy?).
elastic-package stack up -v -d (to boot up the Elastic stack)
The stack will be reported as healthy, but it isn't. Last changes were applied after @nchaulet 's review (thanks!). We observed this problem then: elastic/beats#24453 . Now it's changed (maybe regression?)
The text was updated successfully, but these errors were encountered:
Blocker for elastic/elastic-package#278
I'm working on elastic/elastic-package#279 to enable the Fleet Server and during the weekly status check for all blockers, I found this additional one. It seems that the agent can't pick up the right policy (even though it's marked as healthy?).
This is something new comparing to the last week.
Steps to reproduce:
make build
elastic-package stack update
(to fetch latest 7.13.0-SNAPSHOT)elastic-package stack up -v -d
(to boot up the Elastic stack)The stack will be reported as healthy, but it isn't. Last changes were applied after @nchaulet 's review (thanks!). We observed this problem then: elastic/beats#24453 . Now it's changed (maybe regression?)
The text was updated successfully, but these errors were encountered: