Bug 2023228 - Remove Tech preview badge on Trigger components 1.6 OSP on OCP 4.9
Summary: Remove Tech preview badge on Trigger components 1.6 OSP on OCP 4.9
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: All
OS: All
Target Milestone: ---
: 4.10.0
Assignee: Karthik Jeeyar
QA Contact: spathak@redhat.com
Depends On:
Blocks: 2025799
TreeView+ depends on / blocked
Reported: 2021-11-15 09:25 UTC by Karthik Jeeyar
Modified: 2022-03-10 16:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:27:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10473 0 None open Bug 2023228: Remove Tech preview badge for the triggers component for triggers GA … 2021-11-16 09:50:33 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:27:41 UTC

Description Karthik Jeeyar 2021-11-15 09:25:35 UTC
Description of problem:

OSP 1.6 uses Triggers 0.16 (GA version of triggers components), so we need to remove the Tech preview badges on the OCP UI 4.9.

Version-Release number of selected component (if applicable):
OCP - 4.9

How reproducible:

Steps to Reproduce:
1. Install OSP 1.6 on OCP-4.9

Actual results:
Tech preview badges is shown in the admin-> pipelines -> Triggers pages.

Expected results:
Tech preview badges needs to be removed

Additional info:

Comment 5 spathak@redhat.com 2021-12-06 07:27:02 UTC
Verified on build version: 4.10.0-0.ci-2021-12-04-104040
Browser version: chrome 90

Comment 9 errata-xmlrpc 2022-03-10 16:27:22 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.