# How is the agent upgrade availability is detected in fleet env (on-prem)

**URL:** <https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [March 7, 2024, 12:55pm UTC](https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956 "2024-03-07T12:55:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marfrarsi](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@marfrarsi](https://discuss.elastic.co/u/marfrarsi)\
**Post date:** [March 7, 2024, 12:55pm UTC](https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956/1 "2024-03-07T12:55:44Z")

</div>

Hello!  
Elastic 3 node Linux cluster on prem, with some Elastic Agent managed by a fleet server.  
I've upgraded the whole stack from 8.11.3 to 8.12 (Elasticsearch, kibana and fleet server). Now I would like to upgrade all the agents but the update to 8.12 is not proposed in Kibana gui under the Fleet management panel. and the "upgrade agent" option is greyed out.

 ![elastic-fleet](https://us1.discourse-cdn.com/elastic/original/3X/0/f/0f82255269442bd5d341e5882c49f8e16c4e3903.jpeg)

My env is air-gaped, so I use my own binary repository (updated with latest agent packages and set up in fleet policy) and if I try to manually upgrade via command line an Agent it upgrades successfully (with command: /opt/Elastic/Agent/elastic-agent upgrade 8.12.0

Looking for somebody with the same problem here, I've found and followed this guide thinking my problem could be this one:  
[Fleet and Elastic Agent 8.12.1 | Fleet and Elastic Agent Guide [8.12] | Elastic](https://www.elastic.co/guide/en/fleet/current/release-notes-8.12.1.html#known-issue-3263-8121))

But nothing changes.

So, does somebody know how the Fleet UI understand that a new Agent version is available and propose the upgrade? Is this an operation done by Fleet server or Kibana?

Thank you for the support!

Marco

---

<div class="post-metadata">

**Author:** ![marfrarsi](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@marfrarsi](https://discuss.elastic.co/u/marfrarsi)\
**Post date:** [March 7, 2024, 3:41pm UTC](https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956/2 "2024-03-07T15:41:03Z")

</div>

Well, I reply to myself..  
I've updated Kibana from 8.12.0 to 8.12.2 and now the problem disappear.

Probably a bug in Kibana 8.12.0

---

<div class="post-metadata">

**Author:** ![Julia\_Bardi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julia_bardi/32/79463_2.png) [@Julia\_Bardi](https://discuss.elastic.co/u/Julia_Bardi)\
**Post date:** [March 25, 2024, 2:05pm UTC](https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956/3 "2024-03-25T14:05:21Z")

</div>

Hi Marco, welcome to the community!

Yes, this seems to be the known issue in 8.12.0 and 8.12.1 that you linked.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 22, 2024, 2:05pm UTC](https://discuss.elastic.co/t/how-is-the-agent-upgrade-availability-is-detected-in-fleet-env-on-prem/354956/4 "2024-04-22T14:05:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.