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]: User is unable to create agent policy from Default space to Space1. #203527

Closed
harshitgupta-qasource opened this issue Dec 10, 2024 · 4 comments · Fixed by #205925
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium 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

@harshitgupta-qasource
Copy link

Kibana Build details:

VERSION: 8.17.0 BC5
BUILD: 80495
COMMIT: 5c78fb5e4e9b5063bd83ae9bd1e5b32c63f5cc34

Host OS: All

Preconditions:

  1. 8.17.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. Create a new Agent Policy.
  4. Scroll down to the Spaces section and click the dropdown list.
  5. Remove the Default Space and assign Space1 to the policy.
  6. Then, create Agent Policy.
  7. Observe New agent policy is created.
  8. Navigate back to the Agent Policies tab.
  9. Select the newly created Policy.
  10. Observe that the assigned space (e.g., Space1) is not displayed; instead, only the Default Space (where the policy was created) is visible.

Screen Shot

  • On creating Agent Policy
    Image

  • After Creating Agent Policy
    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: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 Dec 10, 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.

@amolnater-qasource amolnater-qasource added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Dec 10, 2024
@nchaulet nchaulet self-assigned this Jan 8, 2025
@harshitgupta-qasource harshitgupta-qasource added the QA:Ready for Testing Code is merged and ready for QA to validate label Jan 13, 2025
@harshitgupta-qasource
Copy link
Author

Hi Team,

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

Observations:

  • User is able to create agent policy from Default space to Space1.

Build details:
VERSION: 8.18.0 SNAPSHOT
BUILD: 81812
COMMIT: f1a7a2d

Screen-cast:

Agent.policies.-.Fleet.-.Elastic.Mozilla.Firefox.2025-01-20.11-13-36.mp4

Hence, we are closing this issue and marking 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 Jan 20, 2025
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:medium Addressing this issue will have a medium 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