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]: Confirmation flyout shows blank when all the policies are removed from the shared integration. #196796

Open
amolnater-qasource opened this issue Oct 18, 2024 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience good first issue low hanging fruit impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@amolnater-qasource
Copy link

Kibana Build details:

VERSION: 8.16.0-SNAPSHOT
BUILD: 79269
COMMIT: 574ec2fc5f383da6bff0d506cc6ab76803119dae

Preconditions:

  1. 8.16.0-SNAPSHOT Kibana cloud environment should be available.
  2. Shared integration should be installed in various policies.
  3. An agent should be installed.

Steps to reproduce:

  1. Navigate to Fleet>Agent policies tab.
  2. Select policy with which agent is installed and shared integration is there.
  3. Edit shared integration.
  4. Remove all the agent policies.
  5. Observe message in confirmation flyout: Fleet has detected that the selected agent policies, , are already in use by some of your agents. As a result of this action, Fleet will deploy updates to all agents that use these policies.

Expected Result:
Confirmation flyout should show appropriate message when all the policies are removed from the shared integration.

Screen Recording:

Agent.policy.3.-.Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2024-10-18.12-32-02.mp4

Feature:
#75867

@amolnater-qasource amolnater-qasource added bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Oct 18, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@amolnater-qasource
Copy link
Author

@muskangulati-qasource Please review.

@muskangulati-qasource
Copy link

Secondary review is Done for this ticket!

@kpollich kpollich added the good first issue low hanging fruit label Nov 11, 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 good first issue low hanging fruit impact:low Addressing this issue will have a low 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

4 participants