monasca-api unit tests fail with connection failure

Bug #1503861 reported by Bradley Klein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Monasca
Triaged
Low
Deklan Dieterly

Bug Description

One of the java unit tests for monasca-api is more a functional test -- and always fails assuming it can talk to influx it appears:

[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running monasca.api.integration.docker.ITInfluxDBTest
[INFO] Configuring TestNG with: TestNG652Configurator
[INFO] 20:20:33.897 [pool-1-thread-1] DEBUG c.g.d.client.command.AbstrDockerCmd - Cmd: pull monasca/api-integ-tests-kafka
[INFO] Oct 07, 2015 8:20:33 PM com.sun.jersey.api.client.filter.LoggingFilter log
[INFO] INFO: 1 * Client out-bound request
[INFO] 1 > POST http://192.168.59.103:2375/v1.13/images/create?tag=&registry=&fromImage=monasca/api-integ-tests-kafka
[INFO] 1 > Accept: application/octet-stream
[INFO]
[INFO] 20:20:34.118 [pool-1-thread-1] DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection request: [route: {}->http://192.168.59.103:2375][total kept alive: 0; route allocated: 0 of 1000; total allocated: 0 of 1000]
[INFO] 20:20:34.148 [pool-1-thread-1] DEBUG o.a.h.i.c.PoolingClientConnectionManager - Connection leased: [id: 0][route: {}->http://192.168.59.103:2375][total kept alive: 0; route allocated: 1 of 1000; total allocated: 1 of 1000]
[INFO] 20:20:34.156 [pool-1-thread-1] DEBUG o.a.h.i.c.DefaultClientConnectionOperator - Connecting to 192.168.59.103:2375

Allan G (greental)
Changed in monasca:
assignee: nobody → Deklan Dieterly (deklan)
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.