Loading...

XML

Word

Printable

Story Points:
0
Epic Link:
OSPRH-26752
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Docs Approval:
?
AssignedTeam:
rhos-observability-telemetry
Regression:
None
Release Note Text:

Hide
.The `sg-core` container no longer crashes when accessing empty lists

Before this update, the `sg-core` container crashed with the message "panic: interface conversion: interface is nil, not main.expiry". This error was caused by the use of a list data structure that is not suitable for concurrent access. With this update, access to the shared list has been serialized to prevent the `sg-core` container crashing when accessing empty lists.

Show
.The `sg-core` container no longer crashes when accessing empty lists Before this update, the `sg-core` container crashed with the message "panic: interface conversion: interface is nil, not main.expiry". This error was caused by the use of a list data structure that is not suitable for concurrent access. With this update, access to the shared list has been serialized to prevent the `sg-core` container crashing when accessing empty lists.
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