Airgap standalone Elastic Agent Upgrade

Elastic Stack Elastic Agent
1

I'm running a standalone agent on an airgap Windows system using the zip deployment. I'm trying to upgrade from 8.19.0 to 8.19.15 as a test.

It appears that there is a way to use the elastic-agent.exe upgrade command with the --source-uri argument (docs say this argument accepts file://<file path>) to point to an Elastic Agent zip package to upgrade the agent and it appears to want to always look in "~\Elastic\Agent\data\elastic-agent-X.X.X-xxxxxx\downloads" no matter the path you give it.

I tried multiple paths (and slash variants) and even tried putting the zip file in the place it is looking for and it still fails claiming it can't find the zip package. Ironically after the command fails, it deletes the zip file I place in the downloads folder.

Am I doing this wrong? Is this supported?

image
image951×205 15.1 KB

image
image979×346 58.4 KB

2

Hi, The file:// isn't actually supported for --source-uri. the official command reference ( https://www.elastic.co/guide/en/fleet/8.19/elastic-agent-cmd-options.html#elastic-agent-upgrade-command ). For air-gapped upgrades, the supported approach is to host your own artifact registry and point --source-uri at it. See the Air-gapped environments docs for details.

3

Yeah, now that I'm looking, it appears that the file:// option is supported in 9.x (Elastic Agent Upgrade - Source-URI) and if I change the version to 8.19.x on the docs page, it isn't listed. In my case, hosting my own registry is not possible in this environment. I'm running standalone agents. I guess since this does seem to be supported in newer versions, this is resolved by upgrading.