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

add_cloud_metadata produces errors running in non-cloud elastic-agent install #36018

Closed
fearful-symmetry opened this issue Jul 6, 2023 · 2 comments · Fixed by #36829
Closed
Labels
bug needs_team Indicates that the issue/PR needs a Team:* label

Comments

@fearful-symmetry
Copy link
Contributor

For confirmed bugs, please report:

  • Version: 8.9.0
  • Operating System: Linux
  • Steps to Reproduce: Install beats via elastic-agent 8.9.0 on a local Linux instance

Discovered during 8.9.0 testing. Right now, in non-cloud environments, add_cloud_metadata logs a few errors:

{"log.level":"warn","@timestamp":"2023-07-06T18:24:06.085Z","message":"error fetching EC2 Identity Document: operation error ec2imds: GetInstanceIdentityDocument, canceled, context deadline exceeded.","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"filestream-monitoring","type":"filestream"},"log":{"source":"filestream-monitoring"},"log.logger":"add_cloud_metadata","log.origin":{"file.line":91,"file.name":"add_cloud_metadata/provider_aws_ec2.go"},"service.name":"filebeat","ecs.version":"1.6.0","ecs.version":"1.6.0"}

I assume this is an innocuous error, but it is a tad annoying.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 6, 2023
@andrewkroh
Copy link
Member

andrewkroh commented Jul 11, 2023

This appears to be related to the number (2) bullet in #33058.

but it is a tad annoying.

Very much so agree.

@tommyers-elastic
Copy link
Contributor

can we close this as a dup of #35147 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants