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

[7.17](backport #36829) [add_cloud_metadata] Remove logger for AWS/EC2 #37150

Closed
wants to merge 3 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 20, 2023

This is an automatic backport of pull request #36829 done by Mergify.
Cherry-pick of d66a000 has failed:

On branch mergify/bp/7.17/pr-36829
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit d66a0001ac.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   libbeat/processors/add_cloud_metadata/providers.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/processors/add_cloud_metadata/provider_aws_ec2.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Remove logger.

* Add error message.

* Add log message

(cherry picked from commit d66a000)

# Conflicts:
#	libbeat/processors/add_cloud_metadata/provider_aws_ec2.go
@mergify mergify bot requested a review from a team as a code owner November 20, 2023 10:57
@mergify mergify bot requested review from ycombinator and removed request for a team November 20, 2023 10:57
@mergify mergify bot added the backport label Nov 20, 2023
@mergify mergify bot requested a review from rdner November 20, 2023 10:57
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Nov 20, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 20, 2023
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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

  • Start Time: 2023-11-20T10:57:26.635+0000

  • Duration: 38 min 32 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

Steps errors 4

Expand to view the steps failures

libbeat-shipping-to-next-major - STACK_ENVIRONMENT=next-major mage pythonIntegTest
  • Took 16 min 1 sec . View more details here
  • Description: STACK_ENVIRONMENT=next-major mage pythonIntegTest
libbeat-shipping-to-next-major - STACK_ENVIRONMENT=next-major mage pythonIntegTest
  • Took 2 min 8 sec . View more details here
  • Description: STACK_ENVIRONMENT=next-major mage pythonIntegTest
libbeat-shipping-to-next-major - STACK_ENVIRONMENT=next-major mage pythonIntegTest
  • Took 7 min 32 sec . View more details here
  • Description: STACK_ENVIRONMENT=next-major mage pythonIntegTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@constanca-m
Copy link
Contributor

@Mergifyio rebase

Copy link
Contributor Author

mergify bot commented Nov 20, 2023

rebase

✅ Nothing to do for rebase action

@elastic elastic deleted a comment from mergify bot Nov 20, 2023
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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

  • Duration: 29 min 53 sec

Pipeline error 1

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@pierrehilbert pierrehilbert added the Team:Elastic-Agent Label for the Agent team label Nov 20, 2023
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 20, 2023
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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

  • Start Time: 2023-11-20T15:01:10.652+0000

  • Duration: 24 min 34 sec

Test stats 🧪

Test Results
Failed 0
Passed 119
Skipped 5
Total 124

Steps errors 2

Expand to view the steps failures

x-pack/elastic-agent-lint - make -C x-pack/elastic-agent check;make -C x-pack/elastic-agent update;
  • Took 4 min 50 sec . View more details here
  • Description: make -C x-pack/elastic-agent check;make -C x-pack/elastic-agent update;make check-no-changes;
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 2'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify mergify bot deleted the mergify/bp/7.17/pr-36829 branch November 21, 2023 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants