Previously, the Events tab in the administration portal logged automated actions as being initiated by "unknown" users. Now, internal actions such as fencing operations are logged as being initiated by the "engine" user.
Description of problem:
Events done by "UNKNOWN" users are logged into Events tab for Hosts
Host aaa.bbb.ccc.ddd was started by <UNKNOWN>
Host aaa.bbb.ccc.ddd was stopped by <UNKNOWN>
The Events sould be descriptive as much as we can, and this message is not.
How reproducible:
The start and the stop actions are done via the ART framework.
Steps to Reproduce:
Run the Host automation test which includes some power management tests.
Actual&expected results:
instead of <UNKNOWN> should be by admin
Additional info:
In the log below attached the messages with the correlation id 3e479eeb which are related to the message ...Stopped by <UNKNOWN>
Messages from log:
=================
2012-10-02 17:50:57,863 INFO [org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand] (pool-4-thread-48) Running command: VdsNotRespondingTreatmentCommand internal: true. Entities affec
ted : ID: 661b89e0-0ca6-11e2-a084-001a4a1697ca Type: VDS
2012-10-02 17:50:57,889 INFO [org.ovirt.engine.core.bll.StopVdsCommand] (pool-4-thread-48) [3e479eeb] Running command: StopVdsCommand internal: true. Entities affected : ID: 661b89e0-0ca6-
11e2-a084-001a4a1697ca Type: VDS
2012-10-02 17:50:57,903 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-48) [3e479eeb] START, SetVdsStatusVDSCommand(HostName = puma39.scl.lab.tlv.redhat.com, H
ostId = 661b89e0-0ca6-11e2-a084-001a4a1697ca, status=Reboot, nonOperationalReason=NONE), log id: 1fc8dc49
2012-10-02 17:50:57,976 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-48) [3e479eeb] FINISH, SetVdsStatusVDSCommand, log id: 1fc8dc49
2012-10-02 17:50:58,000 INFO [org.ovirt.engine.core.bll.FencingExecutor] (pool-4-thread-48) [3e479eeb] Executing <Stop> Power Management command, Proxy Host:puma40.scl.lab.tlv.redhat.com, A
gent:ipmilan, Target Host:puma39.scl.lab.tlv.redhat.com, Management IP:puma39-mgmt.scl.lab.tlv.redhat.com, User:admin, Options:
2012-10-02 17:50:58,001 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (pool-4-thread-48) [3e479eeb] START, FenceVdsVDSCommand(HostName = puma40.scl.lab.tlv.redhat.com,
HostId = 669f63a0-0ca6-11e2-a42f-001a4a1697ca, targetVdsId = 661b89e0-0ca6-11e2-a084-001a4a1697ca, action = Stop, ip = puma39-mgmt.scl.lab.tlv.redhat.com, port = , type = ipmilan, user = ad
min, password = ******, options = ''), log id: 60531053
2012-10-02 17:50:58,050 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (pool-4-thread-48) [3e479eeb] FINISH, FenceVdsVDSCommand, return: Done, log id: 60531053
2012-10-02 17:50:58,050 INFO [org.ovirt.engine.core.bll.FenceVdsBaseCommand] (pool-4-thread-48) [3e479eeb] Waiting for vds puma39.scl.lab.tlv.redhat.com to stop
2012-10-02 17:51:03,051 INFO [org.ovirt.engine.core.bll.FenceVdsBaseCommand] (pool-4-thread-48) [3e479eeb] Attempt 1 to get vds puma39.scl.lab.tlv.redhat.com status
2012-10-02 17:51:03,076 INFO [org.ovirt.engine.core.bll.FencingExecutor] (pool-4-thread-48) [3e479eeb] Executing <Status> Power Management command, Proxy Host:puma40.scl.lab.tlv.redhat.com,
Agent:ipmilan, Target Host:puma39.scl.lab.tlv.redhat.com, Management IP:puma39-mgmt.scl.lab.tlv.redhat.com, User:admin, Options:
2012-10-02 17:51:03,077 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (pool-4-thread-48) [3e479eeb] START, FenceVdsVDSCommand(HostName = puma40.scl.lab.tlv.redhat.com,
HostId = 669f63a0-0ca6-11e2-a42f-001a4a1697ca, targetVdsId = 661b89e0-0ca6-11e2-a084-001a4a1697ca, action = Status, ip = puma39-mgmt.scl.lab.tlv.redhat.com, port = , type = ipmilan, user =
admin, password = ******, options = ''), log id: 784e8354
2012-10-02 17:51:05,233 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (pool-4-thread-48) [3e479eeb] FINISH, FenceVdsVDSCommand, return: Test Succeeded, Host Status is:
off, log id: 784e8354
2012-10-02 17:51:05,233 INFO [org.ovirt.engine.core.bll.FenceVdsBaseCommand] (pool-4-thread-48) [3e479eeb] vds puma39.scl.lab.tlv.redhat.com status is off
Hello,
One of my customers would like to confirm if the fix for the <UNKNOWN> entries extends to the following types of messages as well or just the starting/stopping messages we see in the bug description:
--------------
Type 316:
User USERNAME attach to VM <UNKNOWN> in VM Pool POOLNAME was initiated by USERNAME.
Type 506:
VM VMNAME was restarted on Host <UNKNOWN>
--------------
Thanks!
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.
http://rhn.redhat.com/errata/RHSA-2013-0888.html