Description of problem:
<UNKOWN> is the string for unauthenticated users in the event tab.
please consider to change to other term
Version-Release number of selected component (if applicable):
this is a general issue on the infra process that logs events into the event tab.
*** Bug 921073 has been marked as a duplicate of this bug. ***
I suggested that <KNOWN> will be renamed to "unknown user to engine" or "non interactive user".
Dan, please advise.
what kind of actions are such users allowed to take?
Dan - we encountered the issue during host registration.
However, this may occur at future cases as well.
So we need to define a "system" user or something like that? Just trying to understand what actions are logged under <UNKNOWN>.
Can this be something done by an actual user, or are these actions performed by internal processes that belong to no real user?
//This is why reproduction steps are always needed in every BZ!
Dan, there are at least two sources in our flows for such events -
a. schedulers that initiate commands - I guess for this "system" can be fine
b. internal queries that initiate commands - register servlet uses an internal queryto avoid the need to login.
Hmm, ok, I am looking at the event log, and I don't see too many events that even mention a user. Can we simply log things that got started without user intervention, and that aren't related to a user session, without a user mentioned at all?
Example (SPm failover):
Storage Pool Manager runs on Host paice (Address: paice.demo.lab.tlv.redhat.com).
No mention of any user starting the SPM on this host, so no need to mention a user at all
Does this make sense, or am I still missing something?
ovirt 3.4.0 alpha has been released
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA