Skip to content
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

[Self-Managed]: Appropriate production mode commands for fleet server installation not available under Agents tab. #131212

Closed
amolnater-qasource opened this issue Apr 29, 2022 · 4 comments · Fixed by #131814
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

Kibana version: 8.3 Snapshot Kibana self-managed environment

Host OS and Browser version: Windows, All

Build details:

VERSION: 8.3.0 Snapshot self-managed
BUILD: 52384
COMMIT: 1fbf477afb81d8fc899b950012e035977af83f46

Preconditions:

  1. 8.3 Snapshot Kibana self-managed environment should be available.

Steps to reproduce:

  1. On fresh Kibana setup navigate to Fleet tab.
  2. Navigate to advanced tab.
  3. Click create policy>Select production mode>Add Host>Generate service token.
  4. Observe appropriate command for fleet server installation using production mode is not available.

Expected Result:
Production mode commands for fleet server installation should be available under Agents tab.

Expected command:

.\elastic-agent.exe install --url=`
  --fleet-server-es= `
  --fleet-server-service-token=`
  --certificate-authorities=<PATH_TO_CA> `
  --fleet-server-es-ca=<PATH_TO_ES_CERT> `
  --fleet-server-cert=<PATH_TO_FLEET_SERVER_CERT> `
  --fleet-server-cert-key=<PATH_TO_FLEET_SERVER_CERT_KEY>

Screen Recording:

ec2-3-208-24-242.-.ec2-3-208-24-242.compute-1.amazonaws.com.-.Remote.Desktop.Connection.2022-04-28.14-19-55.mp4
@amolnater-qasource amolnater-qasource added bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Apr 29, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@manishgupta-qasource Please review.

@manishgupta-qasource
Copy link

Secondary review for this ticket is Done

kpollich added a commit to kpollich/kibana that referenced this issue May 9, 2022
kpollich added a commit that referenced this issue May 9, 2022
* Fix newline rendering in Fleet Server commands

Fixes #131110

* Fix production deployment Fleet Server commands

Fixes #131212

* Fix max width issue w/ Fleet Server Host combobox

Fixes #131591
@amolnater-qasource
Copy link
Author

Hi @kpollich
We have revalidated this issue on latest 8.3 Snapshot Kibana self-managed environment and found it fixed now.

  • Correct production mode commands are available for Fleet Server installation under Agents tab.

Build details:
BUILD: 52694
COMMIT: e3e9e00

Screenshots:
6
7

Hence marking this as QA:Validated.
Thanks

@amolnater-qasource amolnater-qasource added the QA:Validated Issue has been validated by QA label May 12, 2022
kertal pushed a commit to kertal/kibana that referenced this issue May 24, 2022
* Fix newline rendering in Fleet Server commands

Fixes elastic#131110

* Fix production deployment Fleet Server commands

Fixes elastic#131212

* Fix max width issue w/ Fleet Server Host combobox

Fixes elastic#131591
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants