etcd snapshot default keys-version should be v3
Bug #1840933 reported by
Mike Wilson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Etcd Charm |
Fix Released
|
Medium
|
Robert Gildein |
Bug Description
etcd snapshots aren't saving Kubernetes data now that Kubernetes data is in a namespace.
12:51:12 <jk0ne> I was trying to do an upgrade, and etcd came back with 0 active peers (and apparently no data)
12:51:39 <jk0ne> I've tried to restore the data (I did make a snapshot) but I can't make it go.
14:14:51 <jk0ne> Here's where I'm at now. I've managed to restore the snapshot and get one etcd working.
14:15:18 <jk0ne> Unfortunately, the snapshot seems to have not restored the kubernetes data stored in etcd (all pods / deployments / etc. lost)
14:15:54 <jk0ne> (the snapshot doesn't include member/snap/db)
Changed in charm-etcd: | |
status: | Triaged → In Progress |
assignee: | nobody → Robert Gildein (rgildein) |
Changed in charm-etcd: | |
milestone: | none → 1.20+ck1 |
tags: | added: backport-needed |
Changed in charm-etcd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Was the snapshot action run with keys-version=v3 ?