- Users - oVirt List Archives

Hosted-engine restore failing when migrating to new storage domain
by Devin A. Bougie 08 Nov '23

08 Nov '23

Hello, We have a functioning oVirt 4.5.4 cluster running on fully-updated EL9.2 hosts. We are trying to migrate the self-hosted engine to a new iSCSI storage domain using the existing hosts, following the documented procedure: - set the cluster into global maintenance mode - backup the engine using "engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log" - shutdown the engine - restore the engine using "hosted-engine --deploy --4 --restore-from-file=backup.bck" This almost works, but fails with the attached log file. Any help or suggestions would be greatly appreciated, including alternate procedures for migrating a self-hosted engine from one domain to another. Many thanks, Devin

2 9

Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2024
by Piotr Kliczewski 08 Nov '23

08 Nov '23

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 Submit Your Proposal All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org

1 0

Moving hosted-engine to a new cluster
by Ling Ho 08 Nov '23

08 Nov '23

Hello, I set up some new hypervisors recently, created a new cluster using the newer CPU, and migrated all my VMs by changing the cluster and restarting them. Now I have the hosted engine left running in my old cluster. I could not find any recent documentation or discussion on the net. What's the proper way to migrate the hosted engine? I am on oVirt 4.5.4. Thanks, ... ling

1 0

Cannot "Change CD" from VM portal with standard user
by Gianluca Amato 07 Nov '23

07 Nov '23

Hello, I am trying to attach a CD to a virtual machine from the VM Portal as a standard user. When I click on the box for choosing the ISO image, I only get "[Empty]". However, when I access the VM portal as an admin, I correctly see the list of ISO images. I suspect it is a problem of permission: I have assigned to the unprivileged user the UserRole permission both for the VM and the ISO disk images. Am I doing something wrong ? Do I need to assign different roles ? Thanks, --gianluca

2 2

'NoneType' object has no attribute 'data_center'
by marek 07 Nov '23

07 Nov '23

hi, i'm using VM creation through ansible - ovirt 4.5 - name: Creates a new Virtual Machine from template ovirt.ovirt.ovirt_vm: auth: "{{ ovirt_auth }}" state: present cpu_cores: 2 memory: 4GiB name: "{{NAME}}" template: "{{ VM_TEMPLATE }}" comment: "{{comment}}" description: "{{description}}" cluster: "{{CLUSTER}}" type: server high_availability: yes operating_system: rhel_9x64 graphical_console: protocol: - vnc cloud_init_persist: yes nics: - name: enp1s0 profile_name: "{{VLAN1}}" - name: enp2s0 profile_name: "{{VLAN2}}" cloud_init: dns_servers: '1.1.1.1' host_name: "{{NAME}}" user_name: root root_password: "{{ROOT_PASSWORD}}" authorized_ssh_keys: "ssh-ed25519 secret" cloud_init_nics: - nic_name: enp1s0 nic_boot_protocol: static nic_ip_address: "{{PRIVATE_IP}}" nic_netmask: 255.255.255.0 nic_gateway: x.x.x.x - nic_name: enp2s0 nic_boot_protocol: static nic_ip_address: "{{PUBLIC_IP}}" nic_netmask: "{{PUBLIC_NETMASK}}" it works before . double checked input no upgrades/changes any ideas where can be problem? any tips howto debug Marek The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 2694, in main File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py", line 673, in create self.build_entity(), File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 1525, in build_entity File "/tmp/ansible_ovirt.ovirt.ovirt_vm_payload_thzzyp5t/ansible_ovirt.ovirt.ovirt_vm_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py", line 1418, in __get_template_with_version AttributeError: 'NoneType' object has no attribute 'data_center'

1 1

How to start QA and testing work in the oVirt project?
by song_chao＠massclouds.com 06 Nov '23

06 Nov '23

Hello everyone, I am a testing and development engineer who has been working for 10 years. I want to learn and participate in Ovirt's testing work, and make my own contribution. Through learning and understanding, I believe that in the near future, I can also make some contributions to the ovirt community. Currently, I would like some information about QA and testing processes and methods. Can anyone provide me with it? Thank you.

3 4

Missing OVF_STORE disks. Impact and how to recover them?
by ivan.lezhnjov.iv＠gmail.com 06 Nov '23

06 Nov '23

Hi! We have a Local Storage SD (Storage Domain) that is missing both OVF_STORE disks. Clearly this SD is strictly speaking broken but the oVirt Host where this SD is configured and VMs that run on that Host seem to be doing fine. No major problems except for the fact that oVirt Events logs are filled with "VDSM command SetVolumeDescriptionVDS failed: Image path does not exist or cannot be accessed/created" error (and a couple others associated with this one) that is generated every 1 hour. Is this SD in a critical state? Are we risking losing data or anything like that? What is the impact of deleting OVF_STORE disks from an SD? And most importantly is there a way to recover/recreate these OVF_STORE disks?

1 0

Multiple hosts stuck in Connecting state waiting for storage pool to go up.
by ivan.lezhnjov.iv＠gmail.com 06 Nov '23

06 Nov '23

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.

2 4

Is this still an active mailing list?
by vince seavello 06 Nov '23

06 Nov '23

I am attempting to install oVirt Node 4.5.4. I could use a little help with a few setup issues. I'm wondering if this mailing list is still active. I ask because there are several links on the ovirt.org site that are not functional. If this list is still active, I'll give some of the specifics of my system and the issues I'm running into. Vince Seavello Seavello Web Design c: 425.478.9682 f: 425.337.8712 e: vseavello(a)gmail.com

1 0

Re: Extend apache.cer and websocket-proxy.cer
by LS CHENG 04 Nov '23

04 Nov '23

Hi Yes it is generated with engine-setup. How do you extend the certificate validation value in engine-setup? (I am aware that browser can have problems with long duration certificates as explained in https://techbeacon.com/security/google-apple-mozilla-enforce-1-year-max-sec… ) Thanks On Sat, Nov 4, 2023 at 6:39 PM Matej Dujava <ovirt(a)kocurkovo.cz> wrote: > Hi, > > By self signed cert, you mean managed cert generated by ovirt itself > (engine-setup)? > > I found an issue https://bugzilla.redhat.com/show_bug.cgi?id=1824103 where > it's mentioned that safari (maybe other browsers too) have problem with > long self signed CA. Of it's not affecting your clients you can change > values and regenerate cert by engine-setup. > > You can always generate SSL cert by hand (openssl or cfssl ...) and > replace it with following > https://www.ovirt.org/documentation/administration_guide/#Replacing_the_Man… > . > > > On 4 November 2023 14:18:26 CET, LS CHENG <lsc.oraes(a)gmail.com> wrote: > >> Hi again >> >> Forgot to mention that I am using self signed certificates >> >> Thank you >> >> >> >> On Sat, Nov 4, 2023 at 2:07 PM LS CHENG <lsc.oraes(a)gmail.com> wrote: >> >>> Hi all >>> >>> I am running Oracle Linux Virtualization Manager 4.4. >>> >>> The default expiration length for apache.cer and websocket-proxy.cer is >>> 1 year, is there a way to extend them to 10 years? >>> >>> Thank you >>> >>> >>>

2 2