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 unassigning the Default Space from Agent Policy, Fleet server gets removed #192545

Closed
harshitgupta-qasource opened this issue Sep 11, 2024 · 5 comments · Fixed by #198175
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:critical This issue should be addressed immediately due to a critical level of impact on the product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@harshitgupta-qasource
Copy link

Kibana Build details:

VERSION: 8.16.0
BUILD: 78156
COMMIT: 6ef9f6c640a86180e92945b1e729ab11709cad3b

Host OS: All

Preconditions:

  1. 8.16.0 or above Kibana should be available.
  2. Agent Policy should be created.
  3. Two or more space should be created.

Steps to reproduce:

  1. Log in to the Default Space.
  2. Navigate to Agents Tab > Agent Policies Tab.
  3. Select any agent policy and go to Settings.
  4. Scroll down to the Spaces section and click the dropdown list.
  5. Verify that all created spaces are listed in the dropdown.
  6. Select all spaces and unassign the Default Space.
  7. Observe that when the Default Space is unassigned from the Agent Policy, the Fleet server is removed.

Expected Result:

  • On unassigning the Default Space from an Agent Policy, the Fleet server should not be removed.

Screen-cast

Fleet.server.gets.removed.mp4

Screen Shot
Image

Feature:
https://github.com/elastic/ingest-dev/issues/1664

@harshitgupta-qasource harshitgupta-qasource added bug Fixes for quality problems that affect the customer experience impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:Fleet Team label for Observability Data Collection Fleet team labels Sep 11, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@harshitgupta-qasource
Copy link
Author

@amolnater-qasource Kindly review

@amolnater-qasource
Copy link

Secondary Review for this ticket is Done.

@nchaulet nchaulet self-assigned this Oct 28, 2024
@nchaulet
Copy link
Member

Looks like we missed the search in those updatedByQuery https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/server/services/spaces/agent_policy.ts#L118 I will fix that and add missing tests

@harshitgupta-qasource
Copy link
Author

Hi Team,

We have re-validated this issue on the latest 8.17.0 Kibana cloud environment and found it fixed now.

Observations:

  • User is not able to change the Default Space of "Elastic Cloud Agent Policy" because of that Fleet server not get removed

Build details:
VERSION: 8.17.0 BC5
BUILD: 80495
COMMIT: 5c78fb5

Screen-cast:

Agents.-.Fleet.-.Elastic.Mozilla.Firefox.2024-12-10.14-30-21.mp4

Hence, we are marking this issue as QA: Validated.

Thanks

@harshitgupta-qasource harshitgupta-qasource added QA:Validated Issue has been validated by QA and removed QA:Ready for Testing Code is merged and ready for QA to validate labels Dec 10, 2024
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:critical This issue should be addressed immediately due to a critical level of impact on the 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