Skip to content

[8.0](backport #28667) Explicitly warns about misconfiguration preventing Filebeat to start …#28928

Closed
mergify[bot] wants to merge 2 commits into8.0from
mergify/bp/8.0/pr-28667
Closed

[8.0](backport #28667) Explicitly warns about misconfiguration preventing Filebeat to start …#28928
mergify[bot] wants to merge 2 commits into8.0from
mergify/bp/8.0/pr-28667

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Nov 11, 2021

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

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

You are currently cherry-picking commit b3789b56fc.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   x-pack/filebeat/input/awss3/config.go

no changes added to commit (use "git add" and/or "git commit -a")

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

…from v8.0 (#28667)

(cherry picked from commit b3789b5)

# Conflicts:
#	x-pack/filebeat/input/awss3/config.go
@mergify mergify Bot added backport conflicts There is a conflict in the backported pull request labels Nov 11, 2021
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 11, 2021
@botelastic
Copy link
Copy Markdown

botelastic Bot commented Nov 11, 2021

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 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: 2021-11-11T10:08:18.671+0000

  • Duration: 13 min 18 sec

  • Commit: 5758403

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

Steps errors 2

Expand to view the steps failures

x-pack/filebeat-lint - make -C x-pack/filebeat check;make -C x-pack/filebeat update;make -C filebe
  • Took 1 min 48 sec . View more details here
  • Description: make -C x-pack/filebeat check;make -C x-pack/filebeat update;make -C filebeat check;make -C filebeat 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

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.

@mergify mergify Bot deleted the mergify/bp/8.0/pr-28667 branch November 11, 2021 10:58
@elasticmachine
Copy link
Copy Markdown
Contributor

💔 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: 2021-11-11T10:57:23.947+0000

  • Duration: 3 min 33 sec

  • Commit: 3268784

Steps errors 2

Expand to view the steps failures

Git fetch
  • Took 0 min 2 sec . View more details here
  • Description: git fetch https://${GIT_USERNAME}:${GIT_PASSWORD}@github.com/elastic/beats.git +refs/pull/*/head:refs/remotes/origin/pr/* > fetch.log 2>&1
Archive the artifacts
  • Took 0 min 1 sec . View more details here
  • Description: fetch.log

❕ Flaky test report

No test was executed to be analysed.

🤖 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.

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 needs_team Indicates that the issue/PR needs a Team:* label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants