-
Notifications
You must be signed in to change notification settings - Fork 143
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
[Agent Upgrade]: Agents gets upgraded automatically after user abort the agent upgrade. #473
Comments
@manishgupta-qasource Please review. |
Secondary review for this ticket is Done |
@samratbhadra-qasource What options did you use for the scheduling? I'm curious if this may actually be the same bug as elastic/kibana#136022 |
Hi @joshdover, Earlier, we have used 'Immediately' option at Maintenance Window on 'Upgrade Agent' modal. Further, we have re-investigated it with below scenarios: Scenario 2: Scheduled Date and Time is set to next available active time slot from the current time on 'Upgrade Agent' modal.
Scenario 3: Maintenance Window is selected '1 hour' on 'Upgrade Agent' modal on selecting more than one Agents
Build details:
Logs: Mac: We will re-validate this ticket once the fixes are available. Thanks! |
|
Closing this as fixed, feel free to reopen it if need be. |
Hi Team, We have re-validated this issue on the latest 8.14.0 BC5 Kibana cloud environment and found it fixed now. Observations:
Build details: Hence, we are marking this issue as QA: Validated. Thanks |
Describe the bug:
Agents gets upgraded automatically even after user abort the agent upgrade.
Build Details:
VERSION: 8.3.0-SNAPSHOT
COMMIT: c993ff2a4fa10898d5a6e15aeb1d0848534ae48e
BUILD: 53035
ARTIFACT LINK: https://snapshots.elastic.co/8.3.0-a497a6ef/summary-8.3.0-SNAPSHOT.html
Preconditions:
Steps to Reproduce:
Expected Result:
Agents should not get upgraded automatically after user abort the agent upgrade.
Screenshot:
Logs:
Windows:
Winlogs.zip
MAC:
elastic-agent-diagnostics-2022-05-25T07-09-21Z-00.zip
The text was updated successfully, but these errors were encountered: