-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Etcd Upgrade Fails When Persistent Storage Flag is Disabled #78398
Comments
this is fixed function. is_new_etcd_cluster() {
local -a extra_flags
read -r -a extra_flags <<< "$(etcdctl_auth_flags)"
is_boolean_yes "$ETCD_ON_K8S" && extra_flags+=("--endpoints=$(etcdctl_get_endpoints true)")
! debug_execute etcdctl endpoint status --cluster "${extra_flags[@]}"
} |
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
@saurabhnetskope please check upgrading notes on latest release:
|
@juan131 helm upgrade is not working when persistent storage is disabled. |
Could you please provide the chart parameters (provided via |
Using 3.5.18-debian-12-r0 through 3.5.19-debian-12-r0, we're seeing this problem. The initial cluster setup works, but after it transitions from
|
@alop what chart version are you upgrading from and to? |
@juan131 No chart upgrade - using 9.8.1 - simply updating the image tag passed in from |
On image version If you want to upgrade to |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/etcd:3.5.18
What architecture are you using?
amd64
What steps will reproduce the bug?
Description:
We are running a 3-pod etcd cluster without persistent storage, relying on
emptyDir
. However, after the recent change introduced in commit 1aff4e2, the etcd upgrade is failing.Steps to Reproduce:
emptyDir
used instead).Root Cause:
The issue lies in the
is_new_etcd_cluster
function. To determine if the cluster is new or existing, this function executes:During a rolling upgrade, not all endpoints will be responsive. When
etcdctl_get_endpoints
includes its own endpoint, the command:fails, leading to the upgrade issue.
Proposed Fix:
Modify
etcdctl_get_endpoints
to exclude the pod's own endpoint before executingetcdctl endpoint status --cluster
. This will prevent failures when checking the cluster status during a rolling upgrade.Expected Behavior:
The etcd cluster should successfully upgrade even when persistent storage is disabled, allowing rolling upgrades to complete without failure.
Environment Details:
emptyDir
What is the expected behavior?
The etcd cluster should successfully upgrade even when persistent storage is disabled, allowing rolling upgrades to complete without failure.
What do you see instead?
emptyDir
for ephemeral etcd storage.The text was updated successfully, but these errors were encountered: