Actions
Bug #55674
closedmgr/cephadm: alertmanager generate_config also doesn't consider FQDN
% Done:
0%
Source:
Tags:
Backport:
quincy, pacific, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Updated by Volker Theile almost 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 46285
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
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56042: pacific: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56043: octopus: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56044: quincy: mgr/cephadm: alertmanager generate_config also doesn't consider FQDN added
Updated by Adam King almost 2 years ago
- Status changed from Pending Backport to Resolved
Actions