Actions
Bug #59443
closedcephadm: port 9095 not opened in firewall after adopting prometheus
% Done:
0%
Source:
Tags:
backport_processed
Backport:
reef, quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Cephadm has logic to open relevant ports in the firewall when deploying daemons. However, when we adopt the monitoring stack daemons (prometheus, alertmanager, grafana) we don't attempt to open those ports. If the ports differ from the default cephadm ports, this can end up preventing these services from working (e.g. port used by prometheus differs on cephadm and ceph-ansible deployments).
Updated by Backport Bot 11 months ago
- Copied to Backport #61676: quincy: cephadm: port 9095 not opened in firewall after adopting prometheus added
Updated by Backport Bot 11 months ago
- Copied to Backport #61677: pacific: cephadm: port 9095 not opened in firewall after adopting prometheus added
Updated by Backport Bot 11 months ago
- Copied to Backport #61678: reef: cephadm: port 9095 not opened in firewall after adopting prometheus added
Actions