Skip to content
This repository was archived by the owner on Sep 17, 2024. It is now read-only.

fix: use new file name in elastic-package v0.26.0#1739

Merged
mdelapenya merged 2 commits intoelastic:7.16from
mdelapenya:fix-breaking-changes-elastic-package-7.16
Oct 29, 2021
Merged

fix: use new file name in elastic-package v0.26.0#1739
mdelapenya merged 2 commits intoelastic:7.16from
mdelapenya:fix-breaking-changes-elastic-package-7.16

Conversation

@mdelapenya
Copy link
Copy Markdown
Contributor

What does this PR do?

This PR updates the kibana config file retrieved from the tool in its v0.26.0 version

Why is it important?

The tool introduced a breaking change related to the kibana config file name to provide support for multiple versions on Kibana

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have run the Unit tests (make unit-test), and they are passing locally
  • I have run the End-2-End tests for the suite I'm working on, and they are passing locally
  • I have noticed new Go dependencies (run make notice in the proper directory)

Related issues

@mdelapenya mdelapenya added Team:Automation Label for the Observability productivity team v7.15.0 labels Oct 28, 2021
@mdelapenya mdelapenya requested a review from a team October 28, 2021 14:55
@mdelapenya mdelapenya self-assigned this Oct 28, 2021
@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Tests 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-10-28T14:56:07.320+0000

  • Duration: 68 min 27 sec

  • Commit: ccae604

Test stats 🧪

Test Results
Failed 9
Passed 220
Skipped 0
Total 229

Test errors 9

Expand to view the tests failures

Initializing / End-To-End Tests / arm64_fleet_permission_change / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-83a70bca-3033-4b7f-ac9e-5ea4b2687fcc/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_backend_processes / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-0479c807-bfb9-4083-b6d1-557e8366b5f5/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_linux_integration / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-0a994407-d290-4e3e-ba21-fbb5a5077106/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_policies / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-fd0248f6-4399-4eb3-89ad-d5d1ea1e7496/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_integrations / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-a76178dd-d27e-4189-9cf9-7dace56fae9e/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_preconfigured_policies / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-e302ab67-e201-49e8-9c1c-8acd1577f564/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_apm_server / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-4f458a72-d135-40aa-bf91-34d887f2e9c7/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / arm64_fleet_running_on_beats / [empty] – TEST-arm64-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file /var/lib/jenkins/workspace/PR-1739-1-a14f7768-185a-4bd3-bcd7-34c163183daa/src/github.com/elastic/e2e-testing/outputs/TEST-arm64-fleet.xml was length 0 
    

Initializing / End-To-End Tests / windows-2019_fleet_fleet_mode_agent / [empty] – TEST-windows-fleet.xml
  • no error details
  • Expand to view the stacktrace

     Test report file C:\Users\jenkins\workspace\PR-1739-1-508e9cd0-570b-4429-bf46-d3523a4a19e2\src\github.com\elastic\e2e-testing\outputs\TEST-windows-fleet.xml was length 0 
    

Steps errors 16

Expand to view the steps failures

Show only the first 10 steps failures

Run functional tests for arm64:fleet:permission_change && ~@nightly && ~debian && ~@skip:arm64
  • Took 13 min 19 sec . View more details here
  • Description: .ci/scripts/functional-test.sh "fleet" "permission_change && ~@nightly && ~debian && ~@skip:arm64" "7.x-SNAPSHOT" "7.x-SNAPSHOT"
Archive the artifacts
  • Took 0 min 12 sec . View more details here
  • Description: [2021-10-28T15:41:22.792Z] Archiving artifacts script returned exit code 2
Run functional tests for arm64:fleet:policies && ~@nightly && ~debian && ~@skip:arm64
  • Took 13 min 14 sec . View more details here
  • Description: .ci/scripts/functional-test.sh "fleet" "policies && ~@nightly && ~debian && ~@skip:arm64" "7.x-SNAPSHOT" "7.x-SNAPSHOT"
Archive the artifacts
  • Took 0 min 9 sec . View more details here
  • Description: [2021-10-28T15:43:05.758Z] Archiving artifacts script returned exit code 2
Run functional tests for arm64:fleet:backend_processes && ~@nightly && ~debian && ~@skip:arm64
  • Took 13 min 23 sec . View more details here
  • Description: .ci/scripts/functional-test.sh "fleet" "backend_processes && ~@nightly && ~debian && ~@skip:arm64" "7.x-SNAPSHOT" "7.x-SNAPSHOT"
Archive the artifacts
  • Took 0 min 9 sec . View more details here
  • Description: [2021-10-28T15:41:49.662Z] Archiving artifacts script returned exit code 2
Run functional tests for arm64:fleet:running_on_beats && ~@nightly && ~debian && ~@skip:arm64
  • Took 13 min 22 sec . View more details here
  • Description: .ci/scripts/functional-test.sh "fleet" "running_on_beats && ~@nightly && ~debian && ~@skip:arm64" "7.x-SNAPSHOT" "7.x-SNAPSHOT"
Archive the artifacts
  • Took 0 min 13 sec . View more details here
  • Description: [2021-10-28T15:43:19.913Z] Archiving artifacts script returned exit code 2
Run functional tests for arm64:fleet:preconfigured_policies && ~@nightly && ~debian && ~@skip:arm64
  • Took 13 min 22 sec . View more details here
  • Description: .ci/scripts/functional-test.sh "fleet" "preconfigured_policies && ~@nightly && ~debian && ~@skip:arm64" "7.x-SNAPSHOT" "7.x-SNAPSHOT"
Archive the artifacts
  • Took 0 min 10 sec . View more details here
  • Description: [2021-10-28T15:43:09.948Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 9

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

  • Name: Initializing / End-To-End Tests / arm64_fleet_permission_change / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_backend_processes / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_linux_integration / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_policies / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_integrations / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_preconfigured_policies / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_apm_server / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / arm64_fleet_running_on_beats / [empty] – TEST-arm64-fleet.xml
  • Name: Initializing / End-To-End Tests / windows-2019_fleet_fleet_mode_agent / [empty] – TEST-windows-fleet.xml

🤖 GitHub comments

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

  • /test : Re-trigger the build.


xpack.fleet.enabled: true
xpack.fleet.registryUrl: https://epr-staging.elastic.co
xpack.fleet.registryUrl: "http://package-registry:8080"
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Using local package registry

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I described my concerns about using the local package reigstry in https://github.com/elastic/e2e-testing/pull/1738/files#r738951910

Not sure if this line should be kept as it's now

@mdelapenya mdelapenya merged commit 043b29a into elastic:7.16 Oct 29, 2021
@mdelapenya mdelapenya deleted the fix-breaking-changes-elastic-package-7.16 branch November 2, 2021 16:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Team:Automation Label for the Observability productivity team v7.15.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants