elastic / elastic/fleet-server

[Fleet] [FIPS] Fleet Server fails to enroll when running install command on Windows x64 with FIPS Elastic Agent artifact

Open
#7,145 7 comments 0 reactions 0 assignees View on GitHub
bug impact:high Team:Elastic-Agent-Control-Plane
Dominant language
Go
Stars
113
Forks
117
Avg merge
1d 16h
Merged PRs (30d)
112

Description

**Kibana Build details:**
```
VERSION: 9.5.0-SNAPSHOT
BUILD: 104114
COMMIT: 2860842a141c80f2cef7f5c27a5840a157656ac2
```

**Host OS:** All

**Preconditions:**
1. 9.5.0 SNAPSHOT Kibana should be available.
2. Windows x64 endpoint is available.
3. Elastic Agent 9.5.0 64-bit (x86_64) FIPS artifact has been downloaded.

**Steps to reproduce:**

1. Navigate to Fleet → Agents.
2. Click Add Fleet Server and add a new Fleet Server host: https://:8220.
3. Copy the generated enrollment command.
4. Run the Fleet Server install command on the Windows x64 machine.
5. Observe that Fleet Server fails to enroll and errors are displayed in the CLI output.

**Expected Result:**
- Fleet Server should enroll successfully on Windows x64 using the FIPS Elastic Agent artifact, with no errors in the CLI.

**Screen-shot**

Image

**Ticket:**
- https://github.com/elastic/ingest-dev/issues/7431

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.