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.
Backport:
quincy, pacific, octopus
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.
- Status changed from New to Fix Under Review
- Pull request ID set to 46285
- 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
- Copied to Backport #56042: pacific: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
- Copied to Backport #56043: octopus: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
- Copied to Backport #56044: quincy: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF