-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.12, 4.11
-
None
-
None
-
False
-
-
This is a clone of issue OCPBUGS-5293. The following is the description of the original issue:
—
Description of problem
call for os-clock-sync-state returns Invalid memory error and stops receiving and message >> It works for other two events.
Error Message
cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status result *Error
"
:
success status to send(TO): /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/ptp-status/lock-state/wz5Pf result <nil> " time="2023-01-03T20:23:24Z" level=info msg="created new sender for /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status" time="2023-01-03T20:23:24Z" level=info msg="sending status requerst to status address /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status with return /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC" time="2023-01-03T20:23:24Z" level=info msg="waiting to receive message at /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC" time="2023-01-03T20:23:24Z" level=info msg="setting return address to /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC" time="2023-01-03T20:23:24Z" level=info msg="got status check call,send events for subscriber 00000000-0000-0000-0000-000000000000 => /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC" time="2023-01-03T20:23:24Z" level=info msg="created new sender for /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC" time="2023-01-03T20:23:24Z" level=info msg="got the status msg Context Attributes,\n specversion: 0.3\n type: event.sync.sync-status.os-clock-sync-state-change\n source: /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state\n subject: /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state\n id: 679c4402-c4b6-43fb-a0a2-b5d5105de255\n time: 2023-01-03T20:23:24.697Z\n datacontenttype: application/json\nData,\n {\n \"version\": \"v1\",\n \"values\": [\n {\n \"resource\": \"/cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/CLOCK_REALTIME\",\n \"dataType\": \"notification\",\n \"valueType\": \"enumeration\",\n \"value\": \"LOCKED\"\n },\n {\n \"resource\": \"/cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/CLOCK_REALTIME\",\n \"dataType\": \"metric\",\n \"valueType\": \"decimal64.3\",\n \"value\": \"6\"\n }\n ]\n }\n" time="2023-01-03T20:23:24Z" level=error msg="success status to send(TO): /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC result <nil> " time="2023-01-03T20:23:30Z" level=info msg="sending status requerst to status address /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status with return /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/4phwD" time="2023-01-03T20:23:30Z" level=info msg="waiting to receive message at /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/4phwD" time="2023-01-03T20:23:30Z" level=info msg="setting return address to /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/4phwD" time="2023-01-03T20:23:30Z" level=info msg="got status check call,send events for subscriber 00000000-0000-0000-0000-000000000000 => /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/4phwD" {"level":"error","ts":1672777410.3417394,"logger":"fallback","caller":"client/invoker.go:77","msg":"call to Invoker.Invoke(...) has panicked: runtime error: invalid memory address or nil pointer dereference","stacktrace":"github.com/cloudevents/sdk-go/v2/client.(*receiveInvoker).Invoke.func2.1\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/invoker.go:77\nruntime.gopanic\n\t/usr/lib/golang/src/runtime/panic.go:884\nruntime.panicmem\n\t/usr/lib/golang/src/runtime/panic.go:260\nruntime.sigpanic\n\t/usr/lib/golang/src/runtime/signal_unix.go:835\nplugin/unnamed-4ef8c97d69adf9a5afd502688ae75fef59e20c66.getCurrentStatOverrideFn.func1.1\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/plugins/ptp_operator/ptp_operator_plugin.go:202\nplugin/unnamed-4ef8c97d69adf9a5afd502688ae75fef59e20c66.getCurrentStatOverrideFn.func1\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/plugins/ptp_operator/ptp_operator_plugin.go:223\ngithub.com/redhat-cne/sdk-go/pkg/protocol/amqp.(*Router).setReceiver.func1\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/redhat-cne/sdk-go/pkg/protocol/amqp/amqp.go:586\nreflect.Value.call\n\t/usr/lib/golang/src/reflect/value.go:584\nreflect.Value.Call\n\t/usr/lib/golang/src/reflect/value.go:368\ngithub.com/cloudevents/sdk-go/v2/client.(*receiverFn).invoke\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/receiver.go:91\ngithub.com/cloudevents/sdk-go/v2/client.(*receiveInvoker).Invoke.func2\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/invoker.go:85\ngithub.com/cloudevents/sdk-go/v2/client.(*receiveInvoker).Invoke\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/invoker.go:88\ngithub.com/cloudevents/sdk-go/v2/client.(*ceClient).StartReceiver.func2.1\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/client.go:253\ngithub.com/cloudevents/sdk-go/v2/client.(*ceClient).StartReceiver.func2.2\n\t/go/src/github.com/redhat-cne/cloud-event-proxy/vendor/github.com/cloudevents/sdk-go/v2/client/client.go:265"} time="2023-01-03T20:23:30Z" level=error msg="failed to send(TO): /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status result *Error{Condition: github.com/cloudevents/sdk-go/protocol/amqp/v2, Description: call to Invoker.Invoke(...) has panicked: runtime error: invalid memory address or nil pointer dereference, Info: map[]} "
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Deploy with event enabled and exec into it (AMQ required to be running ) 2. run this command ( replace node name) curl http://localhost:9085/api/cloudNotifications/v1/cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/CurrentState Actual results:{code:none} Works first time and next time errors
Expected results:
Should work every time msg="got the status msg Context Attributes,\n specversion: 0.3\n type: event.sync.sync-status.os-clock-sync-state-change\n source: /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state\n subject: /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state\n id: 679c4402-c4b6-43fb-a0a2-b5d5105de255\n time: 2023-01-03T20:23:24.697Z\n datacontenttype: application/json\nData,\n {\n \"version\": \"v1\",\n \"values\": [\n {\n \"resource\": \"/cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/CLOCK_REALTIME\",\n \"dataType\": \"notification\",\n \"valueType\": \"enumeration\",\n \"value\": \"LOCKED\"\n },\n {\n \"resource\": \"/cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/CLOCK_REALTIME\",\n \"dataType\": \"metric\",\n \"valueType\": \"decimal64.3\",\n \"value\": \"6\"\n }\n ]\n }\n" time="2023-01-03T20:23:24Z" level=error msg="success status to send(TO): /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/RjkwC result <nil> " time="2023-01-03T20:23:30Z" level=info msg="sending status requerst to status address /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/status with return /cluster/node/cnfde4.ptp.lab.eng.bos.redhat.com/sync/sync-status/os-clock-sync-state/4phwD" (This could be due to clearing of resource)
- blocks
-
OCPBUGS-5357 Current State api call for os-clock-state creates nil pointer
- Closed
- clones
-
OCPBUGS-5293 Current State api call for os-clock-state creates nil pointer-Dual Nic
- Closed
- is blocked by
-
OCPBUGS-5293 Current State api call for os-clock-state creates nil pointer-Dual Nic
- Closed
- is cloned by
-
OCPBUGS-5357 Current State api call for os-clock-state creates nil pointer
- Closed
- links to