Cap deploy fails with ERROR: Repository not found.

151 views
Skip to first unread message

niristotle okram

unread,
Jul 6, 2015, 5:11:46 PM7/6/15
to capis...@googlegroups.com
Versions:
  • Ruby : ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]
  • Capistrano : 'capistrano', '2.15.5'
Platform:
  • Working on.... RHEL 6.6
  • Deploying to... RHEL 6.6
Logs:
Hey guys, can you let me know why the cap2 is failing, when it tries to connect to the github? I can verify that it works i execute the commands manaully on the jenkins slaves (they does the deploy). I refer the http://capistranorb.com/documentation/getting-started/authentication-and-authorisation/

it appears that the capistrano is running the command as only: git ls-remote g...@github.com:Hewlett-PackardDevOps/ows-oss-test.git dev.. Rather than
deploy_user@serverX 'git ls-remote g...@github.com:Hewlett-PackardDevOps/ows-oss-test.git dev'
 

So executing this on the jenkins slave:

[jenkins@ip-10-0-0-90 ~]$ git ls-remote ssh://g...@github.com:some_name.git dev   
ssh: Could not resolve hostname github.com:some_name: Name or service not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


The above response/ERROR is what i have when executing the 'cap dev deploy' 

niristotle okram

unread,
Jul 7, 2015, 12:48:03 AM7/7/15
to capis...@googlegroups.com
turns out that i was using a same key pair for 2 different github accounts.
Reply all
Reply to author
Forward
0 new messages