Skip to content

Fleet update fails wit missing .asc file #126440

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

Closed
drummbelbummel opened this issue Apr 8, 2025 · 1 comment
Closed

Fleet update fails wit missing .asc file #126440

drummbelbummel opened this issue Apr 8, 2025 · 1 comment
Labels
>bug needs:triage Requires assignment of a team area label

Comments

@drummbelbummel
Copy link

Elasticsearch Version

Version: 8.17.4, Build: deb/c63c7f5f8ce7d2e4805b7b3d842e7e792d84dda1/2025-03-20T15:39:59.811110136Z, JVM: 23

Installed Plugins

No response

Java Version

JVM: 23

OS Version

different linux

Problem Description

I want to update my agents via fleet. What is working fine on windows fails on linux. Tested with kali linux, kali purple, proxmox and an old debian.
Every time it is a missing .asc file.
If i go to them machine and download the file with wget while the fleet update is running - everything is working fine.
As i can download the file with wget in the machine itself i can not see any cause in the infrastructure?

Steps to Reproduce

Start agent update via fleet, wait to fail, check agent status

Logs (if relevant)

┌──(root㉿yoga-2-purple)-[/home/kali]
└─# /opt/Elastic/Agent/elastic-agent status
┌─ fleet
│ └─ status: (HEALTHY) Connected
├─ elastic-agent
│ └─ status: (HEALTHY) Running
└─ upgrade_details
├─ target_version: 8.17.4
├─ state: UPG_FAILED
├─ action_id: 2a18eb82-9f3f-456a-bbbb-07fbfa30ec7f
└─ metadata
├─ failed_state: UPG_DOWNLOADING
└─ error_msg: failed verification of agent binary: could not get .asc file: fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-8.17.3-0efe49/downloads/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-8.17.3-0efe49/downloads/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc: no such file or directory
fetching asc file from https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc: failed loading public key: Get "https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc": context deadline exceeded

[elastic_agent][error] upgrade to version 8.17.4 failed: failed verification of agent binary: could not get .asc file: fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-8.17.3-0efe49/downloads/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-8.17.3-0efe49/downloads/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc: no such file or directory
fetching asc file from https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc: failed loading public key: Get "https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-8.17.4-linux-x86_64.tar.gz.asc": context deadline exceeded

@drummbelbummel drummbelbummel added >bug needs:triage Requires assignment of a team area label labels Apr 8, 2025
@jbaiera
Copy link
Member

jbaiera commented Apr 14, 2025

Thanks for your interest in the Elasticsearch project. Unfortunately, this looks like it might be some kind of issue with another Elastic product. I would try reopening this issue against an Elastic project that most aligns with the problem you're experiencing (maybe https://github.com/elastic/fleet-server, there are a few for fleet/agent).

@jbaiera jbaiera closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug needs:triage Requires assignment of a team area label
Projects
None yet
Development

No branches or pull requests

2 participants