Skip to content

Features not matching version after an upgrade to 8.13+ #109254

@thbkrkr

Description

@thbkrkr

Elasticsearch Version

8.13.x

  • Java Version: bundled

  • OS Version: N/A (different k8s versions)

Problem Description

ECK operator 2.12.1 fails upgrading Elasticsearch 8.13+ as it is stalled on the following error when calling the desired nodes API:

400 Bad Request: {
    Reason: [node_version] field is required and must have a valid value 
    Type: x_content_parse_exception
    ...
}

Steps to Reproduce

The steps should be (not tested yet):

  • Deploy ECK 2.12.1+
  • Deploy Elasticsearch 8.11.x?
  • Upgrade to Elasticsearch 8.13+

Notes

Note: this is from ECK 2.12.1 that the operator stops to use the deprecated node_version field if the cluster is 8.13+:

Two occurences of this issue have been reported for these versions upgrades:

  • 8.11.x -> 8.13.3
  • 8.11.4 -> 8.13.2

Each time, the users confirmed that:

  • some nodes did not have desired_node.version_deprecated feature
  • a restart fixes the issue

Metadata

Metadata

Assignees

Labels

:Core/Infra/CoreCore issues without another label:Distributed/Cluster CoordinationCluster formation and cluster state publication, including cluster membership and fault detection.>bugTeam:Core/InfraMeta label for core/infra teamTeam:DistributedMeta label for distributed team.low-riskAn open issue or test failure that is a low risk to future releasesv8.13.0

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions