- Users - oVirt List Archives

how to fix time-drift on el8 hosts?
by Nathanaël Blanchet 10 Jan '21

10 Jan '21

Hello, Engine complains about my fresh el8 ovirt 4.4.3 node host: "Host hadriacus has time-drift of 3202 seconds while maximum configured value is 300 seconds." I tried to fix it with these commands: sudo chronyc -a makestep chronyc sources chronyc tracking ... but the host is still not synchronized. How should I proceed? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

6 5

Restore failed. Not possible to manage storage domain 'hosted_storage'
by Alexey Nikolaev 10 Jan '21

10 Jan '21

Hi community! I have issue when trying to restore 4.3.10.4 hosted engine. [ ERROR ] Exception: Not possible to manage storage domain 'hosted_storage'. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Not possible to manage storage domain 'hosted_storage'."} This error occurs with both Glusterfs and NFS shared storage. engine setup ansible create storage domain log https://gist.github.com/virtio-technique/38a3678b834017f3e4cd9c03f6811e71 vdsm log https://gist.github.com/virtio-technique/8c5ad1ce0e2f07d98d61a964744adff9 hosted engine setup log https://gist.github.com/virtio-technique/00230b117cf8ee1b1a094c1001f424bd Can I use a hosted engine backup file to restore the manager to a dedicated server and manually delete the hosted engine domain?

2 1

Timeout in "Add HE disks" task
by Jiří Sléžka 09 Jan '21

09 Jan '21

Hello, I am trying to upgrade RHV4.3.10 (standalone) to RHV4.4.3 (HE) in one step which is probably not supported but in case of our oVirt cluster it worked well. I am using hosted-engine --deploy with answer file hosted-engine --deploy --restore-from-file=backup/backup.tar --config-append=answer-file_pontus.txt I can pass until this task [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add HE disks] then ansible fails with a "Timeout exceed while waiting on result state of the entity." In the engine I can see that he_virtio_disk is successfuly created and in OK state but he_sanlock is in LOCKED state. Shared storage domain is FC. Here is part of ovirt-hosted-engine-setup-ansible-create_target_vm.log ... { "_ansible_item_label": { "content": "hosted_engine_sanlock", "description": "Hosted-Engine sanlock disk", "format": "raw", "name": "he_sanlock", "size": "1GiB", "sparse": false }, "_ansible_no_log": false, "ansible_loop_var": "item", "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk.py\", line 802, in main\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/redhat/rhv/plugins/module_utils/ovirt.py\", line 652, in create\n poll_interval=self._module.params['poll_interval'],\n File \"/tmp/ansible_ovirt_disk_payload_sy1l4b1p/ansible_ovirt_disk_payload.zip/ansible_collections/redhat/rhv/plugins/module_utils/ovirt.py\", line 370, in wait\n raise Exception(\"Timeout exceed while waiting on result state of the entity.\")\nException: Timeout exceed while waiting on result state of the entity.\n", "failed": true, ... Do have anybody an idea where could be problem? Thanks in advance, Jiri

1 0

LXD or LXC Container Host
by Tarun Kushwaha 09 Jan '21

09 Jan '21

is it possible to manage LXD Host from ovirt cluster or any possibility to this features in near future.?

1 0

[ANN] Async release for ovirt-engine is now available
by Sandro Bonazzola 08 Jan '21

08 Jan '21

The oVirt Team has just released a new version of ovirt-engine package (4.4.4.7) that fixes a few important bugs: - [BZ 1894454](https://bugzilla.redhat.com/1894454) - VM fails to boot when moved to a cluster with a different chipset - [BZ 1908643](https://bugzilla.redhat.com/1908643) - ovirt-backend contains jar that should not be there - [BZ 1576923](https://bugzilla.redhat.com/1576923) - RFE: Ability to move master role to another domain without putting the domain to maintenance - [BZ 1911597](https://bugzilla.redhat.com/1911597) - Block manually switch master domain for Gluster domains fixes also security issue: CVE-2020-35497 ( https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35497) - Moderate - ovirt-engine: non-admin user is able to access other users public SSH key -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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 0

QEMU error qemuDomainAgentAvailable in /var/log/messages
by souvaliotimaria＠mail.com 08 Jan '21

08 Jan '21

Hello everyone and a happy new year! I have a question which might be silly but I am stumped. I keep getting the following error in my /var/log/messages Jan 5 12:20:30 ovno3 libvirtd: 2021-01-05 10:20:30.481+0000: 5283: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected This entry appears on the arbitrary node only and it has a recurrence of 5 minutes. I have GlusterFS on the ovirt environment (production environment) and it's serving several vital services. The VMs are running ok and I haven't noticed any discrepancy. Almost a week ago there was a disconnection on the gluster storage but since then everything works as expected. Does anyone know what this error is and if there is a guide or something to fix it? I have no idea what to search and where. Thank you all very much for your time!

2 2

how to build oVirt engine on eclipse?
by Henry lol 07 Jan '21

07 Jan '21

hello, I've just only imported existing maven projects from engine's git, but there were so many errors and failed to build. Should I do some configurations before importing?

2 1

Re: VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Nir Soffer 07 Jan '21

07 Jan '21

On Thu, Jan 7, 2021, 16:48 Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: ... > *2020-12-08 10:18:35,451+01 INFO > [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] > (ForkJoinPool-1-worker-31) [] VM > '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'* > *2020-12-08 10:18:35,466+01 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is > down with error. Exit message: Lost connection with qemu process.* > Looks like qemu crashed when stopping the backup. Can you file a bug for this, and attach logs? We these logs from host the vm was running on: - /var/log/vdsm/vdsm.log (the right log showing the time backup was stopped) - /var/log/ovirt-imageio/daemon.log - /var/log/libvirt/libvird.log (may be missing) - /var/log/libvirt/qemu/<vm-name>.log Also the vm xml (virsh -r dumpxml vm-name). ... > The environment of faulty host is: > OS Version: RHEL - 8.3 - 1.0.el8 > OS Description: Red Hat Enterprise Linux 8.3 (Ootpa) > Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 > KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69 > LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5 > I never had any issue with these version: # rpm -q libvirt-daemon qemu-kvm libvirt-daemon-6.6.0-8.module+el8.3.1+8648+130818f2.x86_64 qemu-kvm-5.1.0-13.module+el8.3.0+8424+e82f331d.x86_64 Looks like you run older libvirt version, but have newer qemu version. Where did you got these packages? Are you running on RHEL or Centos? Nir

1 0

VMs shut down after backup: "moved from 'Up' --> 'Down'" only on RHEL hosts
by Łukasz Kołaciński 07 Jan '21

07 Jan '21

Hello, I still haven't solved the problem with vms turning off. The original message: We have RHV manager with several different hosts. After the backup, vm placed on RHEL shuts down. In engine.log I found where this happen: "VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down'". I attached whole logs to email. It doesn't matter if it's a full or incremental, results are always the same. RHVH hosts works properly. Log fragment: 2020-12-08 10:18:33,845+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-76) [60da31e3-92f6-4555-8c43-2f8afee272e0] Updating image transfer 87bdb42e-e64c-460d-97ac-218e923336a1 (image e57e4af0-5d0b-4f60-9e6c-e217c666e5e6) phase to Finalizing Success 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Running command: StopVmBackupCommand internal: false. Entities affected : ID: 35183baa-1c70-4016-b7cd-528889876f19 Type: VMAction group BACKUP_DISK with role type ADMIN, ID: e57e4af0-5d0b-4f60-9e6c-e217c666e5e6 Type: DiskAction group BACKUP_DISK with role type ADMIN 2020-12-08 10:18:33,940+01 INFO [org.ovirt.engine.core.bll.StopVmBackupCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] Stopping VmBackup 'aae03819-cea6-45a1-9ee5-0f831af8464d' 2020-12-08 10:18:33,952+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] START, StopVmBackupVDSCommand(HostName = rhv-2, VmBackupVDSParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', backupId='aae03819-cea6-45a1-9ee5-0f831af8464d'}), log id: 78b2c27a 2020-12-08 10:18:33,958+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.StopVmBackupVDSCommand] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] FINISH, StopVmBackupVDSCommand, return: , log id: 78b2c27a 2020-12-08 10:18:33,975+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-76) [89ec1a77-4b46-42b0-9d0f-15e53d5f952a] EVENT_ID: VM_BACKUP_FINALIZED(10,794), Backup <UNKNOWN> for VM stor2rrd finalized (User: admin@internal-authz). 2020-12-08 10:18:35,221+01 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-73) [] User admin@internal successfully logged out 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-81) [1b35276c] Running command: TerminateSessionsForTokenCommand internal: true. 2020-12-08 10:18:35,236+01 INFO [org.ovirt.engine.core.bll.aaa.SessionDataContainer] (default task-81) [1b35276c] Not removing session '90TxdK0PBueLijy+sCrFoHC/KNUGNzNpZuYMK/yKDAkbAefFr+8wOJsATsDKv18LxpyxCl+eX7hTHNxN23anAw==', session has running commands for user 'admin@internal-authz'. 2020-12-08 10:18:35,447+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19' was reported as Down on VDS 'afad6b8b-78a6-4e9a-a9bd-783ad42a2d47'(rhv-2) 2020-12-08 10:18:35,448+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] START, DestroyVDSCommand(HostName = rhv-2, DestroyVmVDSCommandParameters:{hostId='afad6b8b-78a6-4e9a-a9bd-783ad42a2d47', vmId='35183baa-1c70-4016-b7cd-528889876f19', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-31) [] FINISH, DestroyVDSCommand, return: , log id: 4f473135 2020-12-08 10:18:35,451+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-31) [] VM '35183baa-1c70-4016-b7cd-528889876f19'(stor2rrd) moved from 'Up' --> 'Down' 2020-12-08 10:18:35,466+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-31) [] EVENT_ID: VM_DOWN_ERROR(119), VM stor2rrd is down with error. Exit message: Lost connection with qemu process. 2020-12-08 10:18:35,484+01 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-34085) [3da40159] Running command: ProcessDownVmCommand internal: true. The environment of faulty host is: OS Version: RHEL - 8.3 - 1.0.el8 OS Description: Red Hat Enterprise Linux 8.3 (Ootpa) Kernel Version: 4.18.0 - 240.1.1.el8_3.x86_64 KVM Version: 5.1.0 - 14.module+el8.3.0+8438+644aff69 LIBVIRT Version: libvirt-6.6.0-7.module+el8.3.0+8424+5ea525c5 VDSM Version: vdsm-4.40.26.3-1.el8ev SPICE Version: 0.14.3 - 3.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: openvswitch-2.11-7.el8ev Nmstate Version: nmstate-0.3.4-13.el8_3 Regards, Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

1 0

Spliting login pages
by ozmen62＠hotmail.com 07 Jan '21

07 Jan '21

Hi, We want to split admin, user and grafana login pages. As you know all in main page. So, this might get users attention and they may try to login and get their accounts locked or worse :) Thanks

4 7