Project

General

Profile

Actions

Bug #54502

closed

mgr/cephadm: alertmanager generate_config doesn't consider FQDN

Added by Tatjana Dehler about 4 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Category:
ceph-mgr
Target version:
-
% Done:

0%

Source:
Backport:
pacific octopus quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Fixed In:
v17.0.0-11226-g5301c3737ca
Released In:
v18.2.0~2523
Upkeep Timestamp:
2025-07-14T06:47:35+00:00

Description

The Prometheus alertmanager contains a dashboard webhook_config entry for every mgr instance (active and inactive) as part of the config. Unfortunately the 'generate_config' function (which is responsible for creating the config) does only consider the FQDN of the active mgr. For the inactive ones, it takes the information from the inventory. The inventory might contain the short host-name only, e.g.:

- name: ceph-dashboard
webhook_configs:
- send_resolved: true
http_config: {}
url: https://node1.pacific.test:8443//api/prometheus_receiver
max_alerts: 0
- send_resolved: true
http_config: {}
url: https://node2:8443/api/prometheus_receiver
max_alerts: 0
- send_resolved: true
http_config: {}
url: https://node3:8443/api/prometheus_receiver
max_alerts: 0

This might lead to issues with configured certificates that apply to FQDN only.

It would be better to check if it's possible to get the FQDN for the inactive instances as well. If yes, take it. If not, fall back to the short host-name.


Related issues 3 (0 open3 closed)

Copied to mgr - Backport #55035: octopus: mgr/cephadm: alertmanager generate_config doesn't consider FQDNResolvedTatjana DehlerActions
Copied to mgr - Backport #55036: pacific: mgr/cephadm: alertmanager generate_config doesn't consider FQDNResolvedTatjana DehlerActions
Copied to mgr - Backport #55042: quincy: mgr/cephadm: alertmanager generate_config doesn't consider FQDNResolvedTatjana DehlerActions
Actions #1

Updated by Tatjana Dehler about 4 years ago

  • Backport set to pacific, octopus
Actions #2

Updated by Tatjana Dehler almost 4 years ago

  • Pull request ID set to 45333
Actions #3

Updated by Tatjana Dehler almost 4 years ago

  • Status changed from New to Pending Backport
Actions #4

Updated by Tatjana Dehler almost 4 years ago

  • Backport changed from pacific, octopus to pacific octopus
Actions #5

Updated by Tatjana Dehler almost 4 years ago

  • Copied to Backport #55035: octopus: mgr/cephadm: alertmanager generate_config doesn't consider FQDN added
Actions #6

Updated by Upkeep Bot almost 4 years ago

  • Copied to Backport #55036: pacific: mgr/cephadm: alertmanager generate_config doesn't consider FQDN added
Actions #7

Updated by Tatjana Dehler almost 4 years ago

  • Backport changed from pacific octopus to pacific octopus quincy
Actions #8

Updated by Upkeep Bot almost 4 years ago

  • Copied to Backport #55042: quincy: mgr/cephadm: alertmanager generate_config doesn't consider FQDN added
Actions #10

Updated by Konstantin Shalygin over 3 years ago

  • Status changed from Pending Backport to Resolved
Actions #11

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to 5301c3737ca89ec175b3d4900f98d7b3854d0891
  • Fixed In set to v17.0.0-11226-g5301c3737ca
  • Released In set to v18.2.0~2523
  • Upkeep Timestamp set to 2025-07-14T06:47:35+00:00
Actions

Also available in: Atom PDF