Bug 1148574

Created attachment 943184 [details]
Why can't RHEV help me find this "events" log?

Aharon/Matt -
Please detail steps to reproduce.

It's probably supposed to be engine log, but I'd like to reproduce and make sure.

I can't reproduce, though I do see the message in the code.
From the attached engine.log I do see some more info there, so I'm amending the message to look there instead of the events log.

This is how I tried to reproduce:
1. Detached my export domain.
2. Selected mport EXPORT/NFS domain.
3. Data Center is the same as it was before (and even if not got the same results).
4. Export Path: The same path of the export domain I previously detached.

Results:
message:
Import operation failed. Domain export already exists in the system.

Nothing on events log.

OK, so not detach, but remove+format.
Now reproduces.

So what I gather from this is the following:
When saying the events log, the meaning is indeed the events tab that you opened.
The "more" information there consists of the previous actions that led to this point of failure, nothing more, nothing less.
This should be enough info for the average user.
For the more advanced user, the engine log is the answer, but this is not a place we ordinarily point out to and we're inclined to keep it that way.

Regarding the other suggestions about logging in the system in general, I think this should be an (unrelated) RFE.

So I'm going to close this as not a bug unless pending your response.

What are we expecting to show in the Events area? Looking at Alerts, Events, and Tasks, nothing remotely resembling that error message appears in there. Events is almost entirely log in/log out messages, and a couple low disk space warnings. Alerts has two entries about power management in it. The three Tasks are shown as completing successfully.

There are no logs within the log viewer that are titled "events". I wouldn't consider the Events tab at the bottom a log if it doesn't have a log file.

In the 3.4 Admin Guide, they refer to that area as the Alerts/Events Pane.

Alerts/Events Pane
"The Alerts tab lists all high severity events such as errors or warnings. The Events tab shows a list of events for all resources. The Tasks tab lists the currently running tasks. You can view this panel by clicking the maximize/minimize button."

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Administration_Guide/index.html#Graphical_User_Interface_elements

Filed the RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1154114

I'm not sure how the process differs for RFE vs bug fix though, please feel free to update the bug to match RHEV's standards.

Thanks!

Vered, did you end up changing the string? You said: "From the attached engine.log I do see some more info there, so I'm amending the message to look there instead of the events log."

Normally I would expect the BZ to change to modified if we changed something. Just want to double check we won't tell users to go look at the event log anymore, when it doesn't seem to exist, and that this was updated, and not just closed.

No Matt, I did not. Once I managed to reproduced I added comment #8 saying this is what was meant to be on this scenario, and engine.log is not the solution.

Vered, what did you see in the events pane when you reproduced? As I said in comment 9, there was nothing in there for me that would have been that useful. Maybe in a different environment, it's more useful? Our testing environment is pretty sparse.

If there is no such thing as an events log, and the error is actually trying to point people to the events pane, can we change the wording of the current error message to be more accurate?

(In reply to Matt Reid from comment #13)
> Vered, what did you see in the events pane when you reproduced?
I just saw the previous actions taken in the system, which indeed was not helpful. Then I realized that this is what it was meant to be. Just see the previous actions that took place, and that may give you a hint as to how you got to your present (bad) situation.

> If there is no such thing as an events log, and the error is actually trying
> to point people to the events pane, can we change the wording of the current
> error message to be more accurate?
I agree pane would be more appropriate, but I think this should be a different bug that should address all occurrences of pointing to the event log.
Einav, is there a reason for addressing this as event log and not event pane?

(In reply to Vered Volansky from comment #14)
> (In reply to Matt Reid from comment #13)
> > Vered, what did you see in the events pane when you reproduced?
> I just saw the previous actions taken in the system, which indeed was not
> helpful. Then I realized that this is what it was meant to be. Just see the
> previous actions that took place, and that may give you a hint as to how you
> got to your present (bad) situation.
> 
> > If there is no such thing as an events log, and the error is actually trying
> > to point people to the events pane, can we change the wording of the current
> > error message to be more accurate?
> I agree pane would be more appropriate, but I think this should be a
> different bug that should address all occurrences of pointing to the event
> log.
> Einav, is there a reason for addressing this as event log and not event pane?

depends on where this message is arriving from: if this is a GUI-only message, there is no problem of changing the message to contain "Events pane" instead of "event log". 
if this message arrives from the backend somehow, it means that it can potentially be received in the REST API as well, in which "Events pane" makes no sense; in this case, I would maybe rephrase this to simply "Events" or "Events list".

Matt, will you please open the bug for all events log references in the system according to the assumption that this message can be received by the REST API as well as the GUI, according to Einav's suggestion?

Thanks.

Finally got to it, filed: 1162824