# Fleet Elastic Agent Upgrade only partially available

**URL:** <https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093>\
**Category:** Kibana\
**Tags:** fleet\
**Created:** [February 26, 2024, 7:46am UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093 "2024-02-26T07:46:56Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\
**Post date:** [February 26, 2024, 7:46am UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/1 "2024-02-26T07:46:56Z")

</div>

After upgrading from 8.12.1 to 8.12.2, only 4 of my agents are displaying upgrade available (non of them are fleet-server).

Could this be due to the problem resolve of the other known issue or is this a new bug?

I know I could try upgrading them via API or manually, but I wanted to make sure nothing else might be broken.

Screenshot:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/9/f9c777a0b4eb78346484c26f0cc4227735e1660b.png)

---

<div class="post-metadata">

**Author:** ![MichelLaterman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michellaterman/32/110221_2.png) [@MichelLaterman](https://discuss.elastic.co/u/MichelLaterman)\
**Post date:** [March 4, 2024, 8:37am UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/2 "2024-03-04T08:37:43Z")

</div>

Is this a self-managed or a cloud cluster?  
Has Kibana been upgraded?  
Are the fleet-server instances running 8.12.2?

---

<div class="post-metadata">

**Author:** ![Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/balu/32/37569_2.png) [@Balu](https://discuss.elastic.co/u/Balu)\
**Post date:** [March 4, 2024, 9:28am UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/3 "2024-03-04T09:28:56Z")

</div>

I am having [the same issue](https://discuss.elastic.co/t/agents-upgradeable-or-not/354354) in a self-managed cluster.

Kibana has been updated, but I can't upgrade the fleet-server instances, because they are not shown as "Update available".

All agents are installed from tarballs and were able to be upgraded before.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [March 4, 2024, 12:09pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/4 "2024-03-04T12:09:25Z")

</div>

Is the Fleet Server on 8.12.2 as well?

There is a [know issue](https://www.elastic.co/guide/en/fleet/current/release-notes-8.12.1.html#known-issue-3263-8121) about this.

I had the same issue, I'm still on 8.12.1, but I've upgraded the Fleet Sever manually to 8.12.2 and it seems to have fixed this.

---

<div class="post-metadata">

**Author:** ![Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/balu/32/37569_2.png) [@Balu](https://discuss.elastic.co/u/Balu)\
**Post date:** [March 4, 2024, 1:12pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/5 "2024-03-04T13:12:13Z")

</div>

No. I wasn't able to upgrade the fleet-server because of that issue.

I avoided doing it manually to be able to figure out the issue, but I guess if it's already known I'll just do that.

That said - my agents are on 8.12.1, not 8.12.0?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [March 4, 2024, 1:23pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/6 "2024-03-04T13:23:13Z")

</div>

> [@Balu](#):
>
> That said - my agents are on 8.12.1, not 8.12.0?

The issue is still present on 8.12.1, it affects 8.12.0 and 8.12.1.

The linked issue also has a workaround, did you check it?

---

<div class="post-metadata">

**Author:** ![Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/balu/32/37569_2.png) [@Balu](https://discuss.elastic.co/u/Balu)\
**Post date:** [March 4, 2024, 2:44pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/7 "2024-03-04T14:44:29Z")

</div>

Yes. I've tried the workaround, but the `curl` command is just returning an `Empty reply from server` and the agents still don't want to be updated.

---

<div class="post-metadata">

**Author:** ![Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/balu/32/37569_2.png) [@Balu](https://discuss.elastic.co/u/Balu)\
**Post date:** [March 4, 2024, 3:02pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/8 "2024-03-04T15:02:26Z")

</div>

I have now upgraded the fleet-server manually with

```auto
/opt/Elastic/Agent/elastic-agent upgrade 8.12.2

```

which took longer than what felt right, but it looks that now all other agents seem to want to be upgraded too.

---

<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 1, 2024, 3:03pm UTC](https://discuss.elastic.co/t/fleet-elastic-agent-upgrade-only-partially-available/354093/9 "2024-04-01T15:03:15Z")

</div>

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