Cause: Topology data model was originally a subset of the project workload details page. As more feature were added, topology grew to be similar but did not share the same code. As use cases became more complex, certain edge cases were being missed in the new code.
Consequence: In certain situations, the pod list when viewed from the topology was incorrect.
Fix: Code logic is now shared between the topology and project details workloads page.
Result: Whether viewing the sidebar pod list from topology or from the project details workloads list, the pod details will be identical.
Descriptionspathak@redhat.com
2019-10-11 12:28:18 UTC
Description of problem:
The following DC has two pods associated. One of which is in the `Failed` state and doesn't show up in the workload pod lists with the default filters as `Failed` are hidden.
The topology, however, does not show any pods in any state. Instead, it shows a visual depicting there are zero pods.
Comment 1spathak@redhat.com
2019-10-11 16:50:37 UTC
Fixed indirectly.
We did some work to update the utilities used for populating the topology data model. With this change, the topology and overview pages share the same logic.
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