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 1672799

Summary: [DOC] Red Hat Ceph Storeage Dashboard Installation references incorrect configuration file
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jean-Charles Lopez <jelopez>
Component: DocumentationAssignee: Karen Norteman <knortema>
Status: CLOSED CANTFIX QA Contact: Tejas <tchandra>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1CC: agunn, asriram, jbrier, kdreyer
Target Milestone: z4   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
URL: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/container_guide/monitoring-ceph-clusters-running-in-containers-with-the-red-hat-ceph-storage-dashboard#managing-the-prometheus-environment-container
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-23 12:38:08 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:
Bug Depends On:    
Bug Blocks: 1809203    

Description Jean-Charles Lopez 2019-02-05 23:24:27 UTC
Description of problem:
The container documentation for the Red Hat Ceph Storage Dashboard mentions a configuration file that is incorrect and a configuration method that turns out to be incorrect given the actual configuration file that contains all the configuration.

Version-Release number of selected component (if applicable):
3.1 and 3.2

How reproducible:
Every time

Steps to Reproduce:
1.Connect to your prometheus container
docker exec -it prometheus /bin/bash 
2.List the correct process running
ps -ef | grep prometheus
65534         1      0  0 21:14 ?        00:00:50 /bin/prometheus --config.file=/prometheus/prometheus.yml
65534        32     20  0 23:11 ?        00:00:00 grep prometheus
3.Check the content of the configuration file
cat /prometheus/prometheus.yml
global:
  scrape_interval: 15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']
  - job_name: 'ceph'
    honor_labels: true
    static_configs:
      - targets: ['10.0.1.35:9283']
        labels:
          instance: 'ceph_cluster'
  - job_name: 'node'
    static_configs:
  - job_name: 'cephmetrics'
    static_configs:
      - targets: ['10.0.1.35:9100']
        labels:
          instance: "bstest"

Actual results:
The actual documentation shows the following in chapter 5.5.3
1. Open and edit the /etc/prometheus/prometheus.yml file.
2. Add Ceph targets to the /etc/prometheus/ceph_targets.yml file in the following format.

Expected results:


Additional info:

Comment 1 John Brier 2019-02-06 19:59:30 UTC
Thanks for the report! We'll take a look.

Comment 2 Giridhar Ramaraju 2019-08-05 13:11:35 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 3 Giridhar Ramaraju 2019-08-05 13:12:33 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 4 Giridhar Ramaraju 2019-08-20 07:17:15 UTC
Level setting the severity of this defect to "High" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity