Project

General

Profile

Feature #45996

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

Added by Tim Serong 10 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm
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

Related to Orchestrator - Feature #45652: cephadm: Allow user to select monitoring stack ports New
Blocked by Orchestrator - Feature #48822: Add proper port management to mgr/cephadm Closed

History

#1 Updated by Sebastian Wagner 5 months ago

  • Tracker changed from Bug to Feature

#2 Updated by Sebastian Wagner 5 months ago

  • Related to Feature #45652: cephadm: Allow user to select monitoring stack ports added

#3 Updated by Sebastian Wagner about 2 months ago

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

Also available in: Atom PDF