Description of problem: On the Dashboard -> Cluster -> Monitoring page, source url of prometheus is in format http://hostname:9095 which doesn't work when you click because it's not fully qualified. It works fine if you manually change it to FQDN like http://fqdn:9095. If the cluster is bootstrapped using the --allow-fqdn-hostname option and the server OS is built using the fqdn (ie hostname returns the fqdn) then the link is rendered correctly. Version-Release number of selected component (if applicable): 5.2 How reproducible: By deploying services using short hostnames without --allow-fqdn-hostname option and server OS was built using short hostname (hostname command returns shortname, not fqdn) Steps to Reproduce: 1. Deploy services using short hostnames 2. Check Dashboard -> Cluster -> Monitoring page if the prometheus url built using shortname or FQDN 3. Actual results: Dashboard -> Cluster -> Monitoring page, source url of prometheus is in format http://shortname:9095 Expected results: Dashboard -> Cluster -> Monitoring page, source url of prometheus is in format http://fqdn:9095 Additional info:
I submitte the following Upstream fix candidate: https://github.com/ceph/ceph/pull/49836
Hi @yalbayra Just to understand a little bit and to get more context :) 1) Did the customer test the fix? 2) which release did they use to test it? 3) Why the customer is complaining about https when prometheus in 5.3 is plain http only? Right now, for 5.3 we can't do much as AFAIK. The fix consists on using IPs because we don't have any procedure to migrate a cluster using short-names to fqdns automatically. For 7.0 we will study the possibility of adding fqdn dynamically for already deployed hosts (user will need to add it by hand).
*** Bug 2209384 has been marked as a duplicate of this bug. ***
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 (Moderate: Red Hat Ceph Storage 6.1 security and bug fix update), 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/RHSA-2023:3623