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
While a cluster was being upgraded in-place from 2.3.7 to 3.0.7, the first machine being upgraded was rebooted, restarting the v2 service. As the v3 and v2 services pointed to the same data directories, etcd2 failed to start.
After disabling the etcd2 service and starting etcd3, the cluster is failing to start with state-out-of-range errors:
We do not support cluster downgrade between minor versions. I do not think we should put a lot of effort to make this super safe in the near future. So closing.
While a cluster was being upgraded in-place from 2.3.7 to 3.0.7, the first machine being upgraded was rebooted, restarting the v2 service. As the v3 and v2 services pointed to the same data directories, etcd2 failed to start.
After disabling the etcd2 service and starting etcd3, the cluster is failing to start with state-out-of-range errors:
It would be good to have a mechanism in place to prevent this kind of corruption when downgrades occur, and instead just fail safely.
The text was updated successfully, but these errors were encountered: