Description of problem:
clicking on a daemonset pod takes you to the daemonset list
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. deploy a daemonset
2. click on the daemonset pods (the big blue circle)
This takes you to the daemonset list
this should take you to the pod list of that dameonset or to the pod directly if there is only one pod.
This is intentional, although I understand why it's a little odd. Clicking on the donut for any resource with more than one pod takes you to the resource details. In the case of a daemon set, we don't have a dedicated page, so we go to the list.
I'm going to leave this open as a low severity defect. We will address in the 4.0 coverged console.
Clicking on the daemon set pod link in the 4.0 overview takes you directly to the daemon set pod list.
1. Create DaemonSet
2. Go to Home -> Status page
3. Clicking on N of N pods redirects to DaemonSet Pods list page
$ oc get pods openshift-console-6d9974dd74-5hjqt -n openshift-console -o yaml | grep image
$ oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a8f450c6f9047ab41cb624d5834e916e99c5d8ea43328211e40ec694363b8803
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.