Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2053683

Summary:	[STF 1.3] Expose ringBufferSize parameter to ServiceTelemetry.clouds
Product:	Service Telemetry Framework	Reporter:	Leif Madsen <lmadsen>
Component:	service-telemetry-operator-container	Assignee:	Leif Madsen <lmadsen>
Status:	CLOSED WONTFIX	QA Contact:	Leonid Natapov <lnatapov>
Severity:	medium	Docs Contact:	Joanne O'Flynn <joflynn>
Priority:	medium
Version:	1.3	CC:	joflynn, lnatapov
Target Milestone:	z5	Keywords:	Triaged, ZStream
Target Release:	1.3 (STF)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2053681	Environment:
Last Closed:	2022-03-10 21:09:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2016460
Bug Blocks:

Description Leif Madsen 2022-02-11 18:29:22 UTC

+++ This bug was initially created as a clone of Bug #2053681 +++

Description of problem: The ringBufferSize parameter for the deployment of Smart Gateways is not exposed and is currently hard coded. This results in some large Ceilometer messages being corrupted in the ring buffer before being made available to the socket and consumption of sg-core.


Version-Release number of selected component (if applicable): STF 1.3.4


How reproducible: Always


Steps to Reproduce:
1. Deploy ServiceTelemetry
2. Connect RHOSP 16.2 to STF
3. Enable debugMessages: true in the cloud configuration on STF
4. View the logs and see that periodically some messages are corrupted, e.g.

2022-02-10 22:15:11 [DEBUG] failed handling message [error: ceilometer.OsloSchema.Request: isObjectEnd: object ended prematurely, unexpected char r, error found in #10 byte of ...|Sw��{"request": {|..., bigger context ...|ycast/ceilometer/cops04-metering.sampleSw��{"request": {"oslo.version": "2.0", "oslo.message": "|..., handler: ceilometer-metrics[socket0]]

Additional info: Issue is that the `--rbs` flag is not passed to the Deployment of Smart Gateway for the bridge container. The result is that the default ring buffer message size is set to 2048 and causes some larger Ceilometer messages (events, metrics) to be cut off and thus not parsable by sg-core.

The fix here is to allow the RBS value to be set, and to increase the default sizing to 16384 when deploying Smart Gateways. The maximum size is 65535 (maxBufferSize configured in sg-core as a constant).

Comment 1 Leif Madsen 2022-03-10 21:09:11 UTC

This is a non-trivial backport to a release that is in maintenance mode. Please upgrade to STF 1.4 if this functionality is necessary for your environment.