-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(E) 400: Invalid Item UUID #132
Comments
I've had a second look at our logs and it looks like the error is logged every time the connect-api container fetches a secret by name from 1password. The secret is fetched successfully, but there's always an error message like this
|
Found a similar issue in 1Password/connect repo, linked it above |
This happens to me as well, We also get errors from op CLI with: [ERROR] 2023/01/09 19:52:24 could not read secret op://xxx/credential: could not retrieve vaults: Get "*****************************************/v1/vaults": dial tcp: lookup op-connect.xxx.xxx on 127.0.0.11:53: server misbehaving Not sure it's related, but it seems the connect server is not stable. Any idea? |
This happens to us as well, a lot of "(E) 400: Invalid Item UUID" logs on our PRD cluster |
Hey all. Thank you for raising this. It looks like the issue is rather related to Connect than the operator. |
@edif2008 , I believe that this is an error in the interaction of Operator with OP Connect. Operator needs to have a different path for injecting by Title - so you can do the proper API call to connect. When using TITLE in the path for a OnePasswordItem, the operator is sending a request passing the title as the ID and not finding it, then querying on the title filter.. This causes constant spamming of bad requests to Connect. The log spam in Connect is misuse of the API by Operator. When I reference items by ID, the log spamming stops, but when I reference by title it continually dumps these errors (even though the secret creation is successful and correct). |
Your environment
Operator Version: 1.5.0
Connect Server Version: 1.5.6
Kubernetes Version: 1.22
What happened?
The
connect-api
is constantly logging the following error messageThe error message itself does not contain enough information to figure out which uuid / item has an invalid UUID.
I've gone through the 8 OnePasswordItems in our cluster and could not find any errors on them either
What did you expect to happen?
That the log message contains the UUID of the item
The text was updated successfully, but these errors were encountered: