{"action":"closed","issue":{"url":"https://api.github.com/repos/coreos/etcd-operator/issues/1223","repository_url":"https://api.github.com/repos/coreos/etcd-operator","labels_url":"https://api.github.com/repos/coreos/etcd-operator/issues/1223/labels{/name}","comments_url":"https://api.github.com/repos/coreos/etcd-operator/issues/1223/comments","events_url":"https://api.github.com/repos/coreos/etcd-operator/issues/1223/events","html_url":"https://github.com/coreos/etcd-operator/issues/1223","id":238983038,"number":1223,"title":"Sidecar backup fails to retain user data","user":{"login":"aaronyoungkash","id":23176093,"avatar_url":"https://avatars1.githubusercontent.com/u/23176093?v=3","gravatar_id":"","url":"https://api.github.com/users/aaronyoungkash","html_url":"https://github.com/aaronyoungkash","followers_url":"https://api.github.com/users/aaronyoungkash/followers","following_url":"https://api.github.com/users/aaronyoungkash/following{/other_user}","gists_url":"https://api.github.com/users/aaronyoungkash/gists{/gist_id}","starred_url":"https://api.github.com/users/aaronyoungkash/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aaronyoungkash/subscriptions","organizations_url":"https://api.github.com/users/aaronyoungkash/orgs","repos_url":"https://api.github.com/users/aaronyoungkash/repos","events_url":"https://api.github.com/users/aaronyoungkash/events{/privacy}","received_events_url":"https://api.github.com/users/aaronyoungkash/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-06-27T21:08:12Z","updated_at":"2017-06-27T21:09:57Z","closed_at":"2017-06-27T21:09:57Z","body":"Testing with operator 0.3.3 and cluster 3.1.9 we wanted to see what happens when deleting enough cluster pods to break quorum. What we found was the cluster recovered, but all our stored keys were gone. Is this the expected behaviour? If so how would one maintain user data via backups, or is that not possible?\r\n\r\nSteps to reproduce:\r\n\r\n- Create a key (etcdctl mk foo bar)\r\n- Triggered a sidecar backup via the sidecar /v1/backupnow endpoint\r\n- Delete 75% of the pods\r\n- Operator eventually brings up a new set of pods, which settles into a healthy cluster\r\n- The created key is gone (etcdctl get foo)\r\n\r\nThis is the cluster configuration yaml:\r\n\r\n```\r\napiVersion: \"etcd.coreos.com/v1beta1\"\r\nkind: \"Cluster\"\r\nmetadata:\r\n  name: \"etcd-cluster\"\r\nspec:\r\n  size: 7\r\n  version: \"3.1.9\"\r\n  backup:\r\n    backupIntervalInSecond: 300\r\n    maxBackups: 5\r\n    storageType: \"PersistentVolume\"\r\n    pv:\r\n      volumeSizeInMB: 512\r\n``` "}}
{"actor":{"display_login":"xiang90"}}