{"action":"created","issue":{"url":"https://api.github.com/repos/helm/charts/issues/7433","repository_url":"https://api.github.com/repos/helm/charts","labels_url":"https://api.github.com/repos/helm/charts/issues/7433/labels{/name}","comments_url":"https://api.github.com/repos/helm/charts/issues/7433/comments","events_url":"https://api.github.com/repos/helm/charts/issues/7433/events","html_url":"https://github.com/helm/charts/issues/7433","id":355372334,"node_id":"MDU6SXNzdWUzNTUzNzIzMzQ=","number":7433,"title":"[stable/cockroachdb] for single node cockroachdb, deleting the pod doesn't restore it into a working state","user":{"login":"prashant182","id":20832465,"node_id":"MDQ6VXNlcjIwODMyNDY1","avatar_url":"https://avatars1.githubusercontent.com/u/20832465?v=4","gravatar_id":"","url":"https://api.github.com/users/prashant182","html_url":"https://github.com/prashant182","followers_url":"https://api.github.com/users/prashant182/followers","following_url":"https://api.github.com/users/prashant182/following{/other_user}","gists_url":"https://api.github.com/users/prashant182/gists{/gist_id}","starred_url":"https://api.github.com/users/prashant182/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prashant182/subscriptions","organizations_url":"https://api.github.com/users/prashant182/orgs","repos_url":"https://api.github.com/users/prashant182/repos","events_url":"https://api.github.com/users/prashant182/events{/privacy}","received_events_url":"https://api.github.com/users/prashant182/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-08-29T23:42:30Z","updated_at":"2018-08-31T17:54:58Z","closed_at":null,"author_association":"NONE","body":"<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of-->\r\n\r\n**Is this a request for help?**:\r\nNO\r\n---\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?** (choose one):\r\nYES\r\n<!--\r\nIf this is a BUG REPORT, please:\r\n  - Fill in as much of the template below as you can.  If you leave out\r\n    information, we can't help you as well.\r\n\r\nIf this is a FEATURE REQUEST, please:\r\n  - Describe *in detail* the feature/behavior/change you'd like to see.\r\n\r\nIn both cases, be ready for followup questions, and please respond in a timely\r\nmanner.  If we can't reproduce a bug or think a feature already exists, we\r\nmight close your issue.  If we're wrong, PLEASE feel free to reopen it and\r\nexplain why.\r\n-->\r\nWhen you install the helm chart for replicas = 1, and then delete the running pod, it comes back up but with a readiness prob failed state and db doesn't work. \r\n**Version of Helm and Kubernetes**:\r\nhelm : 2.10\r\nk8s : 1.10\r\n\r\n**Which chart**:\r\nstable/cockroachdb\r\n\r\n**What happened**:\r\ndeleting for from statefulset breaks the cockroachdb\r\n\r\n**What you expected to happen**:\r\ncockroachdb can't restore itself.\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\n```helm install --name my-release stable/cockroachdb\r\nkubectl scale statefulset my-release-cockroachdb --replicas=1\r\nkubectl delete po my-release-cockroachdb-0  \r\n```\r\nwhich will start cockroachdb in failed state.\r\n```\r\nNAME                                    READY     STATUS      RESTARTS   AGE\r\nmy-release-cockroachdb-0            0/1       Running     0          5m\r\nmy-release-cockroachdb-init-6t5q6   0/1       Completed   0          15m\r\n```\r\n** anything else we should know about ** \r\nlogs \r\n```I180829 23:38:26.852352 16443 gossip/client.go:134  [n1] closing client to node 1 (my-release-cockroachdb-0.my-release-cockroachdb:26257): stopping outgoing client to node 1 (my-release-cockroachdb-0.my-release-cockroachdb:26257); loopback connection\r\nW180829 23:38:27.086169 152 sql/jobs/registry.go:286  unable to get node liveness: node not in the liveness table\r\nW180829 23:38:27.433420 117 storage/store.go:1463  [n1,s1,r7/1:/Table/{SystemCon…-11}] could not gossip system config: [NotLeaseHolderError] r7: replica (n1,s1):1 not lease holder; lease holder unknown\r\nI180829 23:38:27.952348 16476 gossip/client.go:129  [n1] started gossip client to my-release-cockroachdb-0.my-release-cockroachdb:26257\r\nI180829 23:38:27.952917 16476 gossip/client.go:134  [n1] closing client to node 1 (my-release-cockroachdb-0.my-release-cockroachdb:26257): stopping outgoing client to node 1 (my-release-cockroachdb-0.my-release-cockroachdb:26257); loopback connection\r\nW180829 23:38:28.466634 117 storage/store.go:1463  [n1,s1,r7/1:/Table/{SystemCon…-11}] could not gossip system config: [NotLeaseHolderError] r7: replica (n1,s1):1 not lease holder; lease holder unknown\r\n```\r\nAnd \r\n\r\n`kubectl describe po my-release-cockroachdb-0`\r\n\r\n logs \r\n```\r\n    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)\r\n    ClaimName:  datadir-my-release-cockroachdb-0\r\n    ReadOnly:   false\r\n  default-token-dx7d8:\r\n    Type:        Secret (a volume populated by a Secret)\r\n    SecretName:  default-token-dx7d8\r\n    Optional:    false\r\nQoS Class:       BestEffort\r\nNode-Selectors:  <none>\r\nTolerations:     node.kubernetes.io/not-ready:NoExecute for 300s\r\n                 node.kubernetes.io/unreachable:NoExecute for 300s\r\nEvents:\r\n  Type     Reason                 Age               From               Message\r\n  ----     ------                 ----              ----               -------\r\n  Normal   Scheduled              8m                default-scheduler  Successfully assigned my-release-cockroachdb-0 to minikube\r\n  Normal   SuccessfulMountVolume  8m                kubelet, minikube  MountVolume.SetUp succeeded for volume \"pvc-54d81355-abe2-11e8-819b-080027096c35\"\r\n  Normal   SuccessfulMountVolume  8m                kubelet, minikube  MountVolume.SetUp succeeded for volume \"default-token-dx7d8\"\r\n  Normal   Pulling                8m                kubelet, minikube  pulling image \"cockroachdb/cockroach:v2.0.5\"\r\n  Normal   Pulled                 8m                kubelet, minikube  Successfully pulled image \"cockroachdb/cockroach:v2.0.5\"\r\n  Normal   Created                8m                kubelet, minikube  Created container\r\n  Normal   Started                8m                kubelet, minikube  Started container\r\n  Warning  Unhealthy              3m (x58 over 7m)  kubelet, minikube  Readiness probe failed: HTTP probe failed with statuscode: 500```"},"comment":{"url":"https://api.github.com/repos/helm/charts/issues/comments/417743052","html_url":"https://github.com/helm/charts/issues/7433#issuecomment-417743052","issue_url":"https://api.github.com/repos/helm/charts/issues/7433","id":417743052,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNzc0MzA1Mg==","user":{"login":"prashant182","id":20832465,"node_id":"MDQ6VXNlcjIwODMyNDY1","avatar_url":"https://avatars1.githubusercontent.com/u/20832465?v=4","gravatar_id":"","url":"https://api.github.com/users/prashant182","html_url":"https://github.com/prashant182","followers_url":"https://api.github.com/users/prashant182/followers","following_url":"https://api.github.com/users/prashant182/following{/other_user}","gists_url":"https://api.github.com/users/prashant182/gists{/gist_id}","starred_url":"https://api.github.com/users/prashant182/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prashant182/subscriptions","organizations_url":"https://api.github.com/users/prashant182/orgs","repos_url":"https://api.github.com/users/prashant182/repos","events_url":"https://api.github.com/users/prashant182/events{/privacy}","received_events_url":"https://api.github.com/users/prashant182/received_events","type":"User","site_admin":false},"created_at":"2018-08-31T17:54:58Z","updated_at":"2018-08-31T17:54:58Z","author_association":"NONE","body":"An “air-gapped” environment is a network that has no path to inbound or outbound internet traffic at all. So in terms of support and installation, we can not assume things that rely on the internet such as timesync. I believe on cockraochdb official website, the recommended way is to use `server time1.google.com iburst` which might not be available for air-gapped environment, so we are not hitting all the points from your production checklist.  "}}
{"actor":{"display_login":"prashant182"}}