Bug 1834345

Summary: `/k8s/all-namespaces/import` in Dev Console results in 404
Product: OpenShift Container Platform Reporter: Robb Hamilton <rhamilto>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, jephilli, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.5.0-0.ci-2020-05-11-110006 Cluster ID: de6c9a2c-6321-4ff5-b668-1cf7a8ba200b Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Last Closed: 2020-07-13 17:37:32 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:
Attachments:
Description Flags
404 error none

Description Robb Hamilton 2020-05-11 14:34:50 UTC 
Created attachment 1687356 [details]
404 error

Description of problem:  Changing the project picker to `all namespaces` while on the `Import YAML` page in Dev Console results in 404 error.

Steps to Reproduce:
1.  In the dev console, visit `/add/all-namespaces`
2.  Click one of the existing project links.
3.  Click the `YAML` card.
4.  Change the project picker to `all namespaces`.
5.  Note the 404 error.

Actual results:  404 error.


Expected results:  Import YAML for all namespaces.


Additional info:  The bug is the result of https://github.com/openshift/console/blob/master/frontend/packages/dev-console/src/plugin.tsx#L740.  Note the admin console works correctly.
Comment 3 Gajanan More 2020-06-10 12:29:41 UTC 
I validated the bugzilla on:
Build:4.5.0-0.nightly-2020-06-09-223121
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.
Comment 4 errata-xmlrpc 2020-07-13 17:37:32 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, 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-2020:2409