Raised bug 1598344, in 3.1 for issue observed in comment #4
Ignore my previous comment #9.
The doc text from comment #8, lgtm
"The 'iSCSI Overview' Grafana page does not behave correctly When using the Red Hat Ceph Storage metrics Dashboard, the 'iSCSI Overview' Grafana page does not display any graphs or values as it is expected to"
The issue seems to be that cephmetrics-ansible is expecting a [iscsis] section in ansible inventory file while the RHCS block device guide states this section should be called [iscsigws]. Adding a [iscsis] section is enough to have the prometheus-node-exporter package correctly installed on iSCSI targets and metrics recorded and exposed on iSCSI Grafana dashboards.
You can refer to these 2 commits from Zack:
And the RHCS block device guide:
great catch! We should probably fix that for 3.2 or document your workaround. Zack, what do you think?
Zack would you please let us know the status of this?
*** Bug 1656053 has been marked as a duplicate of this bug. ***
*** Bug 1515153 has been marked as a duplicate of this bug. ***
Regarding case : #02337240
Customer is facing the same issue. May I please know the status of this bug. Or can we provide any workaround possibly?
Waiting for response!
A workaround would be to have both [iscsis] as well as [iscsigws] sections in the ansible hosts file.
Hello Boris ,
Thank you for the reply. I will suggest this workaround to the customer.
I have a question. If we mention both [iscsis] as well as [iscsigws] in ansible hosts file, customer will need to run site.yml (or site-docker.yml) playbook. Playbook can be run using --limit option. So, the question is, when using --limit option what command will be right?
#ansible-playbook site.yml --limit iscsigws OR
#ansible-playbook site.yml --limit iscsis
I would say this one: ansible-playbook site.yml --limit iscsis,iscsigws
If you are talking site.yml as in ceph-ansible then that should support iscsigws. For the cephmetrics-ansible (playbook.yml), you should use iscsis. Alternatively, you can use the syntax as suggested in the above comment, that should be the safest option and can be used for both ceph-ansible as well as cephmetrics-ansible.
The customer was already aware of work around. And I asked if it is worked for him. But apparently it is not working for him. May I please know if we have some other way to provide to the customer?
they only need to re-deploy cephmetrics after they have both iscsis and iscsigws in their ansible/hosts file. Re-deploying cephmetrics is generally less heavy than doing a full ceph deployment. It would be nice if they could re-run the full cephmetrics-ansible deployment scripts (without any --limit options). If that won't work then I would suggest purging the old cephmetrics installation and then doing a full re-deployment.
The deployment playbook should be located at
The purge playbook should be located at
I will check with the customer regarding purging the old cephmetrics installation. Thank you for your reply.
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.