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
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 ?
Yes Eli, that is OK Thank you
ovirt-3.6.0-3 release
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.
(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
- 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
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.