-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Fleet] Tests for the Agent restructure / symlink work #21023
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
The upgrade / rollback scenario aren't implemented yet, its still a work in progress. |
Hi @EricDavisX / @ph Thank you for sharing the feedback. Please keep us posted once upgrade / rollback scenarios are implemented and share the exact steps to validate the same. |
@EricDavisX I believe this could be closed? |
I was confused on which core focus this issue was. It is about the re-testing of Agent install. It is confirmed as implemented and works well in many cases. There are open issues and questions we are tackling and they are all logged separately. So, yes, lets close this out. |
@rahulgupta-qasource about the upgrade-agent cases, it is testable and we will track that separately as well |
In this PR we had some test questions, since it is closed I'd like to open an issue for testing and automation work and track it here:
#20400 (comment)
@michalpristas can you make sure any changes that break the e2e-testing are fixed?
@rahulgupta-qasource we can use this as a running tally of questions + tests. I'll seed the list with what questions we had from the pr.
Queries:
Could you please let us know if we have to validate the above packages on 7.9.2-SNAPSHOT or 8.0.0-SNAPSHOT also.
Could you please share the exact steps to execute the upgrade/rollback scenarios (say as per comment #20400 (review) , #20400 (comment) and #20400 (comment) )
Please let us know if we are missing something to validate this ticket or need to add any other validation scenario.
The text was updated successfully, but these errors were encountered: