Description of problem: I initiated the Gluster volume profiling on one of the volumes in the RHHI setup. So, when the profiling has begun, and "details" button is clicked, a dialog box opens up with the profiling data, but with an irrelevant message i.e. "Could not fetch brick profile stats" , although it fetch the data for each brick successfully. Version-Release number of selected component (if applicable): qemu-kvm-common-rhev-2.9.0-16.el7_4.8.x86_64 fence-agents-rhevm-4.0.11-66.el7_4.3.x86_64 qemu-img-rhev-2.9.0-16.el7_4.8.x86_64 qemu-kvm-rhev-2.9.0-16.el7_4.8.x86_64 qemu-kvm-tools-rhev-2.9.0-16.el7_4.8.x86_64 glusterfs-3.8.4-44.el7rhgs.x86_64 glusterfs-api-3.8.4-44.el7rhgs.x86_64 glusterfs-cli-3.8.4-44.el7rhgs.x86_64 glusterfs-libs-3.8.4-44.el7rhgs.x86_64 glusterfs-fuse-3.8.4-44.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-44.el7rhgs.x86_64 glusterfs-server-3.8.4-44.el7rhgs.x86_64 gdeploy-2.0.2-14.el7rhgs.noarch glusterfs-geo-replication-3.8.4-44.el7rhgs.x86_64 userspace-rcu-0.7.9-2.el7rhgs.x86_64 How reproducible: Steps to Reproduce: 1. Enter the RHHI setup from frontend, click on volumes tab 2. Select any running volume, and the click on the "Profiling" menu and then start it. 3. Once, it has begun, click on "Profiling" menu and the click the details button. Actual results: Expected results: Additional info:
This bug is already fixed in RHV 4.3 and also verified with RHV 4.3.2 Targetting this bug to RHHI-V 1.6 backlog bugs
Tested with RHV 4.2.7 with glusterfs-3.12.2-45 1. When the brick profiling is started, details can be obtained
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, 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/RHEA-2019:1121