-
Notifications
You must be signed in to change notification settings - Fork 149
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
5k+ download attempts within few seconds in agent logs while upgrading 8.11.3 agent to 8.12.0 with invalid agent binary. #3914
Comments
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
@manishgupta-qasource Please review. |
Secondary review for this ticket is Done |
@ycombinator Do you think this is the same issue as #3915? |
Yes, it is. I will close #3915 as a duplicate of this one. |
This seems to only reproduce for agents enrolled in Fleet. Looking at changes between 8.11.1 and 8.11.3 #3803 is the only one that jumped out as related. Reverting #3803 fixes the problem so somehow it is causing this. Possibly the settings updates are causing the backoff interval to reset continuously. FYI @AndersonQ |
I'm on it. I found the issue already |
the fix is here: #3930 |
Hi @AndersonQ We have revalidated this issue on latest 8.12.0 BC5 kibana cloud environment and found it still reproducible. Observations:
Build details: Agent Logs: Hence, we are reopening this issue. Could you please confirm if this issue will be fixed while upgrading from 8.12.0 onwards? Please let us know if anything else is required from our end. Thanks! |
Hey @amolnater-qasource just to understand, what is this invalid agent binary? |
I believe he meant an invalid Agent Binary Download url |
@amolnater-qasource, I cannot reproduce it.
the agent logs:
I know I'm using linux, but this part of the code isn't platform specific. Did you try with linux, it is happening only on windows or with any platform? |
Hi @AndersonQ
Yes we have tested this with linux SLES only. Just to confirm we are validating this while upgrading 8.11.3 to 8.12.0, I assume the merges won't be available in this version. Should we re-test once the 8.12.1 patch is available?
@pierrehilbert We mean the agent binary url which we update under the Fleet Settings. Screenshot: Please let us know if we are missing anything here. |
The fix from @AndersonQ is not in 8.11.3 so I think this is normal to still have the problem for now and as you mentioned, to test this again from 8.12.0 to 8.12.1 when it will be available. |
@amolnater-qasource should we close this one again then? |
Sure, @pierrehilbert We will revalidate this once the 8.12.1 patch is available and will re-open if required. Thanks! |
You should be able to test this upgrading from 8.12.0 to 8.13.0-SNAPSHOT without waiting for 8.12.1. |
Hi Team, We have revalidated this issue on latest 8.13.0-SNAPSHOT kibana cloud environment and found it fixed now. Observations:
Build details: Agent Logs: Hence we are marking this issue as QA:Validated. Thanks! |
Super, thx @amolnater-qasource |
|
Kibana Build details:
Host OS: SLES15
Preconditions:
Steps to reproduce:
NOTE:
Screenshot:
Expected Result:
Download attempts shouldn't be so frequent while upgrading 8.11.3 agent to 8.12.0 with invalid agent binary.
Logs:
8.11.3[Issue]:
elastic-agent-diagnostics-2023-12-14T08-19-39Z-00.zip
8.11.1[Not an issue]:
elastic-agent-diagnostics-2023-12-14T07-57-23Z-00.zip
The text was updated successfully, but these errors were encountered: