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 1884571

Summary: [GSS][ceph-ansible] node-exporter container not coming online after rolling update
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Janmejay Singh <jansingh>
Component: DocumentationAssignee: Ranjini M N <rmandyam>
Status: CLOSED WORKSFORME QA Contact: Veera Raghava Reddy <vereddy>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3CC: aschoen, assingh, branto, ceph-eng-bugs, dsavinea, gmeno, gsitlani, kdreyer, lithomas, mhackett, nthomas, rmandyam, tserlin, vereddy, ykaul
Target Milestone: ---   
Target Release: 3.3z8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-30 09:47: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 Janmejay Singh 2020-10-02 10:54:00 UTC 
Description of problem:
'node-exporter' container is not coming online after rolling update (infrastructure-playbooks/rolling_update.yml) from RHCS 3 to RHCS 4 if cephmetrics was deployed in cluster previously.


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

How reproducible:

Steps to Reproduce:
1.Deploy RHCS 3.x cluster along with cephmetrics.
2.Purge cephmetrics. 
3.Configure and Perform rolling update.

Actual results:
'node-exporter' container doesn't come online and service remains in 'activating' state.

Expected results:
'node-exporter' should come online and service should be active.