Bug 1912730

Summary: Operator backed: In-context should support visual connector if SBO is not installed
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Jaivardhan Kumar <jakumar>
Severity: medium Docs Contact:
Priority: high    
Version: 4.7CC: aballant, aos-bugs, jakumar, nmukherj
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:49:43 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 Sahil Budhwar 2021-01-05 11:09:41 UTC
Description of problem: 
Operator backed: In-context should support visual connector if SBO is not installed

Currently we show in-context option in topology for operatorbacked only if SBO is installed 

Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
go to toplogy
won't see in-context option for operatorbacked if SBO is not installed
Actual results: 
User is shown in-context option in topology for operatorbacked only if SBO is installed 

Expected results: 
User should be able see option of operator backed and should connect with visual connector if SBO is installed then should create SBR as it happens now

Comment 2 Jaivardhan Kumar 2021-01-13 09:49:04 UTC
Verified on 

OpenShift version
openshift-install: 4.7.0-0.nightly-2021-01-13-054018
Kubernetes version v1.20.0+32efea9

macOSX , Google chrome Version 87.0.4280.88 (Official Build) (x86_64)

Comment 5 errata-xmlrpc 2021-02-24 15:49:43 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.7.0 security, bug fix, and enhancement 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.

https://access.redhat.com/errata/RHSA-2020:5633