[Fleet]: Upgraded Agent toast instead of Upgrading Agent when upgrade is triggered for lower version Agent.

[amolnater-qasource]

Kibana version: 7.16.0 Snapshot Kibana Cloud environment

Host OS and Browser version: All, All

Build details:

Build: 45625
Commit: 223397a5ed39a8ab66e369b9a97de4fc7be879e8

Preconditions:

1. 7.16.0 Snapshot Kibana Cloud environment should be available.
2. Lower version 7.15.1 agent must be installed using Default Policy.

Steps to reproduce:

1. Login to Kibana environment.
2. Navigate to Agents tab and trigger upgrade for Lower version Agent.
3. Observe Upgraded Agent toast instead of Upgrading Agent.

Impacted Testcase:
T719173

Expected Result:
Upgrading Agent toast should appear when upgrade is triggered for lower version Agent instead of Upgraded Agent.

• As agent is not completely upgraded and is in updating state, so toast shouldn't be Upgraded Agent.

Screenshot:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2021-10-29.14-35-16.mp4

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & mention to @jen-huang

CC: @EricDavisX

[jillguyonnet]

This was already resolved in #133138. The message has been additionally modified since then, the current version seems to be 'Upgrading agent(s)'.

[amolnater-qasource]

Hi Team,

We have revalidated this issue on latest 8.7.0 BC3 Kibana cloud environment and found it fixed now.

Observations:

• Upgrading Agent toast appears when upgrade is triggered for lower version Agent instead of Upgraded Agent.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2023-02-24.00-02-29.mp4

Build details:
BUILD: 60804
COMMIT: abbdcf4

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