Created attachment 1675935 [details] the "Source" link for firing alerts from user namespace still links to Alertmanager Description of problem: enable techPreviewUserWorkload and create PrometheusRule under usernamespaces, Alertmanager UI, the "Source" link for firing alerts still links to Alertmanager example, the "Source" link for firing alerts from user namespace https://alertmanager-main-openshift-monitoring.apps.qe-groupd-0403.qe.devcluster.openshift.com/graph?g0.expr=vector%281%29&g0.tab=1 debug in UI href="/graph?g0.expr=vector%281%29&g0.tab=1" the default prefix is the alertmanager-main route checked the firing cluster triggered by cluster-monitoring, the "Source" links to prometheus, example: https://prometheus-k8s-openshift-monitoring.apps.qe-groupd-0403.qe.devcluster.openshift.com/graph?g0.expr=vector%281%29&g0.tab=1 Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-02-195956 How reproducible: Always Steps to Reproduce: 1. See the description 2. 3. Actual results: the "Source" link for firing alerts from user namespace still links to Alertmanager Expected results: links to prometheus UI and show the result Additional info:
checked the firing cluster triggered by cluster-monitoring, the "Source" links to prometheus, example: -> checked the firing alerts triggered by cluster-monitoring, the "Source" links to prometheus, example:
Issue is fixed with 4.5.0-0.nightly-2020-04-25-170442, the "Source" link for firing alerts from user namespace links to thanos-querier UI, and show the result there
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 (OpenShift Container Platform 4.5 image release 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