Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1184397

Summary:	[New] - No event messages are generated when user starts and stops volume profiling
Product:	[Retired] oVirt	Reporter:	RamaKasturi <knarra>
Component:	ovirt-engine-webadmin	Assignee:	anmol babu <anbabu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5	CC:	bugs, dpati, ecohen, gklein, lsurette, mgoldboi, rbalakri, rhsc-qe-bugs, sabose, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150429182702.git939c2e8.el6.noarch	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 13:54:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1187461

Description RamaKasturi 2015-01-21 10:03:26 UTC

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:

Comment 1 RamaKasturi 2015-05-13 12:39:24 UTC

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.

Comment 2 Sandro Bonazzola 2015-11-04 13:54:07 UTC

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.