[Fleet] upgrade available not shown, agent 8.10.4, cloud 8.11.0

[leehinman]

Kibana Version: Cloud stack 8.11.0

Describe the bug:

Upgrade Agent isn't showing up for elastic-agents that are less than the stack version.

Steps to reproduce:

1. Cloud install 8.10.4
2. Agent Policy with System & Elastic Defend integrations
3. elastic-agent install at 8.10.4 (tested with Mac arm version)
4. upgrade cloud stack to 8.11.0
5. change Agent Binary Download to location of 8.11.0 BC artifacts

Expected behavior:

In UI, expect Upgrade Agent to be available.

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

running elastic-agent upgrade 8.11.0 from host works.

[belimawr]

I'm facing the same problem on Win x86_64. I managed to upgrade by calling the API from the Dev Console:

POST kbn:/api/fleet/agents/agent-id/upgrade
{
  "version": "8.11.0"
}

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[kpollich]

This is now expected behavior, see #167387 and #167410. Since agent 8.11 is not GA, the upgrade available option won't show up for it. You'll have to manually upgrade to the BC version using the API request that Tiago referenced above.

[brynjare]

Is the agent still not GA, or should we be able to upgrade through the UI now? An Elastic Cloud cluster running 8.11 still won't let me upgrade from 8.10.04 to 8.11 as of November 9th:

If this is the intended behaviour, when can we expect Elastic Agent to be available through the Kibana fleet management UI?

[kpollich]

@brynjare - Nope this is not expected at this point. We have a bug on our end that we're fixing in 8.11.1: #169825.

[brynjare]

Ah, I tried searching for relevant tickets but missed that one. Thanks for the quick confirmation and link to the appropriate issue, @kpollich - much appreciated!

[kpollich]

Hi folks, I'm following up on all the issues/threads where this was reported and tracked.

Due to 8.11.1 being pulled forward for an emergency release, this bugfix has missed the 8.11.1 build candidate window. The root cause fix in #170974 will be available in the 8.11.2 release scheduled for public availability on December 4th, 2023.

In the meantime, there is a documented workaround available in our support knowledge base here: https://support.elastic.co/knowledge/86bef2c1 (requires an Elastic Cloud login).