Bug 1877858

Summary: ConsoleNotification without spec.location does not appear
Product: OpenShift Container Platform Reporter: Robb Hamilton <rhamilto>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: VERIFIED --- QA Contact: Yanping Zhang <yanpzhan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, jokerman, yapei
Target Milestone: ---Keywords: UpcomingSprint
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.6.0-0.nightly-2020-09-10-054902 Cluster ID: 39238a3a-3e39-4049-85eb-5947fecfd0ee Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36
Last Closed: 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 Robb Hamilton 2020-09-10 15:40:47 UTC
Description of problem:  When creating a ConsoleNotification, spec.location is optional; however, if no spec.location is specified, the ConsoleNotification will not appear in the console.


Steps to Reproduce:
1.  Visit /k8s/cluster/console.openshift.io~v1~ConsoleNotification/~new
2.  Delete spec.location
3.  Click Create
4.  Note the ConsoleNotification does not appear in the console.

Actual results:  No ConsoleNotification appears.


Expected results:  The console should default the location for any ConsoleNotification without a spec.location.

Comment 1 Robb Hamilton 2020-09-11 14:12:35 UTC
PR in the merge queue; bug awaiting QE verification.

Comment 3 Yanping Zhang 2020-09-14 14:01:04 UTC
Checked on ocp 4.6 cluster with payload 4.6.0-0.nightly-2020-09-12-230035。
1.  Visit /k8s/cluster/console.openshift.io~v1~ConsoleNotification/~new
2.  Delete spec.location
3.  Click Create.
4. The created ConsoleNotification appears on the top of the console.
The bug is fixed.