Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visiblity of VM events #1365

Open
TimmiORG opened this issue Feb 5, 2021 · 5 comments · Fixed by #1592
Open

Visiblity of VM events #1365

TimmiORG opened this issue Feb 5, 2021 · 5 comments · Fixed by #1592

Comments

@TimmiORG
Copy link

TimmiORG commented Feb 5, 2021

VM Portal version number: 1.6.6-1

oVirt version number: 4.4.4

Feature enhancement request:
It would be very helpful if it would be possible to see the event log for the selected VM also in the VM portal.
For example who powered it down and when. Or who did revert a snap shot etc.

Please let me know if you need more information on that.

Best regards
Christoph

@sgratch
Copy link
Member

sgratch commented Feb 8, 2021

@TimmiORG You can view part of the events within the notification drawer of the VM portal, but only those triggered by the VM portal actions and that are assigned to the logged user. Supporting other async/progress events are a bit more complicated to implement.
Please check d/s bug already opened on this:
https://bugzilla.redhat.com/show_bug.cgi?id=1886211

@TimmiORG
Copy link
Author

TimmiORG commented Feb 8, 2021

@sgratch
Thank you for the response. I will put my self on CC on that ticket.
This is exactly what I'm looking for. I just thought here is the right place to open such ticket for the VM portal.
So you can close this one if you like.

@sgratch
Copy link
Member

sgratch commented Feb 8, 2021

@TimmiORG this is definitely the right place for tracking of web-ui u/s issues. The Bugzilla is used as a tracker for d/s issues only.
So I'll leave this issue open for now as well. Thanks.

@rszwajko rszwajko linked a pull request Jun 9, 2022 that will close this issue
@sgratch sgratch reopened this Jun 17, 2022
@TimmiORG
Copy link
Author

Closed with #1592

@sgratch
Copy link
Member

sgratch commented Nov 12, 2023

This issue was not completed as done since #1592 was reverted by #1604 due to the reason mentioned in #1604 (comment)

@sgratch sgratch reopened this Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants