{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/helm/issues/1996","repository_url":"https://api.github.com/repos/kubernetes/helm","labels_url":"https://api.github.com/repos/kubernetes/helm/issues/1996/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/helm/issues/1996/comments","events_url":"https://api.github.com/repos/kubernetes/helm/issues/1996/events","html_url":"https://github.com/kubernetes/helm/issues/1996","id":208682866,"number":1996,"title":"`release: not found` when I do `helm install` on a chart with some weird properties","user":{"login":"iameli","id":257909,"avatar_url":"https://avatars2.githubusercontent.com/u/257909?v=4","gravatar_id":"","url":"https://api.github.com/users/iameli","html_url":"https://github.com/iameli","followers_url":"https://api.github.com/users/iameli/followers","following_url":"https://api.github.com/users/iameli/following{/other_user}","gists_url":"https://api.github.com/users/iameli/gists{/gist_id}","starred_url":"https://api.github.com/users/iameli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iameli/subscriptions","organizations_url":"https://api.github.com/users/iameli/orgs","repos_url":"https://api.github.com/users/iameli/repos","events_url":"https://api.github.com/users/iameli/events{/privacy}","received_events_url":"https://api.github.com/users/iameli/received_events","type":"User","site_admin":false},"labels":[{"id":269212351,"url":"https://api.github.com/repos/kubernetes/helm/labels/bug","name":"bug","color":"fc2929","default":true},{"id":427152958,"url":"https://api.github.com/repos/kubernetes/helm/labels/starter","name":"starter","color":"d4c5f9","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2017-02-19T00:26:30Z","updated_at":"2018-05-12T21:59:49Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Came across this while doing some mad science on directories that are both Helm charts and Javascript modules. [Minimal repro case is here](https://github.com/streamplace/weird-chart-bug). The end result is that Helm successfully deploys a chart and immediately forgets that it did, like so:\r\n\r\n```\r\n> helm install --name test .\r\nNAME:   test\r\nError: getting deployed release \"test\": release: not found\r\n```\r\n\r\nIt does actually create the relevant Deployment object, but it doesn't know anything about the `test` release. I have to manually go in and delete the Deployment with `kubectl`.\r\n\r\nI'm sure the problem is related to the `node_modules` directory -- it contains a zillion files and directories for all of my Javascript dependencies. Potentially I'm exceeding some hidden limit for files allowed within a Helm chart? Obviously I should be putting `node_modules` in `.helmignore`, but presumably Helm should also be doing something more coherent upon this failure case."},"comment":{"url":"https://api.github.com/repos/kubernetes/helm/issues/comments/388586207","html_url":"https://github.com/kubernetes/helm/issues/1996#issuecomment-388586207","issue_url":"https://api.github.com/repos/kubernetes/helm/issues/1996","id":388586207,"user":{"login":"fejta-bot","id":30488982,"avatar_url":"https://avatars1.githubusercontent.com/u/30488982?v=4","gravatar_id":"","url":"https://api.github.com/users/fejta-bot","html_url":"https://github.com/fejta-bot","followers_url":"https://api.github.com/users/fejta-bot/followers","following_url":"https://api.github.com/users/fejta-bot/following{/other_user}","gists_url":"https://api.github.com/users/fejta-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/fejta-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fejta-bot/subscriptions","organizations_url":"https://api.github.com/users/fejta-bot/orgs","repos_url":"https://api.github.com/users/fejta-bot/repos","events_url":"https://api.github.com/users/fejta-bot/events{/privacy}","received_events_url":"https://api.github.com/users/fejta-bot/received_events","type":"User","site_admin":false},"created_at":"2018-05-12T21:59:49Z","updated_at":"2018-05-12T21:59:49Z","author_association":"NONE","body":"Issues go stale after 90d of inactivity.\nMark the issue as fresh with `/remove-lifecycle stale`.\nStale issues rot after an additional 30d of inactivity and eventually close.\n\nIf this issue is safe to close now please do so with `/close`.\n\nSend feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n/lifecycle stale"}}
{"actor":{"display_login":"fejta-bot"}}