Description of problem: When user starts and stops profiling on a volume there are no event messages generated. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150105124153.git669ddc1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a volume and start it 2. Select the volume and click on "Profiling->start" 3. Once profiling has been started click on "Profiling->stop". Actual results: There are no event messages generates when volume profiling starts and stops. Expected results: Event messages should be generated when volume profiling starts and stops. Additional info:
Verified and works with build ovirt-engine-3.6.0-0.0.master.20150429182702.git939c2e8.el6.noarch. Following event message gets displayed when user starts profiling on a volume: 1) Gluster volume <vol_name> Profile started. 2) Detected new option diagnostics.count.fop-hits=on on volume <vol_name> of cluster <cluster_name> and added it to engine DB. 3) Detected new option diagnostics.latency.measurement=on on volume <vol_name> of cluster <cluster_name> and added it to engine DB. Following event message gets displayed when user stops profiling on volume. 1) Gluster volume <vol_name> Profile stopped. 2) Detected new option diagnostics.count.fop-hits=on reset on volume <vol_name> of cluster <cluster_name> and added it to engine DB. 3) Detected new option diagnostics.latency.measurement=on reset on volume <vol_name> of cluster <cluster_name> and added it to engine DB.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.