-
Notifications
You must be signed in to change notification settings - Fork 727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster UUID changed when upgrading single master 6.8.x to new nodeSet 7.3.x #2397
Comments
Logs from the 7.3.x instance:
Looks like it got |
From the operator logs:
It looks like we:
I think the operator zen2 algorithm is implicitly expecting 3 to happen before 2, and consider the cluster was not bootstrapped yet. Here the v6 to v7 upgrade happens before the operator notices the cluster has a UUID. Which is based on observed es state (every 10 seconds). |
Highlights from a discussion with @pebrc and @barkbay on Slack:
There are still 2 things we can improve here:
|
We got this in E2E tests: https://devops-ci.elastic.co/job/cloud-on-k8s-stack/148/testReport/github/com_elastic_cloud-on-k8s_test_e2e_es/Run_tests_for_different_ELK_stack_versions_in_GKE___7_4_2___TestVersionUpgradeSingleMaster68xToNewNodeSet73x_Cluster_UUID_should_have_been_preserved/
The text was updated successfully, but these errors were encountered: