March 2021 - Users - Ovirt List Archives

What would be the process to restore master host.

by miguel.garcia＠toshibagcs.com

We have a cluster with one master and 3 ovirt-nodes and the master server got the hard disk fried however the vms are still running and working in shape. We have concerns if restore master by reinstall OS and restore from latest ovirt backup would be enough or if we had to resintall ovirt cluster from scratch along with each node. Thanks in advance for your input.

3 years, 9 months

2
2
0 / 0

Networking

by Jason Alexander Hazen Valliant-Saunders

I'm trying to create vlans to mirror my vlans on my external switch. is there a simple way to simply define a port trunk and have ovirt engine pass the traffic on? In VMWare; this can be accomplished by nic teaming/trunking (802.3 ad) and then pass the traffic to the switch. From what I have read in oVirt I need to define ovs switches first; I'd like to simply pass L2 to the switch directly. Regards, Hazen

3 years, 9 months

3
5
0 / 0

Host Add - Host not found check DNS or /etc/hosts

by penguin pages

Fresh install CentOS8 Streams. Gluster wizard runs and deploys. Engine installs on node. I copy over /etc/hosts for primary site resources to ovirt engine so it can find primary cluster nodes without DNS being booted / up at that time. I check ovirt engine can ssh to the three nodes... so as root I generate SSH key and do ssh-copy-id to all three nodes. So as much as I can validate communication is working.. i have. When I "add host" -> use FDN -> input root password But it shows up in GUI host list with "install fails" Only message is : [root@ovirt01 ~]# cat /var/log/ovirt-engine/ansible-runner-service.log 2021-03-18 09:44:15,998 - runner_service.controllers.hosts - DEBUG - Adding host odin.penguinpages.local to group ovirt 2021-03-18 09:44:16,344 - runner_service.services.hosts - ERROR - SSH - NOCONN:SSH error - 'odin.penguinpages.local' not found; check DNS or /etc/hosts 2021-03-18 10:07:15,970 - root - INFO - Analysing local configuration options from /etc/ansible-runner-service/config.yaml 2021-03-18 10:07:15,975 - root - INFO - - setting playbooks_root_dir to /usr/share/ovirt-engine/ansible-runner-service-project 2021-03-18 10:07:15,975 - root - INFO - - setting ssh_private_key to /etc/pki/ovirt-engine/keys/engine_id_rsa 2021-03-18 10:07:15,975 - root - INFO - - setting port to 50001 2021-03-18 10:07:15,975 - root - INFO - - setting target_user to root 2021-03-18 10:07:15,975 - root - INFO - - setting log_path to /var/log/ovirt-engine 2021-03-18 10:07:15,975 - root - INFO - Analysing runtime overrides from environment variables 2021-03-18 10:07:15,975 - root - INFO - No configuration settings overridden 2021-03-18 10:07:15,995 - root - INFO - Loaded logging configuration from /etc/ansible-runner-service/logging.yaml 2021-03-18 10:07:16,004 - runner_service.controllers.hosts - DEBUG - Request received, content-type :None 2021-03-18 10:07:16,005 - runner_service.controllers.hosts - INFO - 127.0.0.1 - GET /api/v1/hosts/thor.penguinpages.local 2021-03-18 10:07:16,013 - runner_service.controllers.hosts - DEBUG - Request received, content-type :application/json; charset=UTF-8 2021-03-18 10:07:16,013 - runner_service.controllers.hosts - INFO - 127.0.0.1 - POST /api/v1/hosts/thor.penguinpages.local/groups/ovirt 2021-03-18 10:07:16,013 - runner_service.controllers.hosts - DEBUG - additional args received 2021-03-18 10:07:16,014 - runner_service.controllers.hosts - DEBUG - Adding host thor.penguinpages.local to group ovirt 2021-03-18 10:07:16,339 - runner_service.services.hosts - ERROR - SSH - NOCONN:SSH error - 'thor.penguinpages.local' not found; check DNS or /etc/hosts 2021-03-18 10:07:38,333 - runner_service.controllers.hosts - DEBUG - Request received, content-type :None 2021-03-18 10:07:38,334 - runner_service.controllers.hosts - INFO - 127.0.0.1 - GET /api/v1/hosts/thor.penguinpages.local 2021-03-18 10:07:38,339 - runner_service.controllers.hosts - DEBUG - Request received, content-type :application/json; charset=UTF-8 2021-03-18 10:07:38,339 - runner_service.controllers.hosts - INFO - 127.0.0.1 - POST /api/v1/hosts/thor.penguinpages.local/groups/ovirt 2021-03-18 10:07:38,339 - runner_service.controllers.hosts - DEBUG - additional args received 2021-03-18 10:07:38,340 - runner_service.controllers.hosts - DEBUG - Adding host thor.penguinpages.local to group ovirt 2021-03-18 10:07:38,713 - runner_service.services.hosts - ERROR - SSH - NOCONN:SSH error - 'thor.penguinpages.local' not found; check DNS or /etc/hosts But ssh is fine to all hosts works fine. [root@ovirt01 ~]# ssh thor.penguinpages.local Web console: https://thor.penguinpages.local:9090/ or https://172.16.100.101:9090/ Last login: Wed Mar 17 11:27:34 2021 from 172.16.101.103 [root@thor ~]# exit logout Connection to thor.penguinpages.local closed. [root@ovirt01 ~]# ssh medusa.penguinpages.local Activate the web console with: systemctl enable --now cockpit.socket Last login: Thu Mar 18 10:06:40 2021 from 172.16.100.186 [root@medusa ~]# exit logout Connection to medusa.penguinpages.local closed. [root@ovirt01 ~]# ssh odin.penguinpages.local Activate the web console with: systemctl enable --now cockpit.socket Last login: Wed Mar 17 16:02:46 2021 from 172.16.100.186 [root@odin ~]# exit logout Connection to odin.penguinpages.local closed. [root@ovirt01 ~]#

3 years, 9 months

2
1
0 / 0

Quick Question: Degraded Gluster

by Christian Reiss

Hey folks, quick question: I have a 3 node cluster (HC) in a production environment. I recently swapped all the storage SSDs with bigger enterprise grades SSDs. So I took a host down (migrating all VMs away, maintenance, shutdown, fix raid, gluster repair, back online). This worked well and all three nodes are now hardware-wise replaced. The last one is still gluster-healing (roughly 20% done). The other two nodes are happily serving the vms while the third one is still in maintenance. my question is: Can I online the maintenance node while gluster is still healing? Or will will open up a can of worms I would not like? It would be cool having all three nodes back online soon while the gluster is still repairing. We have no urge tho. If there is a risk I would wait. If this is somewhat risk-free and do-able why not :) -- with kind regards, mit freundlichen Gruessen, Christian Reiss

3 years, 9 months

2
1
0 / 0

Upgrading DWH from 4.4.4 to 4.4.5

by Nur Imam Febrianto

Hi, I’m currently trying to upgrade my oVirt Cluster into 4.4.5. Hosted engine upgrade work successfully. But whenever I tried upgrading DWH on separate machine it keep giving me this error : Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' In engine-setup log : 2021-03-18 23:34:10,976+0700 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/apache/selinux.py", line 40, in _misc osetupcons.SystemEnv.SELINUX_BOOLEANS KeyError: 'OVESETUP_SYSTEM/selinuxBooleans' 2021-03-18 23:34:10,977+0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' Using CentOS 8.3 as separate DWH machine. Anybody maybe can help me ? Thanks before. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

3 years, 9 months

1
0
0 / 0

oVirt 4.4.5 is now generally available

by Lev Veyde

oVirt 4.4.5 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.5 , as of March 18th, 2021. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXE... ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.5 Release? This update is the fifth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - oVirt Node (based on CentOS Linux 8.3) - CentOS Stream (tech preview) oVirt Node and Appliance have been updated, including: - oVirt 4.4.5: https://www.ovirt.org/release/4.4.5/ - Ansible 2.9.18: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v... - Advanced Virtualization 8.3.1 - Gluster 8.4: https://docs.gluster.org/en/latest/release-notes/8.4/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.5 release highlights: https://www.ovirt.org/release/4.4.5/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.5/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 years, 9 months

1
0
0 / 0

4.4.5 released? Fails to upgrade

by Rik Theys

Hi, My systems pulled in 4.4.5 packages last night, so I assume oVirt 4.4.5 was released? The release notes page does not list the release and I also did not see any announcement. The packages are 4.4.5.10-1.el8. I ran an engine-setup and upgraded to this release but the upgrade has failed due to a failure to update the database schema and it seems the rollback was not successful as my instance failed to start afterwards. I've downgraded all packages and ran engine-setup --offline, which seems to at least bring back my engine to a working state. I'm confused: has 4.4.5 been released or did I pull in some intermediate version with known issues? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>>

3 years, 9 months

3
3
0 / 0

Python SDK rename virtual machine

by Gerard Weatherby

Is there an API call in the Ovirt Python SDK to rename an existing virtual machine?

3 years, 9 months

2
2
0 / 0

Migrate windows 2003 server 64bits from libvirt to ovirt

by Fernando Hallberg

Hi, I have a VM with 2003 server x64, and I upload the vm image to oVirt. The VM boot on the oVirt, but, the blue screen appear with a error message: [image: image.png] Anybody has some information about this? I try to convert de img file from raw to qcow2, but the error persists. Regards, Fernando Hallberg

3 years, 9 months

5
8
0 / 0

Access to the internet from oVirt VMs

by unityresearcher＠alterpost.org

Hi to all ✋😉 I've stacked with ovirt's vm network routing Infrastructure: 1. stansalone ovirt engine (hetzner cloud vm) 2. ovirt node (hetzner robot, dedicated server) 3. hetzner private cloud network. Both Engine and Node are connected to private network. For node the network is built on external NIC's tagged VLAN https://docs.hetzner.com/robot/dedicated-server/network/vswitch/ 4. Also there is a pfsense router vm in private network So my purpose is to grant access to the internet from VM inside oVirt via pfSense. Additional info: 1. pfsense machine is pingable from oVirt VM 2. oVirt VM NIC – ovirtmgmt 3. pfsenses' NAT works fine for machines in hetzner cloud 4. Painful troubleshooting showed that something on ovirtmgmt bridge forbids to route traffic to another network 5. Internet access "from the box" doesn't work because ovirtmgmt works on VLAN interface, not at physical one itself. 6. In Ovirt's docs I've found the two ways of custom routing. The first one is about external network provider, that unacceptable for me because it doesn't support VLAN tagging (without it node's network can't get access to private cloud network). The second one is custom routing inside a node that doesn't work for me as well by unknown reason What I do wrong? What are the best practices in oVirt network when we talking about internet access from oVirt's VMs? Thx 😉

3 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users March 2021