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

Bug 1989569

Summary: Remove Service Telemetry Operator API dependencies from CSV
Product: Service Telemetry Framework Reporter: Leif Madsen <lmadsen>
Component: distributionAssignee: Leif Madsen <lmadsen>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact: Joanne O'Flynn <joflynn>
Priority: medium    
Version: 1.3CC: jjoyce, joflynn, jschluet, lhh, mburns, mgarciac, shrjoshi
Target Milestone: GAKeywords: Triaged
Target Release: 1.4 (STF)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: service-telemetry-operator-container-1.4.0-1 Doc Type: Removed functionality
Doc Text:
Previously, the Service Telemetry Operator 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), they are no longer required for installation of the Service Telemetry Operator. As an administrator deploying Service Telemetry Framework, subscribe to those third-party Operators before you deploy of a ServiceTelemetry object. Only the Smart Gateway Operator is installed as a dependency of the Service Telemetry Operator.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-26 17:01:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 10 errata-xmlrpc 2022-01-26 17:01:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Service Telemetry Framework 1.4.0 - Container Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:0298