How to handle irrelevant v2 custom content when upgrading to 3.6 of etcd #20231
-
|
Recently I've been trying to upgrade some etcd instances to 3.6 and I'm running into an error: "msg":"illegal v2store content","error":"detected disallowed custom content in v2store" Now we may have some old v2 custom content, but we migrated a long time ago to v3 and it might just been hanging around doing nothing. My question is how do we get etcd to ignore or remove this custom content when upgrading to 3.6? I've tried using the flag: Perhaps our original migration process was invalid, however all the data is so old that it's truely irrelevant now. Any guidance would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 40 replies
-
|
I have exactly the same issue. I even restarted the cluster with V2 enabled to identify any old V2 data, then deleted the old data.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @Timothy-Dougherty & @lukasertl - Thanks for your question. If you have a testing environment available, try starting the 3.5.x cluster with v2 enabled you can then try running What is the output from @ahrtr Do you have any further ideas on what steps to run here? |
Beta Was this translation helpful? Give feedback.
-
Did you remove the flag |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ahrtr - I've shared my snap-file with you. Can you work with this? |
Beta Was this translation helpful? Give feedback.
So it finally worked with this steps:
--snapshot-count=1and the flag--enable-v2so i can delete the userauth: Cannot modify role root: is root role)--enable-v2and restore the previous value of--snapshot-count