[Fleet]: On Updating The Agent Binary, Pop-up Also Includes Count For Elastic Cloud Agent Policy And Hosted Agent.

by ADMIN 115 views

Fleet: On updating the Agent Binary, pop-up also includes count for Elastic Cloud agent policy and hosted agent

In the latest version of Fleet, updating the Agent Binary has been made more efficient with the inclusion of a pop-up that displays the count for Elastic Cloud agent policy and hosted agent. This feature is designed to provide users with a clear understanding of the impact of updating the Agent Binary on their Elastic Cloud agent policy and hosted agents. However, there have been reports of unexpected behavior, where the pop-up also includes the count for Elastic Cloud agent policy and hosted agent, which is not the expected result. In this article, we will delve into the details of this issue, explore the preconditions, steps to reproduce, and expected results, and provide a screen-shot and screen-cast for further reference.

Before we dive into the issue, let's take a look at the Kibana build details:

  • VERSION: 9.1.0-SNAPSHOT
  • BUILD: 85761
  • COMMIT: 7eb727410a752183253273df72ba55ff822cd543

To reproduce this issue, the following preconditions must be met:

  1. Kibana Version: The Kibana version should be 9.1.0 or above.
  2. Agent Policy: An Agent Policy should be created.
  3. Agent Installation: The Agent should be installed.

To reproduce this issue, follow these steps:

  1. Navigate to Fleet > Settings Tab: Navigate to the Fleet settings tab.
  2. Scroll down to Agent Binary: Scroll down to the Agent Binary section.
  3. Click the Action Button: Click the Action button next to the Agent Binary.
  4. Update the Elastic Artifacts: Update the Elastic Artifacts.
  5. Observe the Pop-up: Observe the pop-up that appears after updating the Agent Binary.

The expected results are:

  • Pop-up Should Not Include Count: On updating the Agent Binary, the pop-up should not include the count for Elastic Cloud agent policy and hosted agent.
  • Changes Should Not Be Reflected: On adding a new binary and setting it to default, changes should not be reflected in the Elastic Cloud agent policy.

It's worth noting that on adding a new binary and setting it to default, changes are also reflected in the Elastic Cloud agent policy.

For further reference, a screen-shot of the issue is provided:

Image

A screen-cast of the issue is also available:

https://github.com/user-attachments/assets/cd12ca9c-f5a9-4367-97f9-d9a3b2ddc57e

In conclusion, updating the Agent Binary in Fleet has been made more efficient with the inclusion of a pop-up that displays the count for Elastic Cloud agent policy and hosted agent. However, there have been reports of unexpected behavior, where the pop-up also includes the count for Elastic Cloud agent policy and hosted agent. By following the steps to reproduce and observing the expected results, users can identify and report this issue to the Elastic team. The screen-shot and screen-cast provided in this article will serve as a reference for further investigation and resolution of this issue.

Based on the analysis of this issue, the following recommendations are made:

  • Update Kibana Version: Ensure that the Kibana version is 9.1.0 or above.
  • Verify Agent Policy: Verify that an Agent Policy has been created.
  • Check Agent Installation: Check that the Agent has been installed.
  • Report Issue: Report this issue to the Elastic team for further investigation and resolution.

By following these recommendations, users can ensure that their Fleet setup is up-to-date and functioning as expected.
Fleet: On updating the Agent Binary, pop-up also includes count for Elastic Cloud agent policy and hosted agent - Q&A

In our previous article, we explored the issue of the pop-up including the count for Elastic Cloud agent policy and hosted agent when updating the Agent Binary in Fleet. In this article, we will provide a Q&A section to address some of the frequently asked questions related to this issue.

A: The expected behavior is that the pop-up should not include the count for Elastic Cloud agent policy and hosted agent when updating the Agent Binary.

A: The pop-up is including the count for Elastic Cloud agent policy and hosted agent because of a bug in the Fleet setup. This bug is causing the pop-up to display the count for Elastic Cloud agent policy and hosted agent even when it should not.

A: To verify that the Agent Policy has been created, follow these steps:

  1. Navigate to the Fleet settings tab.
  2. Click on the Agent Policy tab.
  3. Verify that the Agent Policy has been created and is listed in the table.

A: The preconditions for reproducing this issue are:

  1. Kibana version 9.1.0 or above.
  2. Agent Policy created.
  3. Agent installed.

A: To report this issue to the Elastic team, follow these steps:

  1. Go to the Elastic support portal.
  2. Click on the "Create a new issue" button.
  3. Fill in the issue details, including the steps to reproduce the issue and any relevant screenshots or screen casts.
  4. Submit the issue for review.

A: The recommended steps to resolve this issue are:

  1. Update the Kibana version to 9.1.0 or above.
  2. Verify that the Agent Policy has been created.
  3. Check that the Agent has been installed.
  4. Report the issue to the Elastic team for further investigation and resolution.

A: It is not recommended to use the Fleet setup with this issue. The issue is causing unexpected behavior and may lead to errors or data loss. It is recommended to wait for the issue to be resolved by the Elastic team before using the Fleet setup.

In conclusion, the Q&A section provides answers to some of the frequently asked questions related to the issue of the pop-up including the count for Elastic Cloud agent policy and hosted agent when updating the Agent Binary in Fleet. By following the recommended steps to resolve this issue, users can ensure that their Fleet setup is up-to-date and functioning as expected.

Based on the analysis of this issue, the following recommendations are made:

  • Update Kibana Version: Ensure that Kibana version is 9.1.0 or above.
  • Verify Agent Policy: Verify that an Agent Policy has been created.
  • Check Agent Installation: Check that the Agent has been installed.
  • Report Issue: Report this issue to the Elastic team for further investigation and resolution.

By following these recommendations, users can ensure that their Fleet setup is up-to-date and functioning as expected.