Creating snapshots of Windows VM result in Status Code: 500
by Jon Sattelberger
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:
Fri Dec 22 09:43:07 GMT-500 2023 org.ovirt.engine.ui.frontend.Frontend
SEVERE: Failed to execute runQuery: com.google.gwt.user.client.rpc.StatusCodeException: 500 Internal Server Error The call failed on the server; see server log for details
com.google.gwt.user.client.rpc.StatusCodeException: 500 Internal Server Error The call failed on the server; see server log for details
The engine logs will have:
File: server.log
2023-12-22 09:43:04,387-05 ERROR [io.undertow.servlet] (default task-726) Exception while dispatching incoming RPC call: com.google.gwt.user.client.rpc.SerializationException: Can't find the serialization policy file. This probably means that the user has an old version of the application loaded in the browser. To solve the issue the user needs to close the browser and open it again, so that the application is reloaded.
... snip ...
Caused by: com.google.gwt.user.client.rpc.SerializationException: Type 'org.ovirt.engine.core.common.utils.SecretValue' was not included in the set of types which can be serialized by this SerializationPolicy or its Class object could not be loaded. For security purposes, this type will not be serialized.: instance = ***
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.
I've tried in both Firefox (115.5 ESR) and Google Chrome (latest-ish).
Any thoughts on where to look next?
Version 4.5.6-0 (git12af746179.el8) on RHEL 8.
Thank you,
Jon
1 year, 5 months
Failed to validate GPG signature for ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64
by Jirka Simon
Hello ovirt people,
please cloud you check ovirt-engine-appliance for centos stream 9? it
returns
ERROR ] fatal: [localhost]: FAILED! => {"attempts": 10, "changed":
false, "msg": "Failed to validate GPG signature for
ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64: Public key for
ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64.rpm is not
installed"}
it is possible to install it manually
with dnf -y install ovirt-engine-appliance --nogpgcheck
jirka
1 year, 5 months
Access Problem
by Vittorio
When i try to log in on Ovirt
There is :
"PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed"
Can you help me?
1 year, 5 months
Proxy error when deploying self hosted engine
by dhiabimen＠gmail.com
Hello,
I'm trying to deploy a self hosted engine in a KVM node oracle linux 8.8.
But I have got the following error:
2023-12-21 10:40:43,687+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo using specified url]
2023-12-21 10:40:43,889+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost]
2023-12-21 10:40:44,091+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo]
2023-12-21 10:41:28,976+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'ol8
_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/repodata... [Could not
resolve proxy: www-proxy.us.oracle.com]", 'invocation': {'module_args': {'name': ['oracle-ovirt-release-45-el8'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix'
: False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot'
: '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'sslverify': True,
'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': None,
'attempts': 10, 'changed': False, '_ansible_delegated_vars': {'ansible_host': '192.168.222.75', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}}
2023-12-21 10:41:29,078+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.75]: FAILED! => {"attempts": 10, "changed
": false, "msg"2023-12-21 10:40:43,687+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo using spe
cified url]
2023-12-21 10:40:43,889+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost]
2023-12-21 10:40:44,091+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo]
2023-12-21 10:41:28,976+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'ol8
_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/repodata... [Could not
resolve proxy: www-proxy.us.oracle.com]", 'invocation': {'module_args': {'name': ['oracle-ovirt-release-45-el8'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix'
: False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot'
: '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'sslverify': True,
'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': None,
'attempts': 10, 'changed': False, '_ansible_delegated_vars': {'ansible_host': '192.168.222.75', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}}
2023-12-21 10:41:29,078+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.75]: FAILED! => {"attempts": 10, "changed
": false, "msg": "Failed to download metadata for repo 'ol8_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLin
ux/OL8/baseos/latest/x86_64/repodata/repomd.xml [Could not resolve proxy: www-proxy.us.oracle.com]", "rc": 1, "results": []}
: "Failed to download metadata for repo 'ol8_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLin
ux/OL8/baseos/latest/x86_64/repodata/repomd.xml [Could not resolve proxy: www-proxy.us.oracle.com]", "rc": 1, "results": []}
I have found that " www-proxy.us.oracle.com" is declared in the "dnf.conf" file of the ovirt engine created VM.
How can I deploy the self hosted engine without having this error . Please note that I did not use any proxy.
Thanks,
1 year, 5 months
How restore nodes ovirt UP from NonResponsive and VMs executing
by carlos.mendes＠mgo.cv
Hello,
The node (ovirt2) however is having consistent problems. The follow sequence of events is
reproducible and is causing the host to enter a "NonOperational" state on the
cluster:
* Host ovirt2 installed
* VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused
by communication issues
* Host ovirt2 is not responding. Host cannot be fenced automatically because power
management for the host is disabled.
* Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data
Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:43:22 PM)
* (Banner appears in GUI) Failed Activating Host ovirt2.witsconsult.com
* Failed to connect Host ovirt2 to Storage Pool DataCenter1 (5/27/1912:47:07 PM)
* Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data
Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:47:07 PM)
* Host ovirt2 is not responding. Host cannot be fenced automatically because power
management for the host is disabled. (5/27/1912:47:07 PM)
* VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused
by communication issues (5/27/1912:47:07 PM)
I can then re-activate ovirt2, which appears as green for approximately 5 minutes and
then
repeats all of the above issues.
What can I do to troubleshoot this?
1 year, 5 months
iSCSI Storage Domain Issues - Please Help
by Matthew J Black
Hi Guys & Gals,
So I've been researching this issue online for a couple of days now and I can't seem to find a solution - so I'm hoping you kind people here can help.
We're running oVirt (on Rocky 8, at the moment) with a iSCSI back-end provided by Ceph (Quincy, for the record). Everything from the Ceph-end looks AOK.
However, none of the oVirt Hosts (and therefore the VMs) can connect to the Ceph iSCSI RBD Images (oVirt Storage Domains), and only one or two of the Hosts can log into the Ceph iSCSI Target - the others throw a "Failed to setup iSCSI subsystem" error.
All of the existing iSCSI Storage Domains are in Maintenance mode, and when I try to do *anything* to them the logs spit out a "Storage domain does not exist:" message.
I also cannot create a new iSCSI Storage Domain for a new Ceph pool - again, oVirt simply won't/can't see it, even though it clearly visable in the iSCSI section of the Ceph Dashboard (and in gwcli on the Ceph Nodes).
All of this started happening after I ran an update of oVirt - including an "engine setup" with a full engine-vacuum. Nothing has changed on the Ceph-end.
So I'm looking for help on 2 issues, which or may not be related:
1) Is there a way to "force" oVirt Hosts to log into iSCSI targets? This will mean all of the oVirt Hosts will be connected to all of the Ceph iSCSI Gateways.
2) I'm thinking that *somehow* the existing "Storage Domains" registered in oVirt have become orphaned, so they need to be "cleaned up" - is there a cli way to do this (I don't mind digging into SQL as I'm an old SQL engineer/admin from way back). Thoughts on how to do this - and if it should be done at all?
Or should I simple detach the Storage Domain images from the relevant VMs and destroy the Storage Domains, recreate them (once I can get the oVirt Hosts to log back into the Ceph iSCSI Gateways), and then reattach the relevant images to the relevant VMs? I mean, after all, the data is good and available on the Ceph SAN, so there is only a little risk (as far as I can see) - but there are a *hell* of a lot of VMs to do to do this :-)
Anyway, any and all help, suggestions, gotchas, etc, etc, etc, are welcome. :-)
Cheers
Dulux-Oz
1 year, 5 months
oVirt 4.6 OS versions
by d03＠bornfree.org
Has it yet been decided which OS and version will be used for the oVirt
4.6 Hosted Engine and for 4.6 oVirt Node?
1 year, 5 months
Fresh install ovirt node 4.5.5
by nowak.pawel.mail＠gmail.com
Hi,
I made new install ovirt node and i can't login to www panel using the root account (bad user or password). SSH login works correctly. What may be the problem?
1 year, 5 months
