Loading...

XML

Word

Printable

Story Points:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Docs Approval:
?
Regression:
None
Release Note Text:

Hide
Cause: high loaded STF deployments
Consequence: sg-core crashes with "panic: interface conversion: interface is nil, not main.expiry"
Fix: The container/list data structure used in expiry.go is not safe for concurrent use. Serialize the access to the shared list to avoid having check() on empty lists.
Result: sg-core no longer crashes

Show
Cause: high loaded STF deployments Consequence: sg-core crashes with "panic: interface conversion: interface is nil, not main.expiry" Fix: The container/list data structure used in expiry.go is not safe for concurrent use. Serialize the access to the shared list to avoid having check() on empty lists. Result: sg-core no longer crashes
Release Note Type:
Bug Fix
Git Pull Request:
https://github.com/infrawatch/sg-core/pull/155
Intelligence Requested:
Market:
PX Impact Score:

To Reproduce Steps to reproduce the behavior:

Deploy STF 1.5.6
Connect STF to a OSP 17.1 cloud
Allow messages to flow and see the sg-core container crashing sporadically
Inspect logs for the pod with "oc logs -f default-cloud-smartgateway -c sg-core --previous --tail 50"
See "panic: interface conversion: interface is nil, not main.expiry" trace

Expected behavior

Bug impact

Known workaround

Additional context

This is reproducible when the cloud monitored by that sg-core is a production cloud and the volume of metrics being processed is high