Open jonsattelberger opened 5 months ago
these kinds of error are usually due to mismatch in versions of frontend and backend. I would suggest to doublecheck the packages, make sure repos are set up correctly. one note - we never test ovirt with RHEL 8. It is used for RHV still, but only the RHEL 8.6, not later versions. From our CI tests of oVirt on el8stream (and so likely with RHEL 8.7+ too) we know there are issues due to ansible (at least), and they may or may not be reported as conflicts in package upgrade. could it have messed up your config perhaps?
Is there a specific set of packages I should evaluate? I'll be more than happy to poke around.
sadly i can't assist much more than that:/ perhaps check ovirt-engine-* versions of rpms deployed, and where they come from
@michalskrivanek
I should have searched better. This appears to be a duplicate of https://github.com/oVirt/ovirt-engine/issues/783.
Duplicate of https://github.com/oVirt/ovirt-engine/issues/900
Affected version
I receive a "Status Code: 500" popup whenever I attempt to create a snapshot for a Windows VM from the Administration Portal UI. It doesn't matter if the VM is powered on or off. Nor the OS designation set in the UI (setting Linux or Other...).
The modal usually states: "Operation Canceled" followed by "Error while executing action: A Request to the Server failed with the following Status Code: 500" or "Error while executing query: null". There are at least a dozen popups, and will continue to repeat every few seconds.
The snapshot tab in the Admin Portal UI will then have issues displaying the Active VM and the newly created snapshot entry. If you try to examine both entries, the disk, network, and installed applications might appear blank.
The web inspector will usually contain the following:
The engine logs will have:
File: server.log
The same snapshot will appear fine in the VM Portal. I am able to see the network interfaces, and disks.
No issues creating a snapshot of a Linux-based VM from either UI interfaces.
A clear and concise description of what the bug is
Steps to reproduce the behavior
No internal server error 500 modal / popup