Bug 1209786

Summary: Unclear alert in the Alert event in GUI - " System user root run unlock_entity script on all with db user } "
Product: [Retired] oVirt Reporter: Michael Burman <mburman>
Component: ovirt-engine-webadminAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6CC: bugs, ecohen, gklein, lsurette, mburman, mgoldboi, oourfali, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: 3.6.0-4_alpha3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-04 11:47:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Michael Burman 2015-04-08 08:34:00 UTC
Created attachment 1012082 [details]
screenshot

Description of problem:
Unclear alert in the Alert event in GUI -  " System user root run unlock_entity script on all with db user } "

Not sure what is causing this alert to appear in the Alert event and the alert is not clear at all. 

Version-Release number of selected component (if applicable):
3.6.0-0.0.master.20150406175153.gite240701.el6

Comment 1 Eli Mesika 2015-05-13 07:53:10 UTC
This alert was created as a result of running manually unlock_entity.sh (located under dbutils) in order to force unlocking an entity 

This script should be used with care only when the entity instance is stuck in LOCKED state and nothing can't release it

So, the alert generated is correct IMO 

However, I agree that the message is not clear and will improve it 

is that OK ?

Comment 2 Michael Burman 2015-05-14 10:47:06 UTC
Yes Eli, that is OK

Thank you

Comment 3 Max Kovgan 2015-06-28 14:13:38 UTC
ovirt-3.6.0-3 release

Comment 4 Michael Burman 2015-07-09 10:29:40 UTC
Eli and me decided to improve the alert message bit more, cause this alert can be invoked as well when running engine-setup and not only manual change in the script invoking this alert message.


Tested on -  3.6.0-0.0.master.20150627185750.git6f063c1.el6

engine-setup after upgrade invoked the next message:

"/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh : System user root run manually unlock_entity script on entity [type,id] [all,] with db user engine"

This message will be improved, to let user/admin know what invoked the alert, engine-setup or manual change in the script.

Thanks.

Comment 5 Eli Mesika 2015-07-13 09:52:48 UTC
(In reply to Michael Burman from comment #4)

Fix is :

If script is run from engine-setup, then it uses the -i (implicit) flag and no audit-log alert is generated 

If script is run manually and -i is not used, a alert is generated :

Example :

System user root run manually unlock_entity script on entity [type,id] [all,] with db user engine

Comment 6 Michael Burman 2015-08-04 08:17:41 UTC
- Run unlock_entity script manually on  oVirt Engine Version: 3.6.0_master latest and this invoked alert message in UI:
 'unlock_entity.sh :  System user emesika run manually unlock_entity script on entity [type,id] [all,] with db user engine'

- engine-setup isn't invoking this message alert in UI.
Tested and verified on 3.6.0-0.0.master.20150730085151.git25ae1b5.el6

Comment 7 Sandro Bonazzola 2015-11-04 11:47:24 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.