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
5 days, 7 hours
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
2 weeks, 1 day
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.*
3 weeks, 4 days
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
4 weeks
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 month
Multiple hosts stuck in Connecting state waiting for storage pool to go up.
by ivan.lezhnjov.iv＠gmail.com
Hi!
We have a problem with multiple hosts stuck in Connecting state, which I hoped somebody here could help us wrap our heads around.
All hosts, except one, seem to have very similar symptoms but I'll focus on one host that represents the rest.
So, the host is stuck in Connecting state and this what we see in oVirt log files.
/var/log/ovirt-engine/engine.log:
2023-04-20 09:51:53,021+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ABC010-176-XYZ, VdsIdAndVdsVDSCommandParametersBase:{hostId='2c458562-3d4d-4408-afc9-9a9484984a91', vds='Host[ABC010-176-XYZ,2c458562-3d4d-4408-afc9-9a9484984a91]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: SSL session is invalid
2023-04-20 09:55:16,556+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ABC010-176-XYZ command Get Host Capabilities failed: Message timeout which can be caused by communication issues
/var/log/vdsm/vdsm.log:
2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:31)
2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:37)
2023-04-20 17:48:51,978+0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723)
Both engine.log and vdsm.log are flooded with these messages. They are repeated at regular intervals ad infinitum. This is one common symptom shared by multiple hosts in our deployment. They all have these message loops in engine.log and vdsm.log files. On all
Running vdsm-client Host getConnectedStoragePools also returns an empty list represented by [] on all hosts (but interestingly there is one that showed Storage Pool UUID and yet it was still stuck in Connecting state).
This particular host (ABC010-176-XYZ) is connected to 3 CEPH iSCSI Storage Domains and lsblk shows 3 block devices with matching UUIDs in their device components. So, the storage seems to be connected but the Storage Pool is not? How is that even possible?
Now, what's even more weird is that we tried rebooting the host (via Administrator Portal) and it didn't help. We even tried removing and re-adding the host in Administrator Portal but to no avail.
Additionally, the host refused to go into Maintenance mode so we had to enforce it by manually updating Engine DB.
We also tried reinstalling the host via Administrator Portal and ran into another weird problem, which I'm not sure if it's a related one or a problem that deserves a dedicated discussion thread but, basically, the underlying Ansible playbook exited with the following error message:
"stdout" : "fatal: [10.10.10.176]: UNREACHABLE! => {\"changed\": false, \"msg\": \"Data could not be sent to remote host \\\"10.10.10.176\\\". Make sure this host can be reached over ssh: \", \"unreachable\": true}",
Counterintuitively, just before running Reinstall via Administrator Portal we had been able to reboot the same host (which as you know oVirt does via Ansible as well). So, no changes on the host in between just different Ansible playbooks. To confirm that we actually had access to the host over ssh we successfully ran ssh -p $PORT root(a)10.10.10.176 -i /etc/pki/ovirt-engine/keys/engine_id_rsa and it worked.
That made us scratch our heads for a while but what seems to had fixed Ansible's ssh access problems was manual full stop of all VDSM-related systemd services on the host. It was just a wild guess but as soon as we stopped all VDSM services Ansible stopped complaining about not being able to reach the target host and successfully did its job.
I'm sure you'd like to see more logs but I'm not certain what exactly is relevant. There are a ton of logs as this deployment is comprised of nearly 80 hosts. So, I guess it's best if you just request to see specific logs, messages or configuration details and I'll cherry-pick what's relevant.
We don't really understand what's going on and would appreciate any help. We tried just about anything we could think of to resolve this issue and are running out of ideas what to do next.
If you have any questions just ask and I'll do my best to answer them.
1 month
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 month
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 month
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 month
richiesta accesso Zanata
by Rosario Grasso
Buongiorno,
la presente per richiedere l'accesso a Zanata in lingua inglese e se
possibile anche in italiano.
Saluti,
RG
1 month
