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

Testing over storage of Integration Package assets in ES Cluster feature #84967

Closed
5 of 8 tasks
EricDavisX opened this issue Dec 3, 2020 · 5 comments
Closed
5 of 8 tasks
Assignees
Labels
Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@EricDavisX
Copy link
Contributor

EricDavisX commented Dec 3, 2020

This is the test ticket for the 'storage of packages in es' feature work, here: #83426

  • it is merged and available in 8.0. Please test there first. We will confirm and test in 7.12 as well, it is available now.

Feature description in short: We have moved the long term storage of Fleet registry assets into ES, it is loaded into Kibana Saved Objects still, but is not lost if Kibana is re-started - and better supports the case where a user wishes to downgrade the package version for any reason.

This will host the basic AC and general testing guidelines we want to follow through on:
A/C:

  • All features as previously discussed should remain functional, a smoke test will help cover this
  • Installing the 'custom logs' or 'Linux' package (as an example) should work and the logs functionality should be the same
  • upgrade of 7.11 Stack with x,y,z set of Integrations upgrades to 7.12 and still functions
  • uninstalling a package should work as before, it will no longer be shown in saved objects Kibana api.

notes:

  • User will know if they un-install it as it is manually done, otherwise the assets remain intact.

  • What API call can we make to see them:
    api/saved_objects/_find?type=epm-packages-assets

  • These saved objects are against the system index so they will not be visible in kibana stack monitoring

  • When uninstalling, the asset docs are removed from ES and the api call will not show them

Other general test env need:

  • browser tests? Answer:
  • Agent OS types or deploy types? Answer: not needed
  • Cloud test from snapshot vs self managed. Eric will cover self-managed (using e2e-testing framework)
  • others?
@EricDavisX EricDavisX added the Team:Fleet Team label for Observability Data Collection Fleet team label Dec 3, 2020
@EricDavisX EricDavisX self-assigned this Dec 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@EricDavisX
Copy link
Contributor Author

automation ticket for this is created at: elastic/e2e-testing#668

@dikshachauhan-qasource
Copy link

Hi @EricDavisX

We have completed our regression plan on 7.12.0 Build.

Test Plan Link: Ingest Manager 7.12.0 Regression Test Plan

Please Let us know if anything else is required.

Thanks
QAS

@EricDavisX
Copy link
Contributor Author

HI @dikshachauhan-qasource if we have run an upgrade test successfully from prior minor version and all is working then we can close this out.

@dikshachauhan-qasource
Copy link

Hi Eric

Thanks for the feedback.

Yes, we have covered Kibana Upgrade scenarios in our regression plan and functionality is working fine with previous installed agents as well as with new agents.

Hence, closing this out.

Thanks
QAS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants