Project

General

Profile

Actions

Bug #59443

closed

cephadm: port 9095 not opened in firewall after adopting prometheus

Added by Adam King about 1 year ago. Updated 2 months ago.

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

0%

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

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).


Related issues 3 (0 open3 closed)

Copied to Orchestrator - Backport #61676: quincy: cephadm: port 9095 not opened in firewall after adopting prometheusResolvedAdam KingActions
Copied to Orchestrator - Backport #61677: pacific: cephadm: port 9095 not opened in firewall after adopting prometheusResolvedAdam KingActions
Copied to Orchestrator - Backport #61678: reef: cephadm: port 9095 not opened in firewall after adopting prometheusResolvedAdam KingActions
Actions #1

Updated by Adam King about 1 year ago

  • Pull request ID set to 51070
Actions #2

Updated by Adam King 11 months ago

  • Status changed from In Progress to Pending Backport
Actions #3

Updated by Backport Bot 11 months ago

  • Copied to Backport #61676: quincy: cephadm: port 9095 not opened in firewall after adopting prometheus added
Actions #4

Updated by Backport Bot 11 months ago

  • Copied to Backport #61677: pacific: cephadm: port 9095 not opened in firewall after adopting prometheus added
Actions #5

Updated by Backport Bot 11 months ago

  • Copied to Backport #61678: reef: cephadm: port 9095 not opened in firewall after adopting prometheus added
Actions #6

Updated by Backport Bot 11 months ago

  • Tags set to backport_processed
Actions #7

Updated by Adam King 2 months ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF