-
Notifications
You must be signed in to change notification settings - Fork 145
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
[Elastic-Agent] Elastic Agent doesn't read sourceURI
parameter from the policy.
#766
Comments
fyi @michalpristas & @pierrehilbert |
tested with latest snapshot after changing URI i see this in logs: when initiating update to SNAPSHOT, snapshot artifact URI is hit as expected:
when initiating with made up version
resulted in:
|
@criamico have you managed to test it on your end? can we close the issue now? |
yes, I think you can close this issue @michalpristas |
thanks,closing |
Elastic Agent doesn't read
sourceURI
parameter from the policy.I discovered this bug while testing #756. While the policy reloading itself works fine, the agent doesn't seem to read the sourceURI passed through the policy under
agent.download.source_uri
.Test case 1
I tried to upgrade the agent and would expect the agent to pick up the source URI from the policy, however it doesn't read it.
Created In Kibana a new source download source object with a mock source URI
https://test-registry.co
Created a new agent policy and assigned the download source object to it
Did a single agent update with no source URI. I had to disable some internal version checks in fleet UI
The agent is trying to update from the default registry - the custom source URI doesn't appear at all:
The expected behaviour would be trying to download the agent from
https://test-registry.co
, but it doesn't even appear in the logs.Verified that in
.fleet_actions
there is no URI:Test Case 2
I tried to pass version "8.4.0-SNAPSHOT":
Source URI is not there as well and the agent is downloading from a different hardcoded path
https://snapshots.elastic.co/
The text was updated successfully, but these errors were encountered: