-
Notifications
You must be signed in to change notification settings - Fork 77
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
Noobaa events_api fails with error INVALID_SCHEMA_REPLY SERVER #7071
Comments
Hi, Can you please provide some help on this issue? |
Hello @arunprasadmudaliar 🖖 I have tried to reproduce this issue with both v5.10.1 and the latest master branch operator/core installation, I do not see the issue: ➜ noobaa-operator git:(master) ✗ ./build/_output/bin/noobaa-operator-local -n noobaa api events_api read_activity_log '{}'
INFO[0000] ✅ Exists: NooBaa "noobaa"
INFO[0000] ✅ Exists: Service "noobaa-mgmt"
INFO[0000] ✅ Exists: Secret "noobaa-operator"
INFO[0000] ✅ Exists: Secret "noobaa-admin"
INFO[0000] ✈️ RPC: events.read_activity_log() Request: map[]
WARN[0000] RPC: GetConnection creating connection to wss://localhost:65366/rpc/ 0xc0003b6b40
INFO[0000] RPC: Connecting websocket (0xc0003b6b40) &{RPC:0xc00045dd60 Address:wss://localhost:65366/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>}
INFO[0000] RPC: Connected websocket (0xc0003b6b40) &{RPC:0xc00045dd60 Address:wss://localhost:65366/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>}
INFO[0000] ✅ RPC: events.read_activity_log() Response OK: took 44.9ms
logs:
- desc:
- Drive /noobaa_storage of noobaa-default-backing-store-noobaa-pod-e25426c8 in pool
noobaa-default-backing-store is online
event: node.connected
id: 63397dee5c53f6002fc965a0
level: info
node:
linkable: true
name: noobaa-default-backing-store-noobaa-pod-e25426c8#1
pool: noobaa-default-backing-store
time: 1664712174965
- actor:
email: operator@noobaa.io
linkable: true
desc:
- A managed pool noobaa-default-backing-store with 1 nodes was created by operator@noobaa.io
event: resource.create
id: 63397d225c53f6002fc9659c
level: info
pool:
linkable: true
name: noobaa-default-backing-store
resource_type: HOSTS
time: 1664711970827
- account:
email: admin@noobaa.io
linkable: true
desc:
- 'admin@noobaa.io was created '
event: account.create
id: 63397cc45c53f6002fc96593
level: info
time: 1664711876291
- actor:
email: admin@noobaa.io
linkable: true
desc:
- noobaa was created by admin@noobaa.io
event: conf.create_system
id: 63397cb65c53f6002fc9658f
level: info
time: 1664711861995 Could you please provide more info? v5.10.1➜ noobaa-operator git:(6f571fd) ✗ ./build/_output/bin/noobaa-operator-local version
INFO[0000] CLI version: 5.10.1
INFO[0000] noobaa-image: noobaa/noobaa-core:5.10.1
INFO[0000] operator-image: noobaa/noobaa-operator:5.10.1
➜ noobaa-operator git:(6f571fd) ✗ k get noobaa noobaa -n noobaa -o yaml | grep Core
readme: "\n\n\tWelcome to NooBaa!\n\t-----------------\n\tNooBaa Core Version: 5.10.1-e8c9b09\n\tNooBaa
Latest master➜ noobaa-operator git:(master) ✗ ./build/_output/bin/noobaa-operator-local version
INFO[0000] CLI version: 5.12.0
INFO[0000] noobaa-image: noobaa/noobaa-core:master-20220913
INFO[0000] operator-image: noobaa/noobaa-operator:5.12.0
➜ noobaa-operator git:(master) ✗ k get noobaa noobaa -n noobaa -o yaml | grep Core
readme: "\n\n\tWelcome to NooBaa!\n\t-----------------\n\tNooBaa Core Version: 5.12.0-cfbf726\n\tNooBaa
Please share your thoughts. |
Hello @baum, Thank you for responding. Based on your comment, I verified the version of the client and the operator and indeed they were different in my case. ( operator was 5.8.0 and the client was 5.10.0). I have now downgraded my client version to 5.8.0 to match the operator: CLI Operator version ( as shown in web-console) But I still get the same error: INFO[0002] ✅ Exists: NooBaa "noobaa" I have to connect to the server through a VPN connection and initially I thought might be its due to VPN. But later I realized that the websocket connection shows connected and as well as other api queries related to bucket works fine. It's only the events api that throws an error. I tried the export_activity_log but again I get an error. Using the -o flag does not help here. Looks like it is failing due to type casting. noobaa api events_api export_activity_log '{}' -o yaml Please provide any suggestions that you want me to try. Upgrading the operator to latest version is bit difficult as it is maintained by another team. |
Hello @arunprasadmudaliar 🖖
Best regards. |
Hello @baum, Thanks for sharing the above issue details for export_activity_log. I tried to run read_activity_log with 5.10.1 cli but the error still remains the same. ERRO[0009] root@~/noobaa5.10# ./noobaa version So, if I could summarize, I have a noobaa server (operator) of version 5.8.0 and I had tried CLI version's 5.8.0 ( to match server version) and 5.10.1. But I still receive the same error. As far as I understood, the cli and operator are same binaries and so do you think I should try updating the noobaa server (operator) to latest version? Regards, |
Test: ➜ noobaa-operator git:(6f571fd) ✗ ./build/_output/bin/noobaa-operator-local -n noobaa api events_api export_activity_log '{}' INFO[0000] ✅ Exists: NooBaa "noobaa" INFO[0000] ✅ Exists: Service "noobaa-mgmt" INFO[0000] ✅ Exists: Secret "noobaa-operator" INFO[0000] ✅ Exists: Secret "noobaa-admin" INFO[0000]✈️ RPC: events.export_activity_log() Request: map[] WARN[0000] RPC: GetConnection creating connection to wss://localhost:63468/rpc/ 0xc000b9fc20 INFO[0000] RPC: Connecting websocket (0xc000b9fc20) &{RPC:0xc0003659a0 Address:wss://localhost:63468/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} INFO[0000] RPC: Connected websocket (0xc000b9fc20) &{RPC:0xc0003659a0 Address:wss://localhost:63468/rpc/ State:init WS:<nil> PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:<nil>} ERRO[0001] RPC: HandleResponse for OP res API raw bytes {"op":"res","reqid":"wss://localhost:63468/rpc/-0","took":898.633090000134,"reply":{"out_path":"/public/audit.csv"}} INFO[0001] ✅ RPC: events.export_activity_log() Response OK: took 898.6ms out_path: /public/audit.csv Signed-off-by: Alexander Indenbaum <aindenba@redhat.com>
This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed. |
Environment info
Actual behavior
Expected behavior
Steps to reproduce
More information - Screenshots / Logs / Other output
INFO[0008] ✅ Exists: NooBaa "noobaa"✈️ RPC: events.read_activity_log() Request: map[]⚠️ RPC: events.read_activity_log() Response Error: Code=INVALID_SCHEMA_REPLY Message=INVALID_SCHEMA_REPLY SERVER events_api#/methods/read_activity_log
INFO[0008] ✅ Exists: Service "noobaa-mgmt"
INFO[0008] ✅ Exists: Secret "noobaa-operator"
INFO[0009] ✅ Exists: Secret "noobaa-admin"
INFO[0014]
WARN[0014] RPC: GetConnection creating connection to wss://localhost:45005/rpc/ 0xc000478d80
INFO[0014] RPC: Connecting websocket (0xc000478d80) &{RPC:0xc0003d9c20 Address:wss://localhost:45005/rpc/ State:init WS: PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:}
INFO[0016] RPC: Connected websocket (0xc000478d80) &{RPC:0xc0003d9c20 Address:wss://localhost:45005/rpc/ State:init WS: PendingRequests:map[] NextRequestID:0 Lock:{state:1 sema:0} ReconnectDelay:0s cancelPings:}
ERRO[0018]
FATA[0018] ❌ INVALID_SCHEMA_REPLY SERVER events_api#/methods/read_activity_log
We tried 'read_bucket' of 'buckets_api' and that works without any issues when executed from CLI.
As a part of our automation we wanted to get activity logs of obj.upload and obj.download events. Please let me know if this is the correct approach or I am missing something here?
The text was updated successfully, but these errors were encountered: