engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail
by Edward Berger
I was trying to upgrade a hyperconverged oVirt hosted engine and failed in
the engine-setup command with these error and warnings.
...
[ INFO ] Creating/refreshing Engine database schema
[ ERROR ] schema.sh: FATAL: Cannot execute sql command:
--file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql
[ ERROR ] Failed to execute stage 'Misc configuration': Engine schema
refresh failed
...
[ INFO ] Yum Verify: 16/16: ovirt-engine-tools.noarch 0:4.3.3.5-1.el7 - e
[WARNING] Rollback of DWH database postponed to Stage "Clean up"
[ INFO ] Rolling back database schema
...
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
Attaching engine-setup logfile.
1 year, 5 months
Suggestion to switch to nightly
by Sandro Bonazzola
Hi,
As you probably noticed there were no regular releases after oVirt 4.5.4
<https://ovirt.org/release/4.5.4/> in December 2022.
Despite the calls to action to the community and to the companies involved
with oVirt, there have been no uptake of the leading of the oVirt project
yet.
The developers at Red Hat still dedicating time to the project are now
facing the fact they lack the time to do formal releases despite they keep
fixing platform regressions like the recent ones due to the new ansible
changes. That makes a nightly snapshot setup a more stable environment than
oVirt 4.5.4.
For this reason, we would like to suggest the user community to enable
nightly repositories for oVirt by following the procedure at:
https://www.ovirt.org/develop/dev-process/install-nightly-snapshot.html
This will ensure that the latest fixes for the platform regressions will be
promptly available.
Regards,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
1 year, 5 months
Bcp vm
by Ali Gusainov
Hello experts.
Environment:
2 identical servers running
CentOS Linux release 7.7.1908
oVirt Version:4.3.7.2-1.el7
No clusters configured.
NFS share for backups on third server.
Have some questions.
1. Need to create backups of virtual machines to NFS without downtime. Can an 'OVA export' be a complete policy for backups?
2. Is there a way to export vm to OVA via command line?
1 year, 5 months
novnc console error: promise.js missing?
by karl.morgan＠gmail.com
Seeing the following on the engine when attempting to start a novnc console
2023-03-31 11:57:34,988-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] START, SetVmTicketVDSCommand(HostName = ov2node02-mn, SetVmTicketVDSCommandParameters:{hostId='19a92de3-c6e4-4f4e-be31-1d5533a2b6b6', vmId='4481b0e9-a96c-4ee7-8bd2-572558eb9fda', protocol='VNC', ticket='LMl903dd', validTime='120', userName='admin@ovirt', userId='9e88a363-34cb-466a-8ba9-25e46819423b', disconnectAction='LOCK_SCREEN', consoleDisconnectActionDelay='0'}), log id: 1d6520d5
2023-03-31 11:57:35,031-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] FINISH, SetVmTicketVDSCommand, return: , log id: 1d6520d5
2023-03-31 11:57:35,044-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [307c22a9] EVENT_ID: VM_SET_TICKET(164), User admin@ovirt@internalkeycloak-authz initiated console session for VM first
2023-03-31 11:57:35,158-07 INFO [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) [] Can't read file '/usr/share/ovirt-engine/files/novnc/vendor/promise.js' for request '/ovirt-engine/services/files/novnc/vendor/promise.js' -- 404
Curious if this is obvious to anyone? How to resolve?
ovirt-engine-webadmin-portal-4.5.4-1.el9.noarch
ovirt-engine-4.5.4-1.el9.noarch
1 year, 6 months
Ovirt 4.5.0 Support (End of Life Date)
by masood.ahmed＠digital.mod.uk
Hi,
I am working on a project and we would like to utilise (oVirt 4.5.) as the platform for our enterprise infrastructure.
We have arrived at this juncture because of a range of considerations related to hardware and software availability and compatibility.
My question is if there is on-going vendor \ professional support for oVirt moving forward, as one of my colleagues spoke with Red Hat, who stated they are going to end their support for the product.
we will not gain security accreditation for our project unless we have professional support available, community support only is not sufficient,
Any ideas of firms available for a support contract for oVirt 4.5.0?
thanks
1 year, 6 months
Ovirt node disk broken
by marcel d'heureuse
Hi all,
On a single Server the node disk is broken and I have to replace it.
The glusterfs configuration is also gone but the glusterfs directorys are existing on a separate available disk.
Did I have a Chance to install the ovirt Node on a New disk and make the old glusterfs running and also the 7 vms included the hosted engine?
I can also deploy a New hosted engine but can I than import the existing gluster disk from the old Installation?
I have installed the node and also mount the gluster_bricks but to make the volumes available I have not found any command.
It is an ovirt 4.3.10 Installation.
Is there any chance to save some time. The data inside the vms are good to have.
Br
Marcel
1 year, 7 months
Unable to change the admin passsword on oVirt 4.5.2.5
by Ayansh Rocks
Hi All,
Any idea hot to change password of admin user on oVirt 4.5.2.5 ?
Below is not working -
[root@ovirt]# ovirt-aaa-jdbc-tool user password-reset admin
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
Password:
Reenter password:
updating user admin...
user updated successfully
[root@delhi-test-ovirtm-02 ~]#
Above shows successful but password not changed.
Thanks
1 year, 7 months
VDSM certs expired, manual renewal not working
by cen
Hi
Our VDSM certs have expired, both hosts are unassigned and can't be put
into maintenance from UI.
vdsm-client is not working, times out even with --insecure flag. Does
host and port need to be specified when run locally or should defaults work?
Error in console events is: Get Host Capabilities Failed: PKIX path
validation failed...
I followed a RHV guide for this exact situation and generated new vdsm
certificate using the ovirt-engine CA.
The new cert seems identical to the old one, everything matches (algos,
extensions, CA, CN, SAN etc) just new date.
After restarting libvirtd and vdsmd on the host with new cert in place
the host is still not reachable.
However, error message is now slightly different:
get Host Capabilities failed: Received fatal error: certificate_expired
Cert was replaced in the following locations:
/etc/pki/vdsm/certs/vdsmcert.pem
/etc/pki/vdsm/libvirt-spice/server-cert.pem
/etc/pki/libvirt/clientcert.pem
Is there another location missing? What else can I try?
All help appreciated in advance
1 year, 7 months
ovirt 4.5.4 install failure
by Selçuk N
Hello all,
I tried to install ovirt 4.5.4 on ovirt node install.
*hosted-engine --deploy*
After this step installation is stuck.
*[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be
up]*
I checked the log file and details below.
Apr 20 22:10:18 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85405)
Apr 20 22:10:19 ovirt3 python3[51367]: ansible-ovirt_host_info Invoked with
pattern=name=ovirt3.44c.net auth={'token':
'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJOTXdyenhDY284eERxZVlLaFRhWG5xblVpV0lFNDVBM2VmRzhXdndTaDVBIn0.eyJleHAiOjE2ODIwMzQzNzgsImlhdCI6MTY4MjAxNzA5OCwianRpIjoiODdjNDAwZTItNDZiMS00NmY1LTk2MWMtMWJhMDA3MDAxOGQxIiwiaXNzIjoiaHR0cHM6Ly9lbmcuNDRjLm5ldC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZmFiMDNmM2UtODVmZS00YjQ5LWE5ZWItZTExODRjOTYzYzdjIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjYwOWJiMmMxLTJkNTItNDc4Zi1hYzg2LWMyMjVlNTVmYTMwNyIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9lbmcuNDRjLm5ldCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWFwcC1hcGkgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIG92aXJ0LWV4dD10b2tlbi1pbmZvOnB1YmxpYy1hdXRoei1zZWFyY2ggcHJvZmlsZSBvdmlydC1leHQ9dG9rZW46cGFzc3dvcmQtYWNjZXNzIiwic2lkIjoiNjA5YmIyYzEtMmQ1Mi00NzhmLWFjODYtYzIyNWU1NWZhMzA3IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.e47PgAtt_Sj-_4IQ8OIQynAV_AvrOfzalhwi1VJapCQB_sdQqxd0jIH7JGVM1a4TGEJb6E5ffTXBocqQabe5pBPIv4kqsgU1iadyTjjDjZ1elECnahPf6lrze-8hEO92GKFOepGLQ-iu7gRilAknvaXhoc309G1hyQvnP4Q-syffw6Eoo4RmgnLnztnPzsxBtGgkZrzAwFfTNDtdS2uj5lvzzAEIfvDPRFTjJhYwKXSx2hC1lnhXnmv1XEtCfXZZ3qqarXw8GAvOQbe10xklm5UAtu--C8NX32DE6659QtEqk-5g52SdFWIic_OlZ5-obHn3jOllo8qnsb-6mfEn_w',
'url': 'https://eng.44c.net/ovirt-engine/api', 'ca_file': None, 'insecure':
True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None,
'hostname': None, 'username': None, 'password': None} fetch_nested=False
nested_attributes=[] follow=[] all_content=False cluster_version=None
*Apr 20 22:10:22 ovirt3 journal[47971]: Invalid value '-1' for 'cpu.max':
Invalid argument*
Apr 20 22:10:23 ovirt3 sssd_kcm[50811]: Shutting down (status = 0)
Apr 20 22:10:23 ovirt3 systemd[1]: sssd-kcm.service: Deactivated
successfully.
Apr 20 22:10:23 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85400)
Apr 20 22:10:28 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85395)
What did I did wrong?
Thanks.
1 year, 7 months
checking engine vm status during global maintenance
by Alexey Valkov
Hi all,
I tried to check engine status (via hosted-engine --vm-status) during global maintenance in oVirt 4.5.1 and discovered that
it showed me status as it was just before entering global maintenance.
Is it by design? And HA agent doesn't monitor and therefore doesn't update Engine VM status?
If I remember right in oVirt 4.2 hosted-engine --vm-status showed correct status of Engine VM regardless of Global maintenance.
I shutted down the engine but the output of hosted-engine --vm-status was
Engine status : {"vm": "up", "health": "good", "detail": "Up"}
Notice
!! Cluster is in GLOBAL MAINTENANCE mode !!
existed in the output.
Host timestamp and extra metadata was up to date.
All rest info looked good.
Thi is my second attempt to ask the question (first was at 24/04 and still is being moderated).
--
Best regards
Alexei
1 year, 7 months
