Bug 1950219

Summary: KnativeServing is not shown in list on global config page
Product: OpenShift Container Platform Reporter: Yanping Zhang <yanpzhan>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: Debsmita Santra <dsantra>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: aos-bugs, dsantra, jakumar, jokerman, nmukherj, spadgett
Target Milestone: ---Keywords: Regression
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 23:01:26 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:

Description Yanping Zhang 2021-04-16 06:08:51 UTC
Description of problem:
After install openshift serverless operator and create knative-serving instance, check KnativeServing on globalconfig page, it doesn't show up.

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

How reproducible:

Steps to Reproduce:
1.Install OpenShift Serverless operator.
2.Create knative-serving instance in knative-serving project.
3.Go to "Administration"->"Cluster Settings"->"Global configuration", check KnativeServing config.

Actual results:
1.Operator is installed successfully.
2.Instance is created.
3.There is no KnativeServing configuration listed on the page.

Expected results:
3.Should show KnativeServing on the page

Additional info:

Comment 2 Debsmita Santra 2021-05-04 10:49:42 UTC
verified on 4.8.0-0.nightly-2021-04-30-102231

Comment 5 errata-xmlrpc 2021-07-27 23:01:26 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.8.2 bug fix and 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.