Description of problem: Even if a node-proxy is not setup, it is being listed as a service under ceph orch ls [ceph: root@ceph-vpap-71bz-76fuuj-node1-installer /]# ceph orch ls NAME PORTS RUNNING REFRESHED AGE PLACEMENT alertmanager ?:9093,9094 1/1 89s ago 5h count:1 ceph-exporter 3/3 89s ago 5h * crash 3/3 89s ago 5h * grafana ?:3000 1/1 89s ago 5h count:1 mds.cephfs 2/2 27s ago 4h label:mds mgr 2/2 89s ago 5h count:2 mon 3/5 89s ago 5h count:5 node-exporter ?:9100 3/3 89s ago 5h * node-proxy 0/3 - 5h * osd.all-available-devices 18 89s ago 4h * prometheus ?:9095 1/1 89s ago 5h count:1 rgw.rgw.1 ?:80 2/2 27s ago 4h label:rgw [root@ceph-vpap-71bz-76fuuj-node1-installer ~]# systemctl list-units --all | grep node-proxy [root@ceph-vpap-71bz-76fuuj-node1-installer ~]# In the above output, we can see node-proxy with 0/3 running. Version-Release number of selected component (if applicable): Ceph 7.1 18.2.1-105.el9cp How reproducible: Always Steps to Reproduce: 1. Deploy a ceph 7.1 cluster 2. Check ceph orch ls Actual results: node-proxy service being listed under ceph orch ls Expected results: node-proxy should not be listed under ceph orch ls since it was not setup to begin with. Additional info:
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 (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and bug fix update), 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/RHSA-2024:3925