Skip to content

Conversation

@mtojek
Copy link
Contributor

@mtojek mtojek commented Jan 31, 2022

Fixes: #655

Zrzut ekranu 2022-01-31 o 17 09 52

@mtojek mtojek self-assigned this Jan 31, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jan 31, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Reason: null

  • Start Time: 2022-01-31T16:32:59.577+0000

  • Duration: 30 min 7 sec

  • Commit: 3536ffa

Test stats 🧪

Test Results
Failed 0
Passed 471
Skipped 0
Total 471

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@mtojek mtojek requested a review from a team January 31, 2022 15:04
@mtojek mtojek marked this pull request as ready for review January 31, 2022 15:40
Copy link
Member

@jsoriano jsoriano left a comment

Choose a reason for hiding this comment

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

Thanks!

@mtojek
Copy link
Contributor Author

mtojek commented Jan 31, 2022

Error is unrelated, but we may need to chase it finally:

�[36melastic-agent_1              |�[0m {"log.level":"info","@timestamp":"2022-01-31T16:30:28.286Z","log.origin":{"file.name":"cmd/enroll_cmd.go","file.line":253},"message":"Elastic Agent might not be running; unable to trigger restart","ecs.version":"1.6.0"}
�[36melastic-agent_1              |�[0m Error: could not read configuration file /usr/share/elastic-agent/state/elastic-agent.yml: yaml: line 47: could not find expected ':'
�[36melastic-agent_1              |�[0m For help, please see our troubleshooting guide at https://www.elastic.co/guide/en/fleet/8.1/fleet-troubleshooting.html

@mtojek
Copy link
Contributor Author

mtojek commented Jan 31, 2022

/test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Predefine agent policies in the Kibana config

4 participants