elastic-agent install 'interactive' command is unable to enroll the agent into Fleet

[ghost]

Kibana version:
Kibana: 8.0.0-SNAPSHOT

Elasticsearch version:
Elasticsearch: 8.0.0-SNAPSHOT

Host OS and Browser version:
Windows 10 , All

Original install method (e.g. download page, yum, from source, etc.):
From 8.0.0-SNAPSHOT on staging cloud environment https://staging.found.no/

Description
elastic-agent install command is unable to enroll the agent into Fleet

Preconditions

1. 8.0.0-SNAPSHOT Kibana cloud environment should be available.

Steps to Reproduce

1. Open the 8.0.0-SNAPSHOT Kibana cloud environment in browser.
2. Download the 8.0.0 agent from artifact link(https://console.cloud.google.com/storage/browser/beats-ci-artifacts/pull-requests/pr-21206/elastic-agent?pageState=(%22StorageObjectListTable%22:(%22f%22:%22%255B%255D%22))&prefix=&forceOnObjectsSortingFiltering=false)
3. RDP to the endpoint and place the agent.
4. Unarchive the agent
5. Open powershell as admin and run the command for interactive mode:
   ./elastic-agent install
6. Observe that installation is successful bit agent is unable to enroll into fleet.

Test data
N/A

Impacted Test case id
N/A

Actual Result
[Ingest Management]: elastic-agent install command is unable to enroll the agent into Fleet

Expected Result
[Ingest Management]: elastic-agent install command should be able to enroll the agent into Fleet

What's working

• Issue is also occurring for mac and linux

What's not working

• N/A

Screenshot

Logs
N/A

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[botelastic]

This issue doesn't have a Team:<team> label.

[ghost]

@muskangulati-qasource Please review the bug

[muskangulati-qasource]

Reviewed & assigned to @EricDavisX .

[EricDavisX]

confirmed on Windows (as seen here) and macOS (by Eric, screenshots sent to Blake)

[EricDavisX]

note, the usage above is actually a 'negative' test which is passing, because it uses the enrollment token uuid instead of the token itself, the 'secret' which is the string that ends with the == in the UI.

So I can close this out as not an issue. But, I'll say that when I used the secret it still failed. Blake is fixing it so we can re-test soon.