Closed llorllale closed 4 years ago
I declared some dependencies on the fixtures (set dependency on the relevant storage container for each agent) and also increased the Go BDD test timeout to 30... still sometimes seeing this error:
Scenario: did exchange e2e flow using controller api # features/didexchange_e2e_controller.feature:12
Given "Alice" agent is running on "localhost" port "8081" with controller "https://localhost:8082" # features/didexchange_e2e_controller.feature:13
Error: Get "https://localhost:8082": dial tcp 127.0.0.1:8082: connect: connection refused
And yet:
$ docker ps | grep alice.agent.example.com
$
$ docker logs alice.agent.example.com
Error: No such container: alice.agent.example.com
$
Ah - the container does exist - I need to search with the container_name
:
$ docker logs -f alice.aries.example.com
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
WARNING: ca-cert-ec-key.csr.pem does not contain exactly one certificate or CRL: skipping
WARNING: ca-cert-ec-cacert.srl.pem does not contain exactly one certificate or CRL: skipping
Error: failed to start aries agent rest on port [0.0.0.0:8082], failed to initialize framework : default option initialization failed: can't initialize verifaible store : failed to open vc store: failed to create db: Unauthorized: You are not a server admin.
....
excerpt from couchdb logs:
There's the 401
while attempting to create Alice's verifiable store.
Calling the _session
endpoint is not enough:
Querying _users
was not enough... seems CouchDB sometimes can't create it?
None of the agent databases were created in this run.
This bug is a bit hard to reproduce on my local setup.. however, it's ocurring in CI relatively frequently.
See this build log: https://github.com/hyperledger/aries-framework-go/runs/1101967510
Notes:
mem
storage