You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the changes from above mentioned PR it is no longer possible to update the cluster license if the currently installed license has already expired because the reachability criterion relies on a successful health observation:
We need to distinguish the two criteria (service has endpoints and health API responds).
However it seems with expired license health observations are no longer possible as the health API is blocked in the degraded state Elasticsearch enters into when the license expires.
One potential fix for this issue is therefore only apply the first criteria (service has endpoints) when deciding whether to try the license API call or not.
Related #5796
With the changes from above mentioned PR it is no longer possible to update the cluster license if the currently installed license has already expired because the reachability criterion relies on a successful health observation:
https://github.com/elastic/cloud-on-k8s/blob/2.5/pkg/controller/elasticsearch/driver/driver.go#L243
We need to distinguish the two criteria (service has endpoints and health API responds).
However it seems with expired license health observations are no longer possible as the health API is blocked in the degraded state Elasticsearch enters into when the license expires.
One potential fix for this issue is therefore only apply the first criteria (service has endpoints) when deciding whether to try the license API call or not.
Workarounds:
$CLUSTER_NAME-es-license
viacurl
https://www.elastic.co/guide/en/elasticsearch/reference/current/update-license.html (that's all the operator does anyway)The text was updated successfully, but these errors were encountered: