- Users - oVirt List Archives

Managed Block Storage and more
by Shantur Rathore 22 Jan '21

22 Jan '21

Hi all, I am planning my new oVirt cluster on Apple hosts. These hosts can only have one disk which I plan to partition and use for hyper converged setup. As this is my first oVirt cluster I need help in understanding few bits. 1. Is Hyper converged setup possible with Ceph using cinderlib? 2. Can this hyper converged setup be on oVirt Node Next hosts or only Centos? 3. Can I install cinderlib on oVirt Node Next hosts? 4. Are there any pit falls in such a setup? Thanks for your help Regards, Shantur

8 30

[ANN] oVirt 4.4.4 is now generally available
by Sandro Bonazzola 22 Jan '21

22 Jan '21

oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. 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/NDSVUZSESOXEFJ… ) 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.4 Release? This update is the fourth 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.4: https://www.ovirt.org/release/4.4.4/ - Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html - Advanced Virtualization 8.3 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.4 release highlights: https://www.ovirt.org/release/4.4.4/ - 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.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- 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.*

14 32

[ANN] oVirt 4.4.5 Second Release Candidate is now available for testing
by Sandro Bonazzola 22 Jan '21

22 Jan '21

oVirt 4.4.5 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Second Release Candidate for testing, as of January 21st, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) 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 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://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: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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

Cinderlib died after upgrade Cluster Compatibility version 4.4 ->4.5
by Mike Andreev 21 Jan '21

21 Jan '21

hi all, after upgrade oVirt 4.4.7 Cluster Compatibility version 4.4 ->4.5 cinderlib storage is died: tail -f /var/log/ovirt-engine/cinderlib/cinderlib.log 2021-01-20 12:35:28,781 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': Volume type with name __DEFAULT__ could not be found. [3d4a9aa9-c5f0-498c-b650-bc64d979f194] 2021-01-20 12:43:31,209 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': Volume type with name __DEFAULT__ could not be found. [927a1e82-aa21-4358-b213-120682d85e63] 2021-01-20 13:05:32,833 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [b645c321-5c64-4c54-972a-f81080bb6b0f] 2021-01-20 15:16:45,667 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [19d98e01] 2021-01-20 15:16:48,232 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [2088beea] 2021-01-20 15:16:50,320 - cinderlib-client - ERROR - Failure occurred when trying to run command 'disconnect_volume': Volume type with name __DEFAULT__ could not be found. [793923ab] 2021-01-20 15:37:28,423 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [5c8f0d73] 2021-01-20 15:37:30,707 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [35e96dcd] 2021-01-20 15:55:36,179 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [b5fbb358-36c7-4d3b-9431-16b3a699f300] 2021-01-20 15:57:33,733 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [ae879975-d36a-4b2b-9829-2713266f1c1f] in engine.log: 021-01-20 15:57:31,795+01 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-2) [ae879975-d36a-4b2b-9829-2713266f1c1f] Running command: AddDiskCommand internal: false. Entities affected : ID: 32dd7b42-eeb7-4cf5-9bef-bd8f8dd9608e Type: StorageAction group CREATE_DISK with role type USER 2021-01-20 15:57:32,014+01 INFO [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] (EE-ManagedExecutorService-commandCoordinator-Thread-1) [ae879975-d36a-4b2b-9829-2713266f1c1f] Running command: AddManagedBlockStorageDiskCommand internal: true. 2021-01-20 15:57:33,936+01 ERROR [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] (EE-ManagedExecutorService-commandCoordinator-Thread-1) [ae879975-d36a-4b2b-9829-2713266f1c1f] cinderlib execution failed: 2021-01-20 15:57:34,012+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [] EVENT_ID: USER_ADD_DISK_FINISHED_FAILURE(2,022), Add-Disk operation failed to complete. 2021-01-20 15:57:34,090+01 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [ae879975-d36a-4b2b-9829-2713266f1c1f] Command 'AddDisk' id: 'c7e43317-495e-4b97-96cd-02f02cb20ab2' child commands '[1de7bfa3-09c3-45a5-955a-580236f0296c]' executions were completed, status 'FAILED' 2021-01-20 15:57:35,127+01 ERROR [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [ae879975-d36a-4b2b-9829-2713266f1c1f] Ending command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' with failure. 2021-01-20 15:57:35,135+01 ERROR [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [ae879975-d36a-4b2b-9829-2713266f1c1f] Ending command 'org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand' with failure. I check it on cinderlib 2.0, 2.1, 3.0 installed as from rpm (ussuri) and from pip install - errors the same. on backend we use CEPH 14 rbd pools

2 5

Gluster Hyperconverged fails with single disk partitioned
by Shantur Rathore 21 Jan '21

21 Jan '21

Hi, I am trying to setup a single host Self-Hosted hyperconverged setup with GlusterFS. I have a custom partitioning where I provide 100G for oVirt and its partitions and rest 800G to a physical partition (/dev/sda4). When I try to create gluster deployment with the wizard, it fails TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [ovirt-macpro-16.lab.ced.bskyb.com] (item={'key': 'gluster_vg_sda4', 'value': [{'vgname': 'gluster_vg_sda4', 'pvname': '/dev/sda4'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sda4 excluded by a filter.\n", "item": {"key": "gluster_vg_sda4", "value": [{"pvname": "/dev/sda4", "vgname": "gluster_vg_sda4"}]}, "msg": "Creating physical volume '/dev/sda4' failed", "rc": 5} I checked and /etc/lvm/lvm.conf filter doesn't allow /dev/sda4. It only allows PV for onn VG. Once I manually allow /dev/sda4 to lvm filter, it works fine and gluster deployment completes. Fdisk : # fdisk -l /dev/sda Disk /dev/sda: 931.9 GiB, 1000555581440 bytes, 1954210120 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: FE209000-85B5-489A-8A86-4CF0C91B2E7D Device Start End Sectors Size Type /dev/sda1 2048 1230847 1228800 600M EFI System /dev/sda2 1230848 3327999 2097152 1G Linux filesystem /dev/sda3 3328000 213043199 209715200 100G Linux LVM /dev/sda4 213043200 1954209791 1741166592 830.3G Linux filesystem LVS # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home onn Vwi-aotz-- 10.00g pool0 0.11 ovirt-node-ng-4.4.4-0.20201221.0 onn Vwi---tz-k 10.00g pool0 root ovirt-node-ng-4.4.4-0.20201221.0+1 onn Vwi-aotz-- 10.00g pool0 ovirt-node-ng-4.4.4-0.20201221.0 25.26 pool0 onn twi-aotz-- 95.89g 2.95 14.39 root onn Vri---tz-k 10.00g pool0 swap onn -wi-ao---- 4.00g tmp onn Vwi-aotz-- 10.00g pool0 0.12 var onn Vwi-aotz-- 20.00g pool0 0.92 var_crash onn Vwi-aotz-- 10.00g pool0 0.11 var_log onn Vwi-aotz-- 10.00g pool0 0.13 var_log_audit onn Vwi-aotz-- 4.00g pool0 0.27 # grep filter /etc/lvm/lvm.conf filter = ["a|^/dev/disk/by-id/lvm-pv-uuid-QrvErF-eaS9-PxbI-wCBV-3OxJ-V600-NG7raZ$|", "r|.*|"] Am I doing something which oVirt isn't expecting? Is there anyway to provide tell gluster deployment to add it to lvm config. Thanks, Shantur

2 3

Change of IP's
by Román Larumbe S. 21 Jan '21

21 Jan '21

Hello, I have a Dell VRTX with 2 M640 servers, we installed oVirt version 4.3.10.4-1.el7, we have 1 cluster, 2 hosts and 2 storage domains. I need to change ALL the network environment solution, that is, from IP's 192.168.11.XX to 172.16.10.XX. Can anybody help me? Thank you. Román Larumbe S. Facebook: Serahp LS

2 1

VMware Fence Agent
by Robert Tongue 21 Jan '21

21 Jan '21

Greetings all, I am new to oVirt, and have a proof of concept setup with a 3-node oVirt cluster nested inside of VMware VCenter to learn it, so then I can efficiently migrate that back out to the physical nodes to replace VCenter. I have gotten all the way to a working cluster setup, with the exception of fencing. I used engine-config to pull in the vmware_soap fence agent, and enabled all the options, however there is one small thing I cannot figure out. The connection uses a self-signed certificate on the vcenter side, and I cannot figure out the proper combination of engine-config -s commands to get the script to be called with the "ssl-insecure" option, which does contain a value. It just needs the option passed. Is there anyone out there in the ether that can help me out? I can provide any information you request. Thanks in advance. The fence agent script is called with the following syntax in my tests, and returned the proper status: [root@cluster2-vm ~]# /usr/sbin/fence_vmware_soap -o status -a vcenter.address --username="administrator(a)vsphere.local" --password="0bfusc@t3d" --ssl-insecure -n cluster1-vm Status: ON -phunyguy

1 0

Why cannot create new volume ?
by tommy 21 Jan '21

21 Jan '21

3 7

Mutually exclusive VMs
by Shantur Rathore 21 Jan '21

21 Jan '21

Hi all, I am trying to figure if there is a way to force oVirt to schedule VMs on different hosts. So if I am cloning 6 VMs from a template, I want oVirt to schedule them on all different hosts. No 2 VMs must schedule on the same host. I know that there is pin-to-host functionality but I don't want to manually pin it to hosts. Thanks Shantur

2 1

Unable to edit DNS connfiguration on hosts
by miguel.garcia＠toshibagcs.com 20 Jan '21

20 Jan '21

I had to replace the DNS server in my network so I want to update the DNS address on each host so in oVirt web interface I go to Compute > Host > Hostname > Network Interfaces > Setup Host Networks Right there I click on the edit button of the vlan for networking, check out (host ip address is static), DNS configuration, check DNS configuration, Type DNS ip address and click ok to save change. I got message: Error while executing action HostSetupNetworks: Unexpected Exception. Into engile.log found message "Operation not permitted" related to this action despite that was executed with my user account (wint admin privileges) and same message was returned using admin@internal user. 2021-01-20 11:35:31,579-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] START, HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSw itchType='OVS', managementNetworkChanged='false'}), log id: 23059843 2021-01-20 11:35:31,582-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] FINISH, HostSetupNetworksVDSCommand, return: , log id: 23059843 2021-01-20 11:35:35,665-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}] 2021-01-20 11:35:35,665-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Failed in 'HostSetupNetworksVDS' method 2021-01-20 11:35:35,666-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}] 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hyp10.eboss command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'} 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', cluster SwitchType='OVS', managementNetworkChanged='false'})' execution failed: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 2021-01-20 11:35:35,673-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Host setup networks finished. Lock released. Monitoring can run now for host 'hyp10.eboss' from data-center 'tgcs-gdl-dc1-public' 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 (Failed with error unexpected and code 16) 2021-01-20 11:35:35,677-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK39c05625-7b59-4a38-a5a9-5d556ae1fe18=HOST_NETWORK]', sharedLocks=''}' This error message happens even in master as in nodes hosts. Any idea how can I solve it? Thanks in advance

1 0

About Enroll Certificate
by tommy 20 Jan '21

20 Jan '21

Hi, What function of the Enroll Certificate ??

2 2

Problems Installing host on brand new 4.4 cluster
by David Johnson 20 Jan '21

20 Jan '21

Hi all, I am standing up a brand new cluster on new hardware. The ovirt controller is installed and appears to be running fine. When I attempt to add the new host, I get the flag that says "Non Operational", and the exclamation mark with the message "Host has no default route". I have confirmed that I have bidirectional ssh connections between the controller and the new host. Selinux is disabled. Firewall is disabled. I can get to the host console via the link in the GUI Compute|Hosts page. This looks like a common symptom of a host of problems, but there is nothing to readily indicate what the actual problem is. In the ovirt-engine log, I found this entry: "Host 'ovirt-host-03' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt'" This seems self-explanatory, but I see no way to add the missing network to the host. Thank you in advance for your help Regards, David Johnson * <http://www.linkedin.com/in/pojoguy>*

2 2

Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"
by james.freeman＠a24.io 19 Jan '21

19 Jan '21

Hi all I am in the process of migrating a RHV 4.3 setup to RHV 4.4 and struggling with the setup. I am installing on RHEL 8.3, using settings backed up from the RHV 4.3 install (via 'hosted-engine --deploy --restore-from-file=backup.bck'). The install process always fails at the same point for me at the moment, and I can't figure out how to get past it. As far as install progress goes, the local hosted-engine comes up and runs on the node. I have been able to grep for local_vm_ip in the logs, and can SSH into it with the password I set during the setup phase. However the install playbooks always fail with: 2021-01-18 18:38:00,086-0500 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:167 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Earlier in the logs, I note the following: 2021-01-18 18:34:51,258-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} 2021-01-18 18:37:16,661-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} 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-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 435, in _closeup raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2021-01-18 18:37:18,996-0500 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2021-01-18 18:37:32,421-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host rhvm.example.org port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true} I find the unreachable message a bit odd, as at this stage all that has happened is that the local hosted-engine has been brought up to be configured, and so it is running on virbr0, not on my actual network. As a result, that DNS address will never resolve, and the IP it resolves to won't be up. I gave the installation script permission to modify the local /etc/hosts but this hasn't improved things. I presume I'm missing something in the install process, or earlier on in the logs, but I've been scanning for errors and possible clues to no avail. Any and all help greatly appreciated!

3 5

VM Disks order
by Erez Zarum 19 Jan '21

19 Jan '21

When attaching a disk it is not possible to set the disk order nor modify the order later. Example: A new VM is provisioned with 5 disks, Disk0 is the OS and then later attached disks by order up to Disk4. Removing Disk3 and then later attaching does not promise it will be attached back as Disk3. In most other platforms it is possible to set the order. Am i missing something? if not, is there a plan to add this feature?

2 1

Why the update hung here ?
by tommy 19 Jan '21

19 Jan '21

Hi , I just update the hosts, but why the log print these info many many times for a long while.

2 1

noVNC error.
by tommy 19 Jan '21

19 Jan '21

Hi: I use novnc console can connect to engine vm. But when I using novnc console connect to other vm in other datacenter, failed. The ovirt-websocket-proxy log is: Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]: 192.168.10.104 - - [19/Jan/2021 15:43:32] connecting to: ohost2.tltd.com:5900 (using SSL) Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]: ovirt-websocket-proxy[24096] INFO msg:824 handler exception: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:618) What reason ?

2 1

Guest don't start : Cannot access backing file
by Lionel Caignec 19 Jan '21

19 Jan '21

Hi, i've a big problem, i juste shutdown (power off completely) a guest to make a cold restart. And at startup the guest say : "Cannot access backing file '/rhev/data-center/mnt/blockSD/69348aea-7f55-41be-ae4e-febd86c33855/images/8224b2b0-39ba-44ef-ae41-18fe726f26ca/ca141675-c6f5-4b03-98b0-0312254f91e8'" When i look from shell on Hypervisor the device file is red blinking... Trying to change SPM, look device into all hosts, copy disk etc... no way to get my disk back online. It seems ovirt completely lost (delete?) the block device. There is a way to manually dump (dd) the device in command line in order to import it inside ovirt? My environment Storage : SAN (managed by ovirt) Ovirt-engine 4.4.3.12-1.el8 Host centos 8.2 Vdsm 4.40.26 Thanks for help i'm stuck and it's really urgent -- Lionel Caignec

2 2

oVirt Engine no longer Starting
by penguin pages 18 Jan '21

18 Jan '21

3 node cluster. Gluster for shared storage. CentOS8 Updated to CentOS 8 Streams :P -> https://bugzilla.redhat.com/show_bug.cgi?id=1911910 After several weeks .. I am really in need of direction to get this fixed. I saw several postings about oVirt package issues but not found a fix. [root@thor ~]# dnf update Last metadata expiration check: 2:54:29 ago on Fri 15 Jan 2021 06:49:16 AM EST. Error: Problem 1: package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-bridge-234-1.el8.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package cockpit-bridge-217-1.el8.x86_64 Problem 2: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package cockpit-dashboard-217-1.el8.noarch Problem 3: package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch requires ovirt-host >= 4.4.0, but none of the providers can be installed - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch - cannot install the best update candidate for package cockpit-system-217-1.el8.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@thor ~]# yum install cockpit-dashboard --nobest Last metadata expiration check: 2:54:52 ago on Fri 15 Jan 2021 06:49:16 AM EST. Package cockpit-dashboard-217-1.el8.noarch is already installed. Dependencies resolved. Problem: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best candidate for the job ========================================================================================================================================================================================================================================= Package Architecture Version Repository Size ========================================================================================================================================================================================================================================= Skipping packages with broken dependencies: ovirt-host x86_64 4.4.1-1.el8 ovirt-4.4 13 k ovirt-host x86_64 4.4.1-2.el8 ovirt-4.4 13 k ovirt-host x86_64 4.4.1-3.el8 ovirt-4.4 13 k Transaction Summary ========================================================================================================================================================================================================================================= Skip 3 Packages Nothing to do. Complete! [root@thor ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─WDC_WDS100T2B0B-00YS70_19106A802926 253:3 0 931.5G 0 mpath └─vdo_2926 253:5 0 4T 0 vdo /gluster_bricks/gv0 sdb 8:16 0 931.5G 0 disk └─WDC_WDS100T2B0B-00YS70_192490801828 253:4 0 931.5G 0 mpath sdc 8:32 0 477G 0 disk └─vdo_sdc 253:6 0 2.1T 0 vdo ├─gluster_vg_sdc-gluster_lv_engine 253:7 0 100G 0 lvm /gluster_bricks/engine ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc_tmeta 253:8 0 1G 0 lvm │ └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc-tpool 253:10 0 2T 0 lvm │ ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc 253:11 0 2T 1 lvm │ ├─gluster_vg_sdc-gluster_lv_data 253:12 0 1000G 0 lvm /gluster_bricks/data │ └─gluster_vg_sdc-gluster_lv_vmstore 253:13 0 1000G 0 lvm /gluster_bricks/vmstore └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc_tdata 253:9 0 2T 0 lvm └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc-tpool 253:10 0 2T 0 lvm ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc 253:11 0 2T 1 lvm ├─gluster_vg_sdc-gluster_lv_data 253:12 0 1000G 0 lvm /gluster_bricks/data └─gluster_vg_sdc-gluster_lv_vmstore 253:13 0 1000G 0 lvm /gluster_bricks/vmstore sdd 8:48 1 58.8G 0 disk ├─sdd1 8:49 1 1G 0 part /boot └─sdd2 8:50 1 57.8G 0 part ├─cl-root 253:0 0 36.1G 0 lvm / ├─cl-swap 253:1 0 4G 0 lvm [SWAP] └─cl-home 253:2 0 17.6G 0 lvm /home [root@thor ~]# mount |grep engine /dev/mapper/gluster_vg_sdc-gluster_lv_engine on /gluster_bricks/engine type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota,_netdev,x-systemd.requires=vdo.service) thorst.penguinpages.local:/engine on /media/engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072,_netdev) thorst.penguinpages.local:/engine on /rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072,_netdev,x-systemd.device-timeout=0) [root@thor ~]# [root@thor ~]# tail -50 /var/log/messages Jan 15 09:46:43 thor platform-python[28088]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:43 thor abrt-server[28116]: Not saving repeating crash in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 241. Jan 15 09:46:43 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:43 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:45 thor systemd[1]: Started Session c448 of user root. Jan 15 09:46:45 thor systemd[1]: session-c448.scope: Succeeded. Jan 15 09:46:45 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Service RestartSec=10s expired, scheduling restart. Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Scheduled restart job, restart counter is at 211. Jan 15 09:46:48 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Monitoring Agent. Jan 15 09:46:48 thor systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Failed initializing the broker: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run#012 self._storage_broker_instance = self._get_storage_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker#012 return storage_broker.StorageBroker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__#012 self._backend.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 408, in connect#012 self._check_symlinks(self._storage_path, volume.path, service_link)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 105, in _check_symlinks#012 os.unlink(service_link)#012OSError: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Trying to restart the broker Jan 15 09:46:48 thor platform-python[28118]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:48 thor abrt-server[28144]: Deleting problem directory Python3-2021-01-15-09:46:48-28118 (dup of Python3-2020-09-18-14:25:13-1363) Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 242. Jan 15 09:46:48 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:48 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary monitors Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor#012 response = self._proxy.start_monitor(type, options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__#012 return self.__send(self.__name, args)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012 verbose=self.__verbose#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request#012 return self.single_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request#012 http_conn = self.send_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request#012 self.send_content(connection, request_body)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content#012 connection.endheaders(request_body)#012 File "/usr/lib64/python3.6/http/client.py", line 1264, in endheaders#012 self._send_output(message_body, encode_chunked=encode_chunked)#012 File "/usr/lib64/python3.6/http/client.py", line 1040, in _send_output#012 self.send(msg)#012 File "/usr/lib64/python3.6/http/client.py", line 978, in send#012 self.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect#012 self.sock.connect(base64.b16decode(self.host))#012FileNotFoundError: [Errno 2] No such file or directory#012#012During handling of the above exception, another exception occurred:#012#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor#012 ).format(t=type, o=options, e=e)#012ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '172.16.100.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent Jan 15 09:46:48 thor abrt-server[28144]: /bin/sh: reporter-systemd-journal: command not found Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Main process exited, code=exited, status=157/n/a Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Failed with result 'exit-code'. Jan 15 09:46:49 thor vdsm[8421]: WARN Failed to retrieve Hosted Engine HA info, is Hosted Engine setup finished? Jan 15 09:46:50 thor systemd[1]: Started Session c449 of user root. Jan 15 09:46:50 thor systemd[1]: session-c449.scope: Succeeded. Jan 15 09:46:50 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Failed initializing the broker: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run#012 self._storage_broker_instance = self._get_storage_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker#012 return storage_broker.StorageBroker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__#012 self._backend.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 408, in connect#012 self._check_symlinks(self._storage_path, volume.path, service_link)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 105, in _check_symlinks#012 os.unlink(service_link)#012OSError: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Trying to restart the broker Jan 15 09:46:53 thor platform-python[28165]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:53 thor abrt-server[28199]: Not saving repeating crash in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 243. Jan 15 09:46:53 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:53 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:55 thor systemd[1]: Started Session c450 of user root. Jan 15 09:46:55 thor systemd[1]: session-c450.scope: Succeeded. Jan 15 09:46:55 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Questions: 1) I have two important VMs that have snapshots that I need to boot up. Is their a means with an HCI configuration to manually start the VMs without oVirt engine being up? 2) Is their a means to debug what is going on with the engine failing to start to repair (I hate reloading as the only fix for systems) 3) Is their a means to re-deploy HCI setup wizard, but use the "engine" volume and so retain the VMs and templates?

4 19

VG issue / Non Operational
by Christian Reiss 18 Jan '21

18 Jan '21

Hey folks, quick (I hope) question: On my 3-node cluster I am swapping out all the SSDs with fewer but higher capacity ones. So I took one node down (maintenance, stop), then removed all SSDs, set up a new RAID, set up lvm and gluster, let it resync. Gluster health status shows no unsynced entries. Uppon going from maintenance to online from ovirt management It goes into non-operational status, vdsm log on the node shows: 2021-01-17 11:13:29,051+0100 INFO (jsonrpc/6) [api.host] START getAllVmStats() from=::1,48580 (api:48) 2021-01-17 11:13:29,051+0100 INFO (jsonrpc/6) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48580 (api:54) 2021-01-17 11:13:29,052+0100 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2021-01-17 11:13:30,420+0100 WARN (monitor/4a62cdb) [storage.LVM] Reloading VGs failed (vgs=[u'4a62cdb4-b314-4c7f-804e-8e7275518a7f'] rc=5 out=[] err=[' Volume group "4a62cdb4-b314-4c7f-804e-8e7275518a7f" not found', ' Cannot process volume group 4a62cdb4-b314-4c7f-804e-8e7275518a7f']) (lvm:470) 2021-01-17 11:13:30,424+0100 ERROR (monitor/4a62cdb) [storage.Monitor] Setting up monitor for 4a62cdb4-b314-4c7f-804e-8e7275518a7f failed (monitor:330) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 327, in _setupLoop self._setupMonitor() File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 349, in _setupMonitor self._produceDomain() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 159, in wrapper value = meth(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 367, in _produceDomain self.domain = sdCache.produce(self.sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) I assume due to the changed LVM UUID it fails, right? Can I someone fix/change the UUID and get the node back up again? It does not seem to be a major issue, to be honest. I can see the gluster mount (what ovirt mounts when it onlines a node) already, and gluster is happy too. Any help is appreciated! -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 4

encrypted GENEVE traffic
by Pavel Nakonechnyi 18 Jan '21

18 Jan '21

Dear oVirt Community, From my understanding oVirt does not support Open vSwitch IPSEC tunneling for GENEVE traffic (which is described on pages http://docs.openvswitch.org/en/latest/howto/ipsec/ and http://docs.openvswitch.org/en/latest/tutorials/ipsec/) Are there plans to introduce such support? (or explicitly not to..) Is it possible to somehow manually configure such tunneling for existing virtual networks? (even in a limited way) Alternatively, is it possible to deploy oVirt on top of the tunneled (i.e. via VXLAN, IPSec) interfaces? This will allow to encrypt all management traffic. Such requirement arises when using oVirt deployment on third-party premises with untrusted network. Thank in advance for any clarifications. :) -- WBR, Pavel +32478910884

2 7

Q: Node SW Install from oVirt Engine UI Failed
by Andrei Verovski 18 Jan '21

18 Jan '21

Hi, I installed fresh CentOS Stream on HP ProLiant and now trying to install Node SW from oVirt Engine WEB UI. Software installation failed but no comprehensive description displayed in WEB UI. Where I can find detailed logs what’s going wrong? On node "sudo dnf repolist —all” lists required repos, with unnecessary disabled. Thanks in advance. Andrei. repo id repo name status appstream CentOS Stream 8 - AppStream enabled baseos CentOS Stream 8 - BaseOS enabled debuginfo CentOS Stream 8 - Debuginfo disabled extras CentOS Stream 8 - Extras enabled ha CentOS Stream 8 - HighAvailability disabled media-appstream CentOS Stream 8 - Media - AppStream disabled media-baseos CentOS Stream 8 - Media - BaseOS disabled ovirt-4.4 Latest oVirt 4.4 Release enabled ovirt-4.4-advanced-virtualization-testing Advanced Virtualization testing pack enabled ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch enabled ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd enabled ovirt-4.4-centos-ovirt44-testing CentOS-8 - oVirt 4.4 - testing enabled ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdba enabled ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned enabled ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned b enabled ovirt-4.4-epel Extra Packages for Enterprise Linux enabled ovirt-4.4-glusterfs-7-testing GlusterFS 7 testing packages for x86 enabled ovirt-4.4-ioprocess-preview Copr repo for iprocess-preview owned enabled ovirt-4.4-ovirt-imageio-preview Copr repo for ovirt-imageio-preview enabled ovirt-4.4-virtio-win-latest virtio-win builds roughly matching w enabled powertools CentOS Stream 8 - PowerTools enabled rt CentOS Stream 8 - RealTime disabled spp Service Pack for ProLiant enabled

2 3

About Translation
by Reyhan Gülçetin 18 Jan '21

18 Jan '21

Hello, I'm Reyhan! I am a third-grade physics engineering student in Turkey, I also worked as a part-time system administration in the university's IT Head Office until last month. (Now I'm more into DevOps). Back in there, I was responsible for understanding how we can apply oVirt to our IT Office, so I was scrolling through the documentations. I've decided to contribute, oVirt could be the project I used the most, since I'm not a bug-fixer, at least I can help with the translation. I'm a native Turkish speaker, so I thought it would go well. I wish you the best, Best regards. Reyhan Gülçetin.

2 1

how to install hosted-engine without internet connection ?
by tommy 18 Jan '21

18 Jan '21

Hi,every one! My env cannot access internet, but during the hosted-engine installation, It needs to run yum install to update system. I have made a yum source mirror local, but there is a step ( after create engine vm, the vm runs yum update using default repo configure ) it failed to connect yum source. How can I configure yum source to local yum server before the vm run update ? Thanks.

2 2

Re: Networking question on setting up self-hosting engine
by Yedidyah Bar David 17 Jan '21

17 Jan '21

Hi, On Fri, Jan 15, 2021 at 7:10 AM Kim Yuan Lee <netgoogling(a)gmail.com> wrote: > > Hi Didi, > > I sent this to the list, but I cc you here as I think I didn't format the email correctly using the web interface :) I didn't see your message to the list. Now adding the list back. > > Dear Ovirt list, > > I saw some failures in /var/log/ovirt-hosted-engine-setup such as: > 1) Install oVirt Engine packages for restoring backup > 2) Copy engine logs etc > > But I'm not sure what is the root cause for the setup to fail? > > Attached is the log file for your reference. Could you please advise? Thanks. It seems to have failed in: 2021-01-14 19:30:59,509+0800 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Install Oracle oVirt repo kwargs is_conditional:False 2021-01-14 19:30:59,509+0800 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Install Oracle oVirt repo kwargs 2021-01-14 19:31:01,189+0800 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_task': u'Install Oracle oVirt repo', 'task_duration': 1, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} 2021-01-14 19:31:01,189+0800 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7faffb39f590> kwargs 2021-01-14 19:31:01,443+0800 INFO ansible task start {'status': 'OK', 'ansible_task': u'ovirt.hosted_engine_setup : Install oVirt Engine packages for restoring backup', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2021-01-14 19:31:01,443+0800 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Install oVirt Engine packages for restoring backup kwargs is_conditional:False 2021-01-14 19:31:01,444+0800 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Install oVirt Engine packages for restoring backup kwargs 2021-01-14 19:31:18,336+0800 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Install oVirt Engine packages for restoring backup', 'ansible_result': u"type: <type 'dict'>\nstr: {'_ansible_no_log': False, '_ansible_delegated_vars': {'ansible_host': u'engine.orakvm2.local'}, u'changed': False, u'results': [u'Loaded plugins: ulninfo\\nResolving Dependencies\\n--> Running transaction check\\n---> Package ovirt-engine.noarch 0:4.3.6.6-1.0.8.el7 will be installed\\n--> Processing De", 'task_duration': 17, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} This is Oracle-specific code, not part of oVirt. I suggest that you contact Oracle. Good luck and best regards, > > > Sincerely, Lee. > > > On Thu, Jan 14, 2021 at 2:46 PM Yedidyah Bar David <didi(a)redhat.com> wrote: >> >> Hi, >> >> On Wed, Jan 13, 2021 at 7:16 PM <netgoogling(a)gmail.com> wrote: >> > >> > Dear list, >> > >> > I have tried setting up self-hosting engine on a host with ONE Nic (Ovirt 4.4 CentOS 8 Stream). I followed the Quick Start Guide, and tried the command line self-host setup, but ended up with the following error: >> > >> > {u'msg': u'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results.... >> > >> > I tried on another host with TWO NICs (Ovirt 4.3 Oracle Linux 7 Update 9). This time I setup a bridge BR0 and disable EM1 (the first Ethernet interface on the host), and then created Bond0 on-top of BR0. Both Bond0 and EM2 (the second Ethernet interface on the host) were up. And then I tried again using Ovirt-Cockpit wizard, with the Engine VM set on BR0, and the deployment of Engine VM simply failed. The Engine and Host are using the same network numbers (192.168.2.0/24) and they resolved correctly. I read the logs in var/log/ovirt-engine/engine.log but there wasn't any error reported. >> > >> > I have already tried many times for the past few days and I'm at my wits-end. May I know: >> > 1) Is it possible to install Self-hosted engine with just ONE NIC? >> >> Generally speaking, yes. >> >> > 2) Any suggestion how to troubleshoot these problems? And tested network configurations? >> >> Please check/share all relevant logs. If unsure, all of /var/log. >> Specifically, /var/log/ovirt-hosted-engine-setup/* (also engine-logs >> subdirs, if relevant) and /var/log/vdsm/* on the hosts. >> >> Good luck and best regards, >> -- >> Didi >> -- Didi

2 1

Disaster Recovery using Ansible roles
by Henry lol 17 Jan '21

17 Jan '21

Hi, I have 2 questions about Disaster Recovery with Ansible. 1) regarding Ansible failover, AFAIK, a mapping file must be generated before running failover. then, should I periodically generate a new mapping file to reflect the latest structure of the environment? 2) I guess Ansible failover uses OVF_STOREs to restore the environment and OVF_STOREs in storage domains are updated every 1 min as default. then, how to recover the changes made in the meantime?

2 3

Problem with Ovirt
by Keith Forman 17 Jan '21

17 Jan '21

HiNeed help with setting up Ovirt.engine-setup run successfully on CentOS 7, with PostgreSQL 12.Now when running systemctl start ovirt-engine , it starts successfully, but in the frontend, it says 404 Not Found. In engine.log, I see the following 2 errors:Error initializing: Unable to determine the correct call signature - no procedure/function/signature for 'getallfrommacpools'andError in getting DB connection, database is inaccessible: Unable to determine the correct call signature - no procedure/function/signature for 'checkdbconnection'Any tips as to the way forward would be much appreciated

3 2

Hyperconverged Ceph + Managed Block Storage
by Shantur Rathore 16 Jan '21

16 Jan '21

Hi all, I am planning my new oVirt cluster on Apple hosts. These hosts can only have one disk which I plan to partition and use for hyper converged setup. As this is my first oVirt cluster I need help in understanding a few bits. 1. Is Hyper converged setup possible with Ceph using cinderlib? 2. Can this hyper converged setup be on oVirt Node Next hosts or only Centos? 3. Can I install cinderlib on oVirt Node Next hosts? 4. Are there any pitfalls in such a setup? Thanks for your help Regards, Shantur

1 0

Create new user, but why cannot login ?
by tommy 15 Jan '21

15 Jan '21

I just create a new user: [root@oeng ~]# ovirt-aaa-jdbc-tool user add cuitao adding user cuitao... user added successfully [root@oeng ~]# ovirt-aaa-jdbc-tool user password-reset cuitao Password: Reenter password: updating user cuitao... user updated successfully [root@oeng ~]# ovirt-aaa-jdbc-tool user edit cuitao --password-valid-to="2221-01-15 05:23:41Z" updating user cuitao... user updated successfully [root@oeng ~]# ovirt-aaa-jdbc-tool user show cuitao -- User cuitao(300163db-8352-4fbd-86ac-d25014364f08) -- Namespace: * Name: cuitao ID: 300163db-8352-4fbd-86ac-d25014364f08 Display Name: Email: sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> First Name: tommy Last Name: cui Department: Title: Description: Account Disabled: false Account Locked: false Account Unlocked At: 1970-01-01 00:00:00Z Account Valid From: 2021-01-15 05:23:41Z Account Valid To: 2221-01-15 05:23:41Z Account Without Password: false Last successful Login At: 2021-01-15 05:54:49Z Last unsuccessful Login At: 2021-01-15 05:32:12Z Password Valid To: 2221-01-15 05:23:41Z And I give VmCreator Role to the new account. But why cannot login ?

2 2

New oVirt Cluster and Managed block storage
by Shantur Rathore 15 Jan '21

15 Jan '21

Hi all, I am planning my new oVirt cluster on Apple hosts. These hosts can only have one disk which I plan to partition and use for hyper converged setup. As this is my first oVirt cluster I need help in understanding a few bits. 1. Is Hyper converged setup possible with Ceph using cinderlib? 2. Can this hyper converged setup be on oVirt Node Next hosts or only Centos? 3. Can I install cinderlib on oVirt Node Next hosts? 4. Are there any pitfalls in such a setup? Thanks for your help Regards, Shantur

1 0

potential split-brain after upgrading Gluster version and rebooting one of three storage nodes
by user-5138＠yandex.com 15 Jan '21

15 Jan '21

Hello everyone, I'm running an oVirt cluster (4.3.10.4-1.el7) on a bunch of physical nodes with Centos 7.9.2009 and the Hosted Engine is running as a virtual machine on one of these nodes. As for the storage, I'm running GlusterFS 6.7 on three separate physical storage nodes (also Centos 7). Gluster itself has three different volumes of the type "Replicate" or "Distributed-Replicate". I recently updated both the system packages and the GlusterFS version to 6.10 on the first storage node (storage1) and now I'm seeing a potential split-brain situation for one of the three volumes when running "gluster volume heal info": Brick storage1:/data/glusterfs/nvme/brick1/brick Status: Connected Number of entries: 0 Brick storage2:/data/glusterfs/nvme/brick1/brick /c32d664d-69ba-4c3f-8ea1-240133963815/dom_md/ids / /.shard/.remove_me Status: Connected Number of entries: 3 Brick storage3:/data/glusterfs/nvme/brick1/brick /c32d664d-69ba-4c3f-8ea1-240133963815/dom_md/ids / /.shard/.remove_me Status: Connected Number of entries: 3 I checked the hashes and the "dom_md/ids" file has a different md5 on every node. Using the heal on the volume command doesn't do anything and the entries remain. The heal info for the other two volumes shows no entries. The affected gluster volume (type: replicate) is mounted as a Storage Domain using the path "storage1:/nvme" inside of oVirt and is used to store the root partitions of all virtual machines, which were running at the time of the upgrade and reboot of storage1. The volume has three bricks, with one brick being stored on each storage node. For the upgrade process I followed the steps shown at https://docs.gluster.org/en/latest/Upgrade-Guide/generic-upgrade-procedure/. I stopped and killed all gluster related services, upgraded both system and gluster packages and rebooted storage1. Is this a split brain situation and how can I solve this? I would be very grateful for any help. Please let me know if you require any additional information. Best regards

4 7

cockpit-ovirt-dashboard
by Gary Pedretty 15 Jan '21

15 Jan '21

So with the latest updates to Ovirt and CentOS 8 Stream it seems that you either can not install cockpit-ovirt-dashboard, or if you do, it downgrades cockpit-bridge and cockpit-system. You then end up not showing up to date on these hosts on Open Virtualization Manager and can only get back to a fully updated datacenter by doing a yum update --allowerasing which then removes cockpit-ovirt-dashboard. My main concern is now that the command line hosted-engine commands have been removed, if the hosted engine is not running for some reason you have no visibility into what is going on since the regular cockpit host interface will not show the virtualization features. You can't put a host in maintenance or start the engine manually. example.... [root@ravn-kvm-1 admin]# yum install cockpit-ovirt-dashboard //////snip/////// Installed products updated. Downgraded: cockpit-bridge-217-1.el8.x86_64 cockpit-system-217-1.el8.noarch Installed: cockpit-dashboard-217-1.el8.noarch cockpit-ovirt-dashboard-0.14.17-1.el8.noarch ovirt-host-4.4.1-4.el8.x86_64 ovirt-hosted-engine-setup-2.4.9-1.el8.noarch Complete! [root@ravn-kvm-1 admin]# yum update Last metadata expiration check: 3:08:22 ago on Tue 12 Jan 2021 01:00:15 PM AKST. Error: Problem 1: package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-bridge-234-1.el8.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package cockpit-bridge-217-1.el8.x86_64 Problem 2: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package cockpit-dashboard-217-1.el8.noarch Problem 3: package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch requires ovirt-host >= 4.4.0, but none of the providers can be installed - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch - cannot install the best update candidate for package cockpit-system-217-1.el8.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) _______________________________ Gary Pedretty IT Manager Ravn Alaska Office: 907-266-8451 Mobile: 907-388-2247 Email: gary.pedretty(a)ravnalaska.com "We call Alaska......Home!" Ravn Alaska CONFIDENTIALITY NOTICE: The information in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination, forwarding or copying of the email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you.

2 1

how does host's status changes ? Especially Unassigned or NonOperational or NonResponsible
by lifuqiong＠sunyainfo.com 15 Jan '21

15 Jan '21

Hi all, I'm confusing in Host's status in Ovirt Eninge. When will the host's status become Unassigned or NonOperational or NonResponsible? and If the host's status change to these statuses, What will ovirt response to it? After reading Ovirt Engine's source code, I find Only HostMonitoring.java and AutoRecoveryManager.java will change the status of Host. for example, If the host's status is changed to NonOperational, The AutoRecoveryManager will traverse the NonOperational hosts and calling ActivateVdsCommand.java, which will only set the Host's status to Unassigned ? But I don't know What's the next step? So where I can find the article or manual or other helpful information about this question? Thank you . Your sincerely Mark

1 0

How to limit one user to use given cluster and storage domain ?
by tommy 15 Jan '21

15 Jan '21

Any way to limit different user to use different cluster and storage domain ?

1 0

Re: Constantly XFS in memory corruption inside VMs
by Strahil Nikolov 15 Jan '21

15 Jan '21

Damn... You are using EFI boot. Does this happen only to EFI machines ? Did you notice if only EL 8 is affected ? Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:36:09 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: Yes! I have a live VM right now that will de dead on a reboot: [root@kontainerscomk ~]# cat /etc/*release NAME="Red Hat Enterprise Linux" VERSION="8.3 (Ootpa)" ID="rhel" ID_LIKE="fedora" VERSION_ID="8.3" PLATFORM_ID="platform:el8" PRETTY_NAME="Red Hat Enterprise Linux 8.3 (Ootpa)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8.3:GA" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_BUGZILLA_PRODUCT_VERSION=8.3 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.3" Red Hat Enterprise Linux release 8.3 (Ootpa) Red Hat Enterprise Linux release 8.3 (Ootpa) [root@kontainerscomk ~]# sysctl -a | grep dirty vm.dirty_background_bytes = 0 vm.dirty_background_ratio = 10 vm.dirty_bytes = 0 vm.dirty_expire_centisecs = 3000 vm.dirty_ratio = 30 vm.dirty_writeback_centisecs = 500 vm.dirtytime_expire_seconds = 43200 [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) Use -F to force a read attempt. [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 -F xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) xfs_db: size check failed xfs_db: V1 inodes unsupported. Please try an older xfsprogs. [root@kontainerscomk ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Nov 19 22:40:39 2020 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # /dev/mapper/rhel-root / xfs defaults 0 0 UUID=ad84d1ea-c9cc-4b22-8338-d1a6b2c7d27e /boot xfs defaults 0 0 UUID=4642-2FF6 /boot/efi vfat umask=0077,shortname=winnt 0 2 /dev/mapper/rhel-swap none swap defaults 0 0 Thanks, -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, November 29, 2020 2:33 PM To: Vinícius Ferrão <ferrao(a)versatushpc.com.br> Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Constantly XFS in memory corruption inside VMs Can you check the output on the VM that was affected: # cat /etc/*release # sysctl -a | grep dirty Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:07:48 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hi Strahil. I’m not using barrier options on mount. It’s the default settings from CentOS install. I have some additional findings, there’s a big number of discarded packages on the switch on the hypervisor interfaces. Discards are OK as far as I know, I hope TCP handles this and do the proper retransmissions, but I ask if this may be related or not. Our storage is over NFS. My general expertise is with iSCSI and I’ve never seen this kind of issue with iSCSI, not that I’m aware of. In other clusters, I’ve seen a high number of discards with iSCSI on XenServer 7.2 but there’s no corruption on the VMs there... Thanks, Sent from my iPhone > On 29 Nov 2020, at 04:00, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > Are you using "nobarrier" mount options in the VM ? > > If yes, can you try to remove the "nobarrrier" option. > > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 19:25:48 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: > > > > > > Hi Strahil, > > I moved a running VM to other host, rebooted and no corruption was found. If there's any corruption it may be silent corruption... I've cases where the VM was new, just installed, run dnf -y update to get the updated packages, rebooted, and boom XFS corruption. So perhaps the motion process isn't the one to blame. > > But, in fact, I remember when moving a VM that it went down during the process and when I rebooted it was corrupted. But this may not seems related. It perhaps was already in a inconsistent state. > > Anyway, here's the mount options: > > Host1: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > Host2: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > The options are the default ones. I haven't changed anything when configuring this cluster. > > Thanks. > > > > -----Original Message----- > From: Strahil Nikolov <hunter86_bg(a)yahoo.com> > Sent: Saturday, November 28, 2020 1:54 PM > To: users <users(a)ovirt.org>; Vinícius Ferrão > <ferrao(a)versatushpc.com.br> > Subject: Re: [ovirt-users] Constantly XFS in memory corruption inside > VMs > > Can you try with a test vm, if this happens after a Virtual Machine migration ? > > What are your mount options for the storage domain ? > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: > > > > > > > > > Hello, > > > > I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. > > > > For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. > > > > This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. > > > > Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. > > > > Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. > > > > So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. > > > > Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. > > > > Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. > > > > Thanks all. > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HC > FNWTWFZZTL2EJHV36OENHUGB/ _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CZ5E55LJMA7Y5…

3 8

Using Ansible ovirt_vm
by Matthew.Stier＠fujitsu.com 15 Jan '21

15 Jan '21

Over this weekend, I need to shutdown and restart 1500 VMs while I do work. Modifying an Ansible playbook I have, to accomplish that, seems easy enough. Last weekend I used the web gui and edited each Virtual Machine and changed the 'cluster' to the one I wanted to assign it too. Now I would like to automate this with Ansible. In between shutting them down and starting them up, I need to change the cluster registration of quite a few of the hosts, and I have concerns on how to do that. The Ansible ovirt_vm documentation on this is a bit fuzzy. I'm assuming it for assigning the cluster, but in some examples it appears to be used as a filter. Which changes the meaning. Is it "start the VM in this cluster" or "start this VM if it is in this cluster". The playbook I'm working from is straight forward and has three tasks. First, an ovirt_auth task to log into the SHE. Second, an ovirt_vm task which loops though the group of virtualmachines, defined in an 'ini' file. Third, an ovirt_auth task to logout from the SHE. For stopping, I assume I specify a name, and state to 'stopped' and that should initiate the shutdown. For starting, I assume I should set the state to 'running'. For changing the cluster a vm is assigned to, do I simply need to use the 'cluster' parameter with a value of new cluster? Are there other actions that need to be taken? The VM need to be un and re-registered for the change to take effect? I'd like to make the cluster change individual playbook, but could it be added to the start or stop playbook. (ie: stop and change cluster, start on new cluster) Waiting for the wisdom of the community.

1 0

Re: VM console does not work with new cluster.
by tommy 15 Jan '21

15 Jan '21

Cannot connect even closed firewalld service on hosts. -----Original Message----- From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Matthew.Stier(a)fujitsu.com Sent: Thursday, January 14, 2021 11:20 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; tommy <sz_cuitao(a)163.com>; eevans(a)digitaldatatechs.com Cc: users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Listed in firewalld service 'vdsm' -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Wednesday, January 13, 2021 10:52 PM To: tommy <sz_cuitao(a)163.com>; Stier, Matthew <Matthew.Stier(a)fujitsu.com>; eevans(a)digitaldatatechs.com Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Re: VM console does not work with new cluster. I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > > the firewall list of the host ohost1.tltd.com(192.168.10.160) is: > > [root@ohost1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > Please give me some advice,thanks. > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Strahil Nikolov via Users > Sent: Wednesday, January 13, 2021 3:15 AM > To: Matthew.Stier(a)fujitsu.com; eevans(a)digitaldatatechs.com; > users(a)ovirt.org > Subject: [ovirt-users] Re: VM console does not work with new cluster. > > > > It’s just that once the VM has been moved to the new cluster, > > selecting console results in the same behavior, but that virt- > > viewer starts and stops within a second. > > In order to debug, you will need to compare the files provided when > you press the "console" button from both clusters and identify the > problem. > > Have you compared the firewalld ports on 2 nodes (old and new > cluster) ? > > Best Regards, > Strahil Nikolov > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELT > USPKT6KZ7UZWWFCDRNCF5YLN/ > > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N7JRNNAJDZHA4…

1 0

Networking question on setting up self-hosting engine
by Kim Yuan Lee 14 Jan '21

14 Jan '21

Dear Ovirt list, I saw some failures in /var/log/ovirt-hosted-engine-setup such as: 1) Install oVirt Engine packages for restoring backup 2) Copy engine logs etc But I'm not sure what is the root cause for the setup to fail? Attached is the log file for your reference. Could you please advise? Thanks. > On Thursday, 14 January 1:45 a.m., <Yedidyah Bar David> wrote: >> Hi, >> >> On Wed, Jan 13, 2021 at 7:16 PM <netgoogling(a)gmail.com> wrote: ... <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/X5WRCCSULCNW4B…> Dear list, I have tried setting up self-hosting engine on a host with ONE Nic (Ovirt 4.4 CentOS 8 Stream). I followed the Quick Start Guide, and tried the command line self-host setup, but ended up with the following error: {u'msg': u'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results.... I tried on another host with TWO NICs (Ovirt 4.3 Oracle Linux 7 Update 9). This time I setup a bridge BR0 and disable EM1 (the first Ethernet interface on the host), and then created Bond0 on-top of BR0. Both Bond0 and EM2 (the second Ethernet interface on the host) were up. And then I tried again using Ovirt-Cockpit wizard, with the Engine VM set on BR0, and the deployment of Engine VM simply failed. The Engine and Host are using the same network numbers (192.168.2.0/24) and they resolved correctly. I read the logs in var/log/ovirt-engine/engine.log but there wasn't any error reported. I have already tried many times for the past few days and I'm at my wits-end. May I know: 1) Is it possible to install Self-hosted engine with just ONE NIC? >> Generally speaking, yes. ... <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/X5WRCCSULCNW4B…> 2) Any suggestion how to troubleshoot these problems? And tested network configurations? >> >> Please check/share all relevant logs. If unsure, all of /var/log. >> Specifically, /var/log/ovirt-hosted-engine-setup/* (also engine-logs >> subdirs, if relevant) and /var/log/vdsm/* on the hosts. >> >> Good luck and best regards, Regards, Lee.

1 0

[ANN] oVirt 4.4.5 First Release Candidate is now available for testing
by Lev Veyde 14 Jan '21

14 Jan '21

oVirt 4.4.5 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 First Release Candidate for testing, as of January 14th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) 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: http://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: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/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>

1 0

Re: VM console does not work with new cluster.
by Strahil Nikolov 14 Jan '21

14 Jan '21

I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > > the firewall list of the host ohost1.tltd.com(192.168.10.160) is: > > [root@ohost1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > Please give me some advice,thanks. > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Strahil Nikolov via Users > Sent: Wednesday, January 13, 2021 3:15 AM > To: Matthew.Stier(a)fujitsu.com; eevans(a)digitaldatatechs.com; > users(a)ovirt.org > Subject: [ovirt-users] Re: VM console does not work with new cluster. > > > > It’s just that once the VM has been moved to the new cluster, > > selecting console results in the same behavior, but that virt- > > viewer > > starts and stops within a second. > > In order to debug, you will need to compare the files provided when > you press the "console" button from both clusters and identify the > problem. > > Have you compared the firewalld ports on 2 nodes (old and new > cluster) ? > > Best Regards, > Strahil Nikolov > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELTUSPKT… > >

3 2

Q: oVirt 4.4.4.7 Node settings on CentOS Stream
by Andrei Verovski 14 Jan '21

14 Jan '21

Hi ! I’m installing new oVirt 4.4.4 node on CentOS Stream and its seems there are some changes since older node on CentOS 7.x. 1) NFS shares for storage domain. In 7.x I used chown -Rv nfsnobody:nfsnobody /vmraid/nfs; chmod -Rv 755 /vmraid/nfs In Stream nfsnobody don’t exists, should I use: chown -Rv nobody:nobody /vmraid/nfs; chmod -Rv 777 /vmraid/nfs Is that correct settings? 2) SELinux seems to be more permissive now, looks like I don’t have to tweak it to have my custom cron and SNMP scripts running. Yes, SELinux is running, getenforce -> yields “Enforcing”. Will oVirt sw node installation change this behaviour? Thanks in advance Andrei

1 0

Networking question on setting up self-hosting engine
by netgoogling＠gmail.com 14 Jan '21

14 Jan '21

Dear list, I have tried setting up self-hosting engine on a host with ONE Nic (Ovirt 4.4 CentOS 8 Stream). I followed the Quick Start Guide, and tried the command line self-host setup, but ended up with the following error: {u'msg': u'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results.... I tried on another host with TWO NICs (Ovirt 4.3 Oracle Linux 7 Update 9). This time I setup a bridge BR0 and disable EM1 (the first Ethernet interface on the host), and then created Bond0 on-top of BR0. Both Bond0 and EM2 (the second Ethernet interface on the host) were up. And then I tried again using Ovirt-Cockpit wizard, with the Engine VM set on BR0, and the deployment of Engine VM simply failed. The Engine and Host are using the same network numbers (192.168.2.0/24) and they resolved correctly. I read the logs in var/log/ovirt-engine/engine.log but there wasn't any error reported. I have already tried many times for the past few days and I'm at my wits-end. May I know: 1) Is it possible to install Self-hosted engine with just ONE NIC? 2) Any suggestion how to troubleshoot these problems? And tested network configurations? Hope to hear from you. Thanks.

2 1

Q: New oVirt Node - CentOS 8 or Stream ?
by Andrei Verovski 14 Jan '21

14 Jan '21

Hi, I’m currently adding new oVirt node to existing 4.4 setup. Which underlying OS version would you recommend for long-term deployment - CentOS 8 or Stream ? I don’t use pre-built node ISO since I have a number of custom scripts running on node host OS. Thanks in advance. Andrei

3 2

image upload on Managed Block Storage
by Henry lol 13 Jan '21

13 Jan '21

Hello, I've just checked I can't upload an image into the MBS block through either UI or restAPI. So, is there any method to do that?

2 4

2021 first ovirt network question
by ozmen62＠hotmail.com 13 Jan '21

13 Jan '21

Hi, We're using oVirt as VDI solution for awhile. Infrastacture is 2 HPE Gen10 server with 80x2 Core cpu, 2TB RAM, 16GBX2 HBA For getting performance i've splited the networks on physical layer 2X10GB LACP for VM network 2X10GB LACP for Display(Spice) network 1GB for management + Default Route After 40 VMs spice connections start to be laggy. We've found our SAN storage I/O is bad and we'll change it SSD But, on the other hand, RDP connections is flawless. Now, we have 70 VMs and i need to solve this problem. Do you thing this is a network problem? We've also checked dropping packages on the switches, but found nothing.

4 11

My web console also can not connect to other cluster's vm.
by tommy 13 Jan '21

13 Jan '21

I encountered the question too. The follow file is the connect file for vm that can connect using remote viewer: [virt-viewer] type=vnc host=192.168.10.41 port=5900 password=rdXQA4zr/UAY # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=HostedEngine:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 secure-attention=ctrl+alt+end versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6 :99.0-1 newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/consol e-client-resources [ovirt] host=ooeng.tltd.com:443 vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esct m3Im4tz80mE1DjrNT3XQ admin=1 ca=-----BEGIN CERTIFICATE-----\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBh MCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAe Fw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDVQQKDA h0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0GCSqGSIb3DQEB AQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/JmKeJAUVZqNKRg1q80Ip WyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSk idHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLI ffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLM wohz7wgtgsDA36277mujNyMjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAA Gjga0wgaowHQYDVR0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOM qN8+QhCP7DAkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHT AbBgNVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1Ud DwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmjrLZGyh 5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjdrHvhfbZFnZsGe 2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4pHS04c2+4JMhpe+hxgsO 2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVWw+QNXo5islWUXqeDc3RcnW3kq0 XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrDafZn\npTs0KJFNgeVnUhKanB29ONy+tm nUmTAgPMaKKw==\n-----END CERTIFICATE-----\n the firewall list of the host 192.168.10.41 is: [root@ooengh1 ~]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: bond0 ovirtmgmt sources: services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt-vmconsole snmp ssh vdsm ports: 6900/tcp 22/tcp 6081/udp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: the follow file is the connect file that vm that cannot connect using remote viewer: [virt-viewer] type=vnc host=ohost1.tltd.com port=5900 password=4/jWA+RLaSZe # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=testol:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 secure-attention=ctrl+alt+end versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6 :99.0-1 newer-version-url=http://www.ovirt.org/documentation/admin-guide/virt/consol e-client-resources [ovirt] host=ooeng.tltd.com:443 vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a sso-token=4Up7TfLLBjSuQgPkQvRz3D-fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esct m3Im4tz80mE1DjrNT3XQ admin=1 ca=-----BEGIN CERTIFICATE-----\nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBh MCVVMxETAPBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAe Fw0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDVQQKDA h0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0GCSqGSIb3DQEB AQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/JmKeJAUVZqNKRg1q80Ip WyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44ysvCWfU0SBk/ZPnKmQ58o5MlSk idHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqwLrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLI ffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DKE4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLM wohz7wgtgsDA36277mujNyMjMbrSFheu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAA Gjga0wgaowHQYDVR0OBBYEFDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOM qN8+QhCP7DAkqF3RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHT AbBgNVBAMMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1Ud DwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmjrLZGyh 5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjdrHvhfbZFnZsGe 2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4pHS04c2+4JMhpe+hxgsO 2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nVWw+QNXo5islWUXqeDc3RcnW3kq0 XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/jrDafZn\npTs0KJFNgeVnUhKanB29ONy+tm nUmTAgPMaKKw==\n-----END CERTIFICATE-----\n the firewall list of the host ohost1.tltd.com(192.168.10.160) is: [root@ohost1 ~]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: bond0 ovirtmgmt sources: services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt-vmconsole snmp ssh vdsm ports: 22/tcp 6081/udp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Please give me some advice,thanks.

1 0

v2v-conversion-host-wrapper binary missing, unable to perform host conversion task
by dhanaraj.ramesh＠yahoo.com 13 Jan '21

13 Jan '21

As part of VMware to Ovirt vm migration I'm trying to integrate ovirt cluster to cloudform and make one of the ovirt node - CentOS 8.2 to conversion host, but unfortunately when I preparing conversion host using cloudform ansible playbook, unable to install v2v-conversion-host-wrapper package. up on checking found that the specified package is not available in yum repo,... Any help appreciated.

2 2

Re: VM console does not work with new cluster.
by eevans＠digitaldatatechs.com 12 Jan '21

12 Jan '21

Are you using IP or dns? Has the IP changed? Host IP? Vm id? It sounds like virt viewer cannot find it's target. Connecting with spice or vnc? What do your logs say about the connection? Look at event viewer after a try and see what's in the application log. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 1:08 PM To: eevans(a)digitaldatatechs.com; 'Strahil Nikolov' <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Stop/Edit/Start is the only mechanism available. You cannot change the cluster value for a VM, until it is stopped. The VMs have static addresses. The VM is fully function on the new cluster. It’s just that once the VM has been moved to the new cluster, selecting console results in the same behavior, but that virt-viewer starts and stops within a second. -----Original Message----- From: eevans(a)digitaldatatechs.com <eevans(a)digitaldatatechs.com> Sent: Tuesday, January 12, 2021 11:40 AM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com>; 'Strahil Nikolov' <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: RE: [ovirt-users] Re: VM console does not work with new cluster. Did you shut down the vm's and start them up on the new cluster? It sounds like they are associated with the default still and that's where virt viewer is looking for them.. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 12:29 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Sounds like it, but VMs are running on the same network, with the same IP address. The only firewall involved are on the hosts, and they are both firewalld, and have the same ports and service permitted. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, January 10, 2021 10:57 PM To: users(a)ovirt.org; Stier, Matthew <Matthew.Stier(a)fujitsu.com> Subject: Re: [ovirt-users] VM console does not work with new cluster. This sounds like firewall issue. Best Regards, Strahil Nikolov В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier <matthew.stier(a)fujitsu.com> написа: I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL… _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANL… _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RFYNLB53ALNIT…

2 1

Re: VM console does not work with new cluster.
by Strahil Nikolov 12 Jan '21

12 Jan '21

> It’s just that once the VM has been moved to the new cluster, > selecting console results in the same behavior, but that virt-viewer > starts and stops within a second. In order to debug, you will need to compare the files provided when you press the "console" button from both clusters and identify the problem. Have you compared the firewalld ports on 2 nodes (old and new cluster) ? Best Regards, Strahil Nikolov

1 0

Re: VM console does not work with new cluster.
by eevans＠digitaldatatechs.com 12 Jan '21

12 Jan '21

Did you shut down the vm's and start them up on the new cluster? It sounds like they are associated with the default still and that's where virt viewer is looking for them.. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Tuesday, January 12, 2021 12:29 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Sounds like it, but VMs are running on the same network, with the same IP address. The only firewall involved are on the hosts, and they are both firewalld, and have the same ports and service permitted. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, January 10, 2021 10:57 PM To: users(a)ovirt.org; Stier, Matthew <Matthew.Stier(a)fujitsu.com> Subject: Re: [ovirt-users] VM console does not work with new cluster. This sounds like firewall issue. Best Regards, Strahil Nikolov В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier <matthew.stier(a)fujitsu.com> написа: I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL… _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANL…

2 1

VM console does not work with new cluster.
by Matthew Stier 12 Jan '21

12 Jan '21

I've added several new hosts to my data center, and instead of adding them to my 'default' cluster, I created a new cluster ('two'). I can access the VM console (virt-viewer) when the VM is on the 'default' cluster, but once moved to the the new cluster, virt-viewer pops up and disappears in sub-second fashion. Moving the VM back to 'default', restores access. I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months) I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts. The new ('two') cluster hosts are connected to the same networks as the original systems ('default'). (They have the same assigned IP address.) Firewalld is reporting the same ports and services enabled on 'default' and 'two' hosts. The VM's are not running firewalls. Apparently I'm missing something.

3 2