Project

General

Profile

Actions
Copy link

Feature #45996

open

adopted prometheus instance uses port 9095, regardless of original port number

Added by Tim Serong almost 4 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

When adopting prometheus (cephadm adopt --style legacy --name prometheus.HOSTNAME), the new prometheus daemon starts listening on port 9095, regardless of what port the original daemon was running on. This is a problem for upgrades, as if you have an existing grafana instance it will still be looking at the old prometheus port number.

Related issues 3 (1 open — 2 closed)

Related to Orchestrator - Feature #45652: cephadm: Allow user to select monitoring stack portsDuplicate

Actions
Related to Orchestrator - Bug #46561: cephadm: monitoring services adoption doesn't honor the container imageNew

Actions
Blocked by Orchestrator - Feature #48822: Add proper port management to mgr/cephadmClosedSage Weil

Actions
Actions
Copy link
 #1

Updated by Sebastian Wagner over 3 years ago

  • Tracker changed from Bug to Feature
Actions
Copy link
 #2

Updated by Sebastian Wagner over 3 years ago

  • Related to Feature #45652: cephadm: Allow user to select monitoring stack ports added
Actions
Copy link
 #3

Updated by Sebastian Wagner about 3 years ago

  • Blocked by Feature #48822: Add proper port management to mgr/cephadm added
Actions
Copy link
 #4

Updated by Sebastian Wagner almost 3 years ago

  • Category changed from cephadm to cephadm/monitoring
Actions
Copy link
 #5

Updated by Sebastian Wagner almost 3 years ago

  • Related to Bug #46561: cephadm: monitoring services adoption doesn't honor the container image added
Actions
Copy link

Also available in: Atom PDF