{"action":"created","issue":{"url":"https://api.github.com/repos/travis-ci/dpl/issues/240","labels_url":"https://api.github.com/repos/travis-ci/dpl/issues/240/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/dpl/issues/240/comments","events_url":"https://api.github.com/repos/travis-ci/dpl/issues/240/events","html_url":"https://github.com/travis-ci/dpl/issues/240","id":64303578,"number":240,"title":"Login failed when deploying to deis","user":{"login":"jorihardman","id":99236,"avatar_url":"https://avatars.githubusercontent.com/u/99236?v=3","gravatar_id":"","url":"https://api.github.com/users/jorihardman","html_url":"https://github.com/jorihardman","followers_url":"https://api.github.com/users/jorihardman/followers","following_url":"https://api.github.com/users/jorihardman/following{/other_user}","gists_url":"https://api.github.com/users/jorihardman/gists{/gist_id}","starred_url":"https://api.github.com/users/jorihardman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jorihardman/subscriptions","organizations_url":"https://api.github.com/users/jorihardman/orgs","repos_url":"https://api.github.com/users/jorihardman/repos","events_url":"https://api.github.com/users/jorihardman/events{/privacy}","received_events_url":"https://api.github.com/users/jorihardman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-25T15:48:21Z","updated_at":"2015-04-02T00:03:10Z","closed_at":null,"body":"Hello,\r\n\r\nI realize that the deis deploy code hasn't changed since the last issue I submitted, and yet I've lost the ability to deploy.\r\n\r\nWhen trying to deploy I get the following messages:\r\n```\r\nNo stash found.\r\nLogin failed.\r\nfailed to deploy\r\n```\r\n\r\nTypically, when travis deploys, I can see the login in my deis controller logs. A failed login will look like this:\r\n```\r\nMar 24 15:59:31 deis-1 sh[2844]: 172.17.42.1 \"POST /v1/auth/login/ HTTP/1.0\" 400 68 \"python-requests/2.5.1 CPython/2.7.5 Darwin/13.4.0\"\r\n```\r\n\r\nHowever I get no logged auth attempts from travis. If I run the auth command manually from my machine:\r\n```\r\ndeis login deis.myiphere.xip.io --username=travis --password=mypasswordhere\r\n```\r\nI can login successfully. Is there any other way to debug this situation? This started happening around 5 days ago without me changing my deis cluster in any way or changing my travis.yml."},"comment":{"url":"https://api.github.com/repos/travis-ci/dpl/issues/comments/88670773","html_url":"https://github.com/travis-ci/dpl/issues/240#issuecomment-88670773","issue_url":"https://api.github.com/repos/travis-ci/dpl/issues/240","id":88670773,"user":{"login":"eMxyzptlk","id":87115,"avatar_url":"https://avatars.githubusercontent.com/u/87115?v=3","gravatar_id":"","url":"https://api.github.com/users/eMxyzptlk","html_url":"https://github.com/eMxyzptlk","followers_url":"https://api.github.com/users/eMxyzptlk/followers","following_url":"https://api.github.com/users/eMxyzptlk/following{/other_user}","gists_url":"https://api.github.com/users/eMxyzptlk/gists{/gist_id}","starred_url":"https://api.github.com/users/eMxyzptlk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eMxyzptlk/subscriptions","organizations_url":"https://api.github.com/users/eMxyzptlk/orgs","repos_url":"https://api.github.com/users/eMxyzptlk/repos","events_url":"https://api.github.com/users/eMxyzptlk/events{/privacy}","received_events_url":"https://api.github.com/users/eMxyzptlk/received_events","type":"User","site_admin":false},"created_at":"2015-04-02T00:03:10Z","updated_at":"2015-04-02T00:03:10Z","body":"Ok so I was able to debug this and workaround this issue (actually two issues):\r\n\r\n- DPL is installing `deis` through `pip install --user`. Pip installs the `deis` script into `$HOME/.local/bin` which is not in the PATH. Fix: In your `before_install` section of your .travis.yml, add `export PATH=\"$PATH:$HOME/.local/bin\"`\r\n- I was also hitting deis/deis#3285 worked around it by making the deployer an admin (bad bad idea, this should be fixed soon!)"}}