Bug 1765485

Summary: [Ceph-Dashboard] Alerts: The URL for active alert launches with short hostname and fails to connect to server
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Madhavi Kasturi <mkasturi>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, nthomas, tchandra, tserlin, ykaul
Target Milestone: rcKeywords: TestBlocker
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.7-1.el8cp, ceph-ansible-4.0.7-1.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:47:59 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:
Attachments:
Description Flags
Screenshot -Server not found none

Comment 1 Ernesto Puerta 2019-11-21 12:28:35 UTC 
@Madhavi, this seems a Prometheus issue, as that URL comes from Prometheus itself as 'generatorURL' data. Fortunately it has been fixed in that project (https://github.com/prometheus/prometheus/pull/717), but for it to work, we would need Ceph-Ansible to set Prometheus config 'web.hostname' to its FQDN.

I'll move this to Ceph-Ansible component. I think this shouldn't be high severity, as there exists a workaround (manually appending the missing FQDN parts) and the alerts themselves are configured in Prometheus, so users will mostly come from Prometheus to Dashboard rather than the opposite.
Comment 4 Madhavi Kasturi 2019-12-02 13:10:39 UTC 
Created attachment 1641379 [details]
Screenshot -Server not found
Comment 20 errata-xmlrpc 2020-01-31 12:47:59 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:0312