Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2242346

Summary:	cephadm_adopt does not keep Prometheus custom port during adoption
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	ggugliel
Component:	Ceph-Ansible	Assignee:	Teoman ONAY <tonay>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.3	CC:	adking, bkunal, ceph-eng-bugs, cephqe-warriors, enothen, gmeno, hpathan, jcaratza, ksachdev, rpollack, sostapov, tonay, tserlin
Target Milestone:	---
Target Release:	5.3z8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-6.0.28.19-1.el8cp	Doc Type:	Bug Fix
Doc Text:	.Prometheus port settings are kept during upgrade Previously, the Prometheus port definition would reset to the default value during an upgrade from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5. With this fix, the Prometheus port customer-defined settings are saved during an upgrade.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-13 19:22:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ggugliel 2023-10-05 16:16:44 UTC

Description of problem:
During the adoption step of RHCS 4 to RHCS 5 upgrade, cephadm-adopt doesn't keep Prometheus custom port configured in RHCS 4

Version-Release number of selected component (if applicable):
RHCS 5.3z5

How reproducible:
Upgrade an RHCS 4 with a Prometheus listening to a custom port to RHCS5. After adoption step, Prometheus listen to port 9095 instead of the custom port.

Steps to Reproduce:
1.setup an RHCS 4 cluster with custom Prometheus port (set in all.yml)
2.upgrade to RHCS 5.3z5 using rolling_update playbook
3.adopt the cluster using cephadm-adopt playbook

Actual results:
After adoption Prometheus listen on default port 9095

Expected results:
Prometheus listen to the port that was configured in RHCS4

Additional info:

Comment 1 RHEL Program Management 2023-10-05 16:16:56 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 3 Eric Nothen 2023-10-24 12:26:37 UTC

Teoman,

Aside from the question above, and assuming that this BZ is resolved in 7.1 (as currently assigned), would there be anything preventing a backport of the fix to RHCS 5? 

I'm asking because the customer has the expectation that they will eventually get the fix in RHCS 5, but I don't see clearly stated in this BZ one way or another.

Thanks,
Eric

Comment 6 Scott Ostapovicz 2024-01-08 15:30:09 UTC

So is this fix in place already?  We have passed the nominal target date for non-esential fixes for 5.3 z6.

Comment 7 Scott Ostapovicz 2024-02-07 15:41:21 UTC

Lack of updates and the need for a z7 release retargets this to z7.

Comment 33 errata-xmlrpc 2025-02-13 19:22:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 5.3 security and bug fix updates), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2025:1478