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

Added support for bulk api update change#3043

Merged
michalpristas merged 8 commits intoelastic:mainfrom
michalpristas:fix/update-api-key
Sep 27, 2022
Merged

Added support for bulk api update change#3043
michalpristas merged 8 commits intoelastic:mainfrom
michalpristas:fix/update-api-key

Conversation

@michalpristas
Copy link
Copy Markdown
Contributor

Addes support for bulk API key change which does not update api key for output

What does this PR do?

Removes Default API key and operates on api key on output level

Why is it important?

Keep in par with fleet server

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)

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Sep 26, 2022

This pull request does not have a backport label. Could you fix it @michalpristas? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

@michalpristas michalpristas self-assigned this Sep 26, 2022
@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Sep 26, 2022
@michalpristas michalpristas added the backport-v8.5.0 Automated backport with mergify label Sep 26, 2022
@mergify mergify bot removed the backport-skip Skip notification from the automated backport with mergify label Sep 26, 2022
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Sep 26, 2022

💔 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: 2022-09-27T09:04:02.186+0000

  • Duration: 66 min 43 sec

Test stats 🧪

Test Results
Failed 6
Passed 359
Skipped 0
Total 365

Test errors 6

Expand to view the tests failures

Initializing / End-To-End Tests / fleet_debian_10_amd64_system_integration / Adding memory system/metrics Integration to a Policy – System Integration
    Expand to view the error details

     Step "system/metrics" with "memory" metrics are present in the datastreams 
    

  • no stacktrace
Initializing / End-To-End Tests / fleet_sles15_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
    Expand to view the error details

     Step the "elastic-endpoint" process is in the "stopped" state on the host 
    

  • no stacktrace
Initializing / End-To-End Tests / fleet_debian_11_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
    Expand to view the error details

     Step the "elastic-endpoint" process is in the "stopped" state on the host 
    

  • no stacktrace
Initializing / End-To-End Tests / fleet_debian_10_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
    Expand to view the error details

     Step the "elastic-endpoint" process is in the "stopped" state on the host 
    

  • no stacktrace
Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
    Expand to view the error details

     Step the "elastic-endpoint" process is in the "stopped" state on the host 
    

  • no stacktrace
Initializing / End-To-End Tests / fleet_debian_10_amd64_stand_alone_mode / Deploying a default stand-alone agent – Stand-alone Mode
    Expand to view the error details

     Step there is new data in the index from agent: not enough hits in the logs-elastic_agent-default index yet. Current: 0, Desired: 20 
    

  • no stacktrace

Steps errors 31

Expand to view the steps failures

Show only the first 10 steps failures

Configure node for testing
  • Took 5 min 59 sec . View more details here
  • Description: make -C .ci setup-node
Configure node for testing
  • Took 1 min 9 sec . View more details here
  • Description: make -C .ci setup-node
Configure node for testing
  • Took 1 min 8 sec . View more details here
  • Description: make -C .ci setup-node
Run tests in the node
  • Took 14 min 13 sec . View more details here
  • Description: make -C .ci run-tests
Run tests in the node
  • Took 11 min 0 sec . View more details here
  • Description: make -C .ci run-tests
Run tests in the node
  • Took 11 min 6 sec . View more details here
  • Description: make -C .ci run-tests
Run tests in the node
  • Took 16 min 56 sec . View more details here
  • Description: make -C .ci run-tests
Configure node for testing
  • Took 5 min 9 sec . View more details here
  • Description: make -C .ci setup-node
Configure node for testing
  • Took 1 min 8 sec . View more details here
  • Description: make -C .ci setup-node
Configure node for testing
  • Took 1 min 12 sec . View more details here
  • Description: make -C .ci setup-node

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors 6

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

  • Name: Initializing / End-To-End Tests / fleet_debian_10_amd64_system_integration / Adding memory system/metrics Integration to a Policy – System Integration
  • Name: Initializing / End-To-End Tests / fleet_sles15_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_debian_11_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_debian_10_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_backend_processes / Removing Endpoint from Agent policy stops the connected Endpoint – Backend Processes
  • Name: Initializing / End-To-End Tests / fleet_debian_10_amd64_stand_alone_mode / Deploying a default stand-alone agent – Stand-alone Mode

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

@michalpristas
Copy link
Copy Markdown
Contributor Author

PR fixes affected tests.
Needs a follow up once stack version is updated, both options to been updated

@kuisathaverat
Copy link
Copy Markdown
Contributor

kuisathaverat commented Sep 27, 2022

@michalpristas after this change, Which versions of feet can be tested with the e2e? I mean, Is this change compatible with 7.x, 8.0, 8.2, 8.3, 8.4, and 8.5? It is only to know on which version the test will fail (or should be disabled)

@michalpristas
Copy link
Copy Markdown
Contributor Author

michalpristas commented Sep 27, 2022

it is 8.5 up

@michalpristas michalpristas merged commit 4710ae5 into elastic:main Sep 27, 2022
v1v added a commit to v1v/e2e-testing that referenced this pull request Oct 19, 2022
* upstream/main: (35 commits)
  bump stack version 8.6.0-6545f2df (elastic#3135)
  bump stack version 8.6.0-cae815eb (elastic#3130)
  bump stack version 8.6.0-54a302f0 (elastic#3125)
  bump stack version 8.6.0-233dc5d4 (elastic#3122)
  bump stack version 8.6.0-40086bc7 (elastic#3115)
  bump stack version 8.6.0-5a8d757d (elastic#3111)
  bump stack version 8.6.0-c49fac70 (elastic#3106)
  bump stack version 8.6.0-7c9f25a9 (elastic#3105)
  bump stack version 8.6.0-d939cfde (elastic#3096)
  bump stack version 8.6.0-0fca2953 (elastic#3081)
  Turn off all tests but Fleet mode and upgrade for Beats and Agent pipelines (elastic#3077)
  backport: Add 8.5 branch (elastic#3029)
  Only run Fleet mode and upgrade tests on 2 platforms (elastic#3054)
  fix: added setuptools-rust to requiremets.txt (elastic#3048)
  Added support for bulk api update change (elastic#3043)
  Making Changes for Docs for E2E setup (elastic#2929)
  Update ingest notifications channel (elastic#3023)
  chore: stringify http responses (elastic#2772)
  Adding support for v1.25.0 k8s (elastic#2975)
  Fix testcases for fleet api (elastic#2999)
  ...
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

backport-v8.5.0 Automated backport with mergify

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants