Connect Server API shows "Unable to find existing span for request" then "400: Bad Request" in logs

Chris137

I installed the connect server using ansible on an Ubuntu 20.04 cloud server using docker-compose. Everything seems ok, but when using Ansible to request an item Testlogin from the vault Tachyon, then no result gets back.

  - name: Find the item with the label "Testlogin" in the vault "Tachyon"
    onepassword.connect.item_info:
      vault: "Tachyon"
      item: "Testlogin"
    no_log: false
    register: op_item

  - ansible.builtin.debug:
      var: "{{ op_item }}"

This gives

TASK [Find the item with the label "Testlogin" in the vault "Tachyon"] *******************
ok: [hochhuth.point8.cloud]

TASK [ansible.builtin.debug] *************************************************************
ok: [hochhuth.point8.cloud] => {
    "<class 'dict'>": "VARIABLE IS NOT DEFINED!"
}

The API container log shows

{"log_message":"(I) GET /v1/vaults/Tachyon/items/Testlogin","timestamp":"2021-09-17T12:38:41.058357895Z","level":3,"scope":{"request_id":"7a4f69ea-c9a2-45b9-a5c7-657783246d95"}}
{"log_message":"(D) Unable to find existing span for request 7a4f69ea-c9a2-45b9-a5c7-657783246d95","timestamp":"2021-09-17T12:38:41.05841376Z","level":4,"scope":{"request_id":"7a4f69ea-c9a2-45b9-a5c7-657783246d95"}}
{"log_message":"(D) post-handler contenttype: ","timestamp":"2021-09-17T12:38:41.063112149Z","level":4,"scope":{"request_id":"7a4f69ea-c9a2-45b9-a5c7-657783246d95","jti":"jhmr3rdcogyomcal7lv27ck6tq"}}
{"log_message":"(D) setting auto-detected contenttype: application/json","timestamp":"2021-09-17T12:38:41.063209411Z","level":4,"scope":{"request_id":"7a4f69ea-c9a2-45b9-a5c7-657783246d95","jti":"jhmr3rdcogyomcal7lv27ck6tq"}}
{"log_message":"(I) GET /v1/vaults/Tachyon/items/Testlogin completed (400: Bad Request)","timestamp":"2021-09-17T12:38:41.063284181Z","level":3,"scope":{"request_id":"7a4f69ea-c9a2-45b9-a5c7-657783246d95","jti":"jhmr3rdcogyomcal7lv27ck6tq"}}
...

The Sync container log shows:

...
{"log_message":"(D) [discovery-local] potential peer found: 172.18.0.3","timestamp":"2021-09-17T12:46:08.713978708Z","level":4}
{"log_message":"(D) encountered duplicate connection, discarding","timestamp":"2021-09-17T12:46:08.714062524Z","level":4}
{"log_message":"(D) [transport-websocket] recieved message via 2af221af-59e3-4947-b34f-92d17b874185","timestamp":"2021-09-17T12:46:09.301599358Z","level":4}
{"log_message":"(D) received message  aaedb3a1-ea7b-4921-8467-3581744a2c83 from node 2af221af-59e3-4947-b34f-92d17b874185","timestamp":"2021-09-17T12:46:09.301688405Z","level":4}
{"log_message":"(D) [transport-websocket] recieved message via 2af221af-59e3-4947-b34f-92d17b874185","timestamp":"2021-09-17T12:46:09.320446907Z","level":4}
{"log_message":"(D) received message  4763d7b3-a844-4fed-a405-298d8082bc4d from node 2af221af-59e3-4947-b34f-92d17b874185","timestamp":"2021-09-17T12:46:09.32103709Z","level":4}
...

I already stumble over the encountered duplicate connection, discarding but have no idead what that means.

Thanks for any help and insights!

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

David_ag

Hey there! We're taking a look at this and will have an update soon. This looks like an error with how the module handles item lookup, but I'll let you know what we find.