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] [Bug] If an agent is upgraded while in unhealthy state, its status is stuck at updating but the banner shows as unhealthy #122206

Closed
muskangulati-qasource opened this issue Jan 3, 2022 · 9 comments
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

@muskangulati-qasource
Copy link

Description:
If an agent is upgraded while in unhealthy state, its status is stuck at updating but the banner shows as unhealthy

Build Details:

Kibana version: 8.1.0 SNAPSHOT
Build: 49380
Commit: 87f753dba0515c23a1cc4bdf6feac2df2200baea
Artifact page: https://artifacts-api.elastic.co/v1/search/8.1.0-SNAPSHOT

Browser Details:
All

Preconditions:

  1. Kibana user should be logged in.
  2. Mac Agents with 8.0.0 artifacts should be installed on 8.1.0 and should be having unhealthy state

Steps to Reproduce:

  1. Navigate to the Fleet tab from the left hand side navigation
  2. Upgrade the unhealthy 8.0.0 agent to 8.1.0 and observe the color bar is not picking data for unhealthy while the banner shows unhealthy status for the agent

Impacted Test case:
N/A

Actual Result:
If an agent is upgraded while in unhealthy state, its status is stuck at updating but the banner shows as unhealthy

Expected Result:
If an agent is upgraded while in unhealthy state, its status should not get stuck at updating but the banner shows as unhealthy

What's working:
N/A

What's not working:
N/A

Screenshots:
Count Issue
Count Issue1

Logs:
N/A

@muskangulati-qasource muskangulati-qasource added 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. Team:Fleet Team label for Observability Data Collection Fleet team v8.1.0 labels Jan 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@muskangulati-qasource
Copy link
Author

@manishgupta-qasource please review!!

@manishgupta-qasource
Copy link

manishgupta-qasource commented Jan 3, 2022

Reviewed & mention to @mostlyjason

@mostlyjason
Copy link
Contributor

Thanks in our original requirements #75236, the updating status is supposed to supersede the unhealthy status. It seems this is not working as expected.

I believe this is a transitory issue since an agent would likely not remain in the updating state very long, assuming its online. The update should either succeed or fail within a few minutes.

I think we should fix this, but it seems like the impact is limited in time.

@ghost
Copy link

ghost commented Mar 23, 2022

Hi @mostlyjason,
We have tested this issue on the latest 8.2.0-snapshot build and observed that the issue is still reproducible. Please find below the testing details:

  • If an agent is upgraded while in unhealthy state, its status is stuck at updating but the banner shows as unhealthy.

Screenshots:
Screenshot (177)

Screenshot (176)

Build Details:
VERSION: 8.2.0-SNAPSHOT
BUILD: 51365
COMMIT: 130823a
ARTIFACT: https://snapshots.elastic.co/8.2.0-63942b4d/summary-8.2.0-SNAPSHOT.html

Thanks!

@criamico
Copy link
Contributor

Hi @samratbhadra-qasource, can I ask somebody from your team to test again this issue and let us know if it's still occurring?

This bug was last reported roughly one year ago and the elastic agent status has undergone many changes in the meantime, so I'm not sure that it's still valid.

@criamico
Copy link
Contributor

I'm closing as won't fix for now and reopen if it occurs again.

@criamico criamico closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2023
@amolnater-qasource
Copy link

Hi @criamico
We have revalidated this issue on latest 8.7.0 SNAPSHOT kibana cloud environment and found it fixed now.

Observations:

  • If an agent is upgraded while in unhealthy state, its status moves to updating state and the banner also shows as Updating.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2023-02-01.15-04-18.mp4

Build Details:
BUILD: 60262
COMMIT: 772d564

Hence we are marking this issue as QA:Validated.

Thanks

@amolnater-qasource amolnater-qasource added the QA:Validated Issue has been validated by QA label Feb 1, 2023
@criamico
Copy link
Contributor

criamico commented Feb 1, 2023

Thanks for your help @amolnater-qasource

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

No branches or pull requests

7 participants