Project

General

Profile

Actions

Bug #55674

closed

mgr/cephadm: alertmanager generate_config also doesn't consider FQDN

Added by Tatjana Dehler almost 2 years ago. Updated almost 2 years ago.

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

0%

Source:
Tags:
Backport:
quincy, pacific, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

In https://tracker.ceph.com/issues/54502 I thought generate_config already considers the FQDN for the active mgr instance. Unfortunately it turned out this is not the case in any situation and depending on the configuration.


Related issues 3 (0 open3 closed)

Copied to Orchestrator - Backport #56042: pacific: mgr/cephadm: alertmanager generate_config also doesn't consider FQDNResolvedAdam KingActions
Copied to Orchestrator - Backport #56043: octopus: mgr/cephadm: alertmanager generate_config also doesn't consider FQDNResolvedAdam KingActions
Copied to Orchestrator - Backport #56044: quincy: mgr/cephadm: alertmanager generate_config also doesn't consider FQDNResolvedAdam KingActions
Actions #1

Updated by Volker Theile almost 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 46285
Actions #2

Updated by Adam King almost 2 years ago

  • Project changed from mgr to Orchestrator
  • Category deleted (ceph-mgr)
  • Status changed from Fix Under Review to Pending Backport
  • Backport changed from pacific octopus quincy to quincy, pacific, octopus
Actions #3

Updated by Backport Bot almost 2 years ago

  • Copied to Backport #56042: pacific: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Actions #4

Updated by Backport Bot almost 2 years ago

  • Copied to Backport #56043: octopus: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Actions #5

Updated by Backport Bot almost 2 years ago

  • Copied to Backport #56044: quincy: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Actions #6

Updated by Adam King almost 2 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF