Bug 1854151

Summary: Adding an S2I application after selecting all projects creates a form that can never be submitted
Product: OpenShift Container Platform Reporter: Jessica Forrester <jforrest>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:12:24 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 Jessica Forrester 2020-07-06 15:17:06 UTC
In the developer perspective go to the all projects page.
Then choose to +Add and pick one of the builder images like node.js.

This form can not be submitted until there is a namespace, but there is no way to set the namespace. Worse, there is nothing indicating to the user why they can't actually submit the form.

Expected: this page should provide the namespace picker form field when it's in the context of "all projects".

Comment 1 Jessica Forrester 2020-07-06 15:22:51 UTC
Sam let me know that going to the add page in an all projects scope should not even be possible. So here is how I did that:

1) From the scope of any namespace, go into Add and choose the From Catalog option
2) In the namespace picker in the top of the page, switch it to All Projects

You will stay on the catalog page, but your context is now all projects, letting you pick the builder image and get into the form in an invalid state.

Comment 5 Gajanan More 2020-08-24 09:11:20 UTC
I have validated the bugzilla on:

Build: 4.6.0-0.nightly-2020-08-23-214712

Browser: Google Chrome Version 84.0.4147.89 

 Marking this as verified.

Comment 7 errata-xmlrpc 2020-10-27 16:12:24 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 (OpenShift Container Platform 4.6 GA 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.