CI Build is unable to connect to host

The https://ci.openmrs.org/browse/REFAPP-OMODDISTRO/latest build doesn’t get deployed the server due to error: 30-Jul-2015 07:58:10 Failed to connect to host

30-Jul-2015 07:58:10
net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods



30-Jul-2015 07:58:10
        at net.schmizz.sshj.userauth.UserAuthImpl.authenticate(UserAuthImpl.java:114)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.SSHClient.auth(SSHClient.java:205)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:305)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.plugins.scp.ScpTask.execute(ScpTask.java:261)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.plugins.scp.ScpTask.run(ScpTask.java:116)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.plugins.scp.ScpTask.execute(ScpTask.java:94)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:216)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.task.TaskExecutorImpl.execute(TaskExecutorImpl.java:98)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:75)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:188)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:112)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:110)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20)



30-Jul-2015 07:58:10
        at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52)



30-Jul-2015 07:58:10
        at java.lang.Thread.run(Thread.java:745)



30-Jul-2015 07:58:10
Caused by: net.schmizz.sshj.userauth.UserAuthException: publickey auth failed



30-Jul-2015 07:58:10
        at net.schmizz.sshj.userauth.UserAuthImpl.handle(UserAuthImpl.java:157)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.transport.TransportImpl.handle(TransportImpl.java:474)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.transport.Decoder.decode(Decoder.java:127)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.transport.Decoder.received(Decoder.java:195)



30-Jul-2015 07:58:10
        at net.schmizz.sshj.transport.Reader.run(Reader.java:72)
Does anyone know what is going on and is able to fix it?

Give me half an hour and I will take a look

I suppose that 13 hours ago @ryan changed the keys on the Bamboo agents. Apparently the access using the old key was revoked too, not sure if in all the servers, but at least in devtest01.

But there are quite a few Bamboo builds around using the old key.

So I’m replacing that task:

by a script like:

scp openmrs-${bamboo.maven.release.version}.${bamboo.buildNumber}.deb bamboo@devtest01.openmrs.org:/tmp/

whenever I find it.

1 Like

I can see that the problem disappeared, Thanks, @cintiadr!!

Yes all testing servers should be using the new key. I forgot about the scp task where it stores the private key instead of using the one on the box.

If anyone else finds a plan failing for a similar reason, let us know.

1 Like

@tmueller do you have any thoughts on this? https://ci.openmrs.org/browse/REFAPP-OMODDISTRO/history

I asked @tmueller to ignore tests until they are stable and green. He’s on vacation right now so I’ll ignore those which are failing.

Hi, I’m back. @dkayiwa, could you please clarify what you wanted to ask me about ?

@tmueller, did you check out the link i sent?

I noticed it’s a link to the CI build history, but after first look I wasn’t sure which point of the history were you referring to. than I noticed the long history of failing build…

I can point out few reasons of these failures:

“HTTP 500 Internal Server Error” happening when running REST operations in tests (Has something been changed in REST implementation?)

Number of apps visible from HomePage has changed(has something new been added?). This affects tests: AddRolesToUserTest and LoginTest which check number of apps visible for user.

A new error:

@tmueller can we disable/ignore all these failing tests until when they will pass again?

Yeah, but, for the future, if someone sets a test to ignore, he/she should add a short comment why the test was ignored. It’ll help to notify which tests to unignore when a failure reason will be fixed

2 Likes