Bug 1609713 - ceph-metrics ansible doesn't remove prometheus-node-exporter.service after ceph-metrics purge
Summary: ceph-metrics ansible doesn't remove prometheus-node-exporter.service after ce...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Metrics
Version: 3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z4
: 3.3
Assignee: Christina Meno
QA Contact: Madhavi Kasturi
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1584264 1629656
TreeView+ depends on / blocked
 
Reported: 2018-07-30 08:45 UTC by Pratik Surve
Modified: 2021-09-03 22:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.The Prometheus `node-exporter` service is not removed after purging the Dashboard When purging the {product} Dashboard, the `node-exporter` service is not removed, and is still running. To work around this issue, manually stop and remove the `node-exporter` service. Perform the following commands as `root`: ---- # systemctl stop prometheus-node-exporter # systemctl disable prometheus-node-exporter # rpm -e prometheus-node-exporter # reboot ---- For Ceph Monitor, OSD, Object Gateway, MDS, and Dashboard, nodes, reboot these one at a time.
Clone Of:
Environment:
Last Closed: 2020-02-25 18:52:44 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-1438 0 None None None 2021-09-03 22:10:35 UTC

Description Pratik Surve 2018-07-30 08:45:05 UTC 
Description of problem:
ceph-metrics ansible doesn't remove prometheus-node-exporter.service after ceph-metrics purge

Version-Release number of selected component (if applicable):
cephmetrics-ansible-2.0-3.el7cp.x86_64

How reproducible:
always

Steps to Reproduce:
1.deploy ceph cluster 
2.deploy ceph-metrics
3.purge ceph-metrics

Actual results:
prometheus-node-exporter service is active (running)

Expected results:
prometheus-node-exporter service should not be up

Additional info:
Comment 7 Giridhar Ramaraju 2019-08-05 13:09:21 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 8 Giridhar Ramaraju 2019-08-05 13:10:38 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Note You need to log in before you can comment on or make changes to this bug.