RHBA-2022:0298 - Bug Fix Advisory

Topic

Release of components for the Service Telemetry Framework 1.4.0.

Description

Service Telemetry Framework (STF) provides automated collection of measurements and data from remote clients, such as Red Hat OpenStack Platform or third-party nodes. STF then transmits the information to a centralized, receiving Red Hat OpenShift Container Platform deployment for storage, retrieval, and monitoring.

This errata covers the release of Service Telemetry Framework 1.4.0 (General Availability)

Changes to the distribution component:

• The Service Telemetry Operator previously resulted in dependent Operators being installed by Operator Lifecycle Manager when subscribing to the Service Telemetry Operator. That functionality has been removed from this release.

As some of those Operators are outside the scope of the Red Hat Operator CatalogSource (non-productized Operators), do not rely on them for installation of the Service Telemetry Operator. An administrator deploying Service Telemetry Framework should subscribe to those Operators before deployment of a ServiceTelemetry object.

The Prometheus Operators are no longer installed automatically during a Service Telemetry Operator deployment. (BZ#1989569)

Changes to the service-telemetry-operator-container component:

• Add the `backends.events.elasticsearch.version` parameter to the ServiceTelemetry manifest so that the Elasticsearch version requested by STF to the Elasticsearch Operator can be specified. (BZ#2032659)
• In this release, the manually-created x-descriptors which provided UI hints to the OpenShift Container Platform user interface within the Operator Lifecycle Manager (OLM) were removed.

The removal of the x-descriptors results in the UI system using the API defined in the CustomResourceDefinition (CRD). Maintaining the UI hints is easier and more of the ServiceTelemetry objects configuration options are exposed to the OLM UI.

As a result, configuring ServiceTelemetry objects, especially in a multiple cloud environment, is now easier. (BZ#2008523)

Solution

The Service Telemetry Framework container image provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog.
Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally.

Affected Products

• Red Hat OpenStack 1 for RHEL 8 x86_64

Fixes

• BZ - 1975951 - sg-core crashing under high log volume
• BZ - 1989569 - Remove Service Telemetry Operator API dependencies from CSV
• BZ - 1999301 - Migrate Service Telemetry Operator to CustomResourceDefinition API version v1
• BZ - 1999302 - Migrate Smart Gateway Operator to CustomResourceDefinition API version v1
• BZ - 2008523 - [RFE] Add UI x-descriptors to allow configuration of clouds parameter
• BZ - 2032659 - [RFE] Implement version control for Elasticsearch deployment in Service Telemetry Operator
• STF-942 - Prepare STF Release 1.4.0

CVEs

• CVE-2016-10228
• CVE-2017-14502
• CVE-2018-20843
• CVE-2018-1000858
• CVE-2019-8625
• CVE-2019-8710
• CVE-2019-8720
• CVE-2019-8743
• CVE-2019-8764
• CVE-2019-8766
• CVE-2019-8769
• CVE-2019-8771
• CVE-2019-8782
• CVE-2019-8783
• CVE-2019-8808
• CVE-2019-8811
• CVE-2019-8812
• CVE-2019-8813
• CVE-2019-8814
• CVE-2019-8815
• CVE-2019-8816
• CVE-2019-8819
• CVE-2019-8820
• CVE-2019-8823
• CVE-2019-8835
• CVE-2019-8844
• CVE-2019-8846
• CVE-2019-9169
• CVE-2019-13050
• CVE-2019-13627
• CVE-2019-14889
• CVE-2019-15903
• CVE-2019-19906
• CVE-2019-20454
• CVE-2019-20807
• CVE-2019-25013
• CVE-2020-1730
• CVE-2020-3862
• CVE-2020-3864
• CVE-2020-3865
• CVE-2020-3867
• CVE-2020-3868
• CVE-2020-3885
• CVE-2020-3894
• CVE-2020-3895
• CVE-2020-3897
• CVE-2020-3899
• CVE-2020-3900
• CVE-2020-3901
• CVE-2020-3902
• CVE-2020-8927
• CVE-2020-9802
• CVE-2020-9803
• CVE-2020-9805
• CVE-2020-9806
• CVE-2020-9807
• CVE-2020-9843
• CVE-2020-9850
• CVE-2020-9862
• CVE-2020-9893
• CVE-2020-9894
• CVE-2020-9895
• CVE-2020-9915
• CVE-2020-9925
• CVE-2020-9952
• CVE-2020-10018
• CVE-2020-11793
• CVE-2020-13434
• CVE-2020-14391
• CVE-2020-15358
• CVE-2020-15503
• CVE-2020-27618
• CVE-2020-29361
• CVE-2020-29362
• CVE-2020-29363
• CVE-2021-3326
• CVE-2021-3421
• CVE-2021-3449
• CVE-2021-3450
• CVE-2021-3516
• CVE-2021-3517
• CVE-2021-3518
• CVE-2021-3520
• CVE-2021-3537
• CVE-2021-3541
• CVE-2021-3733
• CVE-2021-20271
• CVE-2021-20305
• CVE-2021-22946
• CVE-2021-22947
• CVE-2021-27218
• CVE-2021-30666
• CVE-2021-30761
• CVE-2021-30762
• CVE-2021-33928
• CVE-2021-33929
• CVE-2021-33930
• CVE-2021-33938
• CVE-2021-36222
• CVE-2021-37750

References

(none)