Bug 1820495

Summary: Alertmanager UI, the "Source" link for firing alerts from user namespace still links to Alertmanager
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Simon Pasquier <spasquie>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: low    
Version: 4.5CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 18:03:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1819765    
Bug Blocks:    
Attachments:
Description Flags
the "Source" link for firing alerts from user namespace still links to Alertmanager none

Description Junqi Zhao 2020-04-03 08:22:42 UTC 
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:
Comment 1 Junqi Zhao 2020-04-03 08:24:45 UTC 
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:
Comment 6 Junqi Zhao 2020-04-26 02:14:41 UTC 
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
Comment 8 errata-xmlrpc 2020-08-04 18:03:57 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 (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