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

[Fleet] On-prem Instructions for setting fleet-server displayed under add agent flyout on cloud deployments #104280

Closed
dikshachauhan-qasource opened this issue Jul 5, 2021 · 9 comments
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. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@dikshachauhan-qasource
Copy link

dikshachauhan-qasource commented Jul 5, 2021

Kibana version: 7.14 BC1 Kibana Cloud-qa environment

Host OS and Browser version: Chrome, Firefox and edge

Preconditions:

  1. 7.14 BC1 Kibana Cloud-qa environment should be available.

Build Details:

BUILD 42292
COMMIT 071a74e02f82b79a4a10026b5c9e02d593112fd4
  1. Any user defined policy having Fleet-server integration say 'test1' should be available.

Steps to reproduce:
- Login to Kibana.
- Navigate to Fleet>Agents tab.
- Click on 'Add Agent' button and select policy as 'test1'.
- Observe, On-prem Instructions for setting fleet-server displayed.

Expected result:

  • 4-step Instructions for setting fleet-server should be displayed as per cloud deployment.
  • No steps related to 'deployment mode for security' with options 'quick start' or 'prod' should be displayed.

Screenshot:
image

@dikshachauhan-qasource dikshachauhan-qasource added the bug Fixes for quality problems that affect the customer experience label Jul 5, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 5, 2021
@dikshachauhan-qasource dikshachauhan-qasource added the Team:Fleet Team label for Observability Data Collection Fleet team label Jul 5, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 5, 2021
@dikshachauhan-qasource dikshachauhan-qasource added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Jul 5, 2021
@dikshachauhan-qasource
Copy link
Author

@manishgupta-qasource Please review

@manishgupta-qasource
Copy link

Reviewed & Assigned to @jen-huang

CC @EricDavisX

@jen-huang jen-huang changed the title On-prem Instructions for setting fleet-server displayed under add agent flyout on cloud deployments [Fleet] On-prem Instructions for setting fleet-server displayed under add agent flyout on cloud deployments Jul 6, 2021
@jen-huang
Copy link
Contributor

This is expected behavior. We allow users to add additional Fleet Servers on Cloud, if they wish, hence this showing when you have a policy with Fleet Server integration.

@dikshachauhan-qasource
Copy link
Author

Hi @jen-huang

Thanks for confirmation on above reported issue.

However, we have now come up with following queries.

  • How to provide certs under quick start and Prod option selected at step 3 in cloud environments. Could you please confirm if we need to use same steps as on self managed.

Thanks
QAS

@jen-huang
Copy link
Contributor

@dikshachauhan-qasource For quick start certs shouldn't be needed. For production, the commands generated in the following step has placeholder arguments for certs.

@amolnater-qasource
Copy link

Hi @jen-huang
Thanks for the feedback, could you please confirm do we need to follow the steps shared at https://github.com/elastic/observability-test-plans/issues/218 for production certs on cloud build too or it has some different steps for cloud certs generation?

Thanks

@jen-huang
Copy link
Contributor

@amolnater-qasource I think that should work.

@dikshachauhan-qasource
Copy link
Author

Hi @EricDavisX

We have created a testcase for above reported issue under bug conversion task .

Testcase link is : C149906

Thanks
QAS

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. Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

5 participants