Bug 1768716 - Launcher section don't show up on Namespace Overview
Summary: Launcher section don't show up on Namespace Overview
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-05 05:25 UTC by Yadan Pei
Modified: 2020-01-23 11:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:10:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3241 0 'None' 'closed' 'Bug 1768716: Add NamespaceDashboard links to namespace overview' 2019-11-22 14:15:08 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:11:05 UTC

Description Yadan Pei 2019-11-05 05:25:43 UTC
Description of problem:
When we create ConsoleLink with location set as NamespaceDashboard, there will be a Launcher section on Project Dashboard page, but the Launcher section is missing on Namespace Overview page

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-04-210904

How reproducible:
Always

Steps to Reproduce:
1. Create ConsoleLink with location set as NamespaceDashboard
$ cat > helplink1.yaml << EOF
apiVersion: console.openshift.io/v1
kind: ConsoleLink
metadata:
  name: namespaced-dashboard-link-for-all-namespaces
spec:
  href: 'https://www.example.com'
  location: NamespaceDashboard
  text: This appears in all namespaces
EOF
$ oc create -f helplink1.yaml
2. Check Launcher in project details
steps: Home -> Project -> default
3. Check Launcher in namespace details
steps: Administration -> Namespaces -> default

Actual results:
2. There is Launcher section and `This appears in all namespaces` link
3. No Launcher section

Expected results:
3. According to PR https://github.com/openshift/console/pull/2698, there should be a Launcher section on namespace Overview page with correct links shown

Additional info:

Comment 1 Robb Hamilton 2019-11-05 13:56:29 UTC
@Yadan, did you refresh the browser after adding the new link?  We're not watching ConsoleLinks, so the Launcher section will only appear after a browser refresh.

Comment 2 Robb Hamilton 2019-11-05 15:38:58 UTC
> @Yadan, did you refresh the browser after adding the new link?  We're not watching ConsoleLinks, so the Launcher section will only appear after a browser refresh.

Disregard.  I misread the bug.  The Launcher section is not currently on the Namespace Overview.

Comment 4 Yadan Pei 2019-11-11 02:40:04 UTC
1. Create two ConsoleLinks, one targets all namespaces and the other targets specific namespace
$ cat > link1.yaml << EOF
apiVersion: console.openshift.io/v1
kind: ConsoleLink
metadata:
  name: example-namespace-dashboard
spec:
  href: 'https://www.example.com'
  location: NamespaceDashboard
  text: Namespace Dashboard Link
  namespaceDashboard:
    namespaces:
      - default
EOF

$ cat > link2.yaml << EOF
apiVersion: console.openshift.io/v1
kind: ConsoleLink
metadata:
  name: example-namespace-dashboard-all
spec:
  href: 'https://www.example.com'
  location: NamespaceDashboard
  text: This appears in all Namespace Dashboard Link
EOF
$ oc create -f link1.yaml -f link2.yaml

2. Visit Home -> Project -> default, on project Dashboard we can see two links in Launcher section
3. Visit Administration -> Namepsace -> deafult, we can also see a Launcher section with two links too


Verified on 4.3.0-0.nightly-2019-11-10-185106

Comment 6 errata-xmlrpc 2020-01-23 11:10:52 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:0062


Note You need to log in before you can comment on or make changes to this bug.