January 2019 - Users - oVirt List Archives

Import existing storage domain into new server
by michael＠wanderingmad.com 15 Jan '19

15 Jan '19

I had original ovirt-engine that had stuck tasks and just had storage issues. I decided to load a new engine appliance and import existing servers and VMs into new engine. This actually worked perfect until I went to import the storage domain into new engine, which has failed. I was unable to move the domain to maintenance mode or anything from the old engine. Any way to force import? Error messages / logs: Failed to attach Storage Domains to Data Center Default. (User: admin@internal-authz) (in GUI log) engine.log: 2019-01-13 16:31:27,973-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler8) [176267b0] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 2e7162ed 2019-01-13 16:31:28,204-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,205-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,206-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,208-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,209-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,221-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) [176267b0] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:28,232-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler8) [176267b0] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 2e7162ed 2019-01-13 16:31:37,612-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler10) [2876ae97] START, GlusterTasksListVDSCommand(HostName = daedalus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b79fe49c-761f-4710-adf4-8fa6d1143dae'}), log id: 30c3bd7c 2019-01-13 16:31:37,863-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler10) [2876ae97] FINISH, GlusterTasksListVDSCommand, return: [], log id: 30c3bd7c 2019-01-13 16:31:43,248-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] START, GlusterServersListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 7f890a8 2019-01-13 16:31:43,705-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] FINISH, GlusterServersListVDSCommand, return: [10.100.50.12/24:CONNECTED, icarus.redforest.wanderingmad.com:CONNECTED, daedalus.redforest.wanderingmad.com:CONNECTED], log id: 7f890a8 2019-01-13 16:31:43,708-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 50f59aca 2019-01-13 16:31:43,943-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,944-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,945-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,947-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,948-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,949-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [70a256c0] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:43,949-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler7) [70a256c0] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 50f59aca 2019-01-13 16:31:58,987-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] START, GlusterServersListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, VdsIdVDSCommandParametersBase:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 512ef5c0 2019-01-13 16:31:59,518-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] FINISH, GlusterServersListVDSCommand, return: [10.100.50.12/24:CONNECTED, icarus.redforest.wanderingmad.com:CONNECTED, daedalus.redforest.wanderingmad.com:CONNECTED], log id: 512ef5c0 2019-01-13 16:31:59,521-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] START, GlusterVolumesListVDSCommand(HostName = prometheus.redforest.wanderingmad.com, GlusterVolumesListVDSParameters:{hostId='b5b9e763-704c-47ee-817b-19d081ad9aab'}), log id: 2de38416 2019-01-13 16:31:59,773-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,774-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.14:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,775-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.12:/gluster_bricks/nvme-storagetwo/nvme-storagetwo' of volume 'fe0c3620-6a33-48fa-98b7-847ad76edaba' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,776-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick 'Daedalus.redforest.wanderingmad.com:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,777-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.14:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,778-05 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4) [59b635f4] Could not associate brick '10.100.50.12:/gluster_bricks/ssd-storagetwo/ssd-storagetwo' of volume '7add3797-9b03-433c-aa1a-90ad7c5ac280' with correct network as no gluster network found in cluster '8e8cc8a7-9f45-4054-85e5-8014ec421b7f' 2019-01-13 16:31:59,778-05 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler4) [59b635f4] FINISH, GlusterVolumesListVDSCommand, return: {7add3797-9b03-433c-aa1a-90ad7c5ac280=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@4205765f, fe0c3620-6a33-48fa-98b7-847ad76edaba=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@40fccb}, log id: 2de38416 and of course, none of the gluster hosts is set as the SPM

2 2

unable to create templates or upload files
by michael＠wanderingmad.com 15 Jan '19

15 Jan '19

ovirt stopped accepting new deployments or uploading ISOs, they just stay as locked disks. I checked ovirt-engine log and see constant errors like below: ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-2) [] OAuthException access_denied: Cannot authenticate user 'admin@N/A': No valid profile found in credentials.. I checked the ovn provider in the admin portal and it's set correctly to "admin@internal" for the ovn provider

2 1

External private ova / image repository
by Leo David 15 Jan '19

15 Jan '19

Hello Everyone, I am not sure what would it be the pieces needed to have an external repo that I can manage and use at the client site for downloading customized templates. ie: how an external docker repo works Any ideeas on this ? Thank you ! Have a nice day, Leo

1 1

oVirt Node install - kickstart postintall
by jeanbaptiste＠nfrance.com 14 Jan '19

14 Jan '19

Hello everybody, Since days, I'm trying to install oVirt (via Foreman) in network mode (TFTP net install). All is great, but I want to make some actions in postinstall (%post). Some actions are relatated to /etc/sysconfig/network-interfaces and another action is related to root authorized_keys. When I try to add pub-key to a created authorized_keys for root, I work (verified into anaconda. But after installation and anaconda reboot, I've noticed all my %post actions in /(root) are discared. After reboot, there is nothing in /root/.ssh for example. Whereas, in /etc, all my modications are preserved. I thought to a Selinux relative issue, but It is not relative to Selinux I miss something. Please can you help to understand how oVirt install / partition work ? thanks for all

2 1

Ovirt 4.3 / New Install / NFS (broken)
by Devin Acosta 14 Jan '19

14 Jan '19

I installed the latest 4.3 release candidate and tried to add an NFS mount to the Data Center, and it errors in the GUI with “Error while executing action New NFS Storage Domain: Invalid parameter”, then in the vdsm.log I see it is passing “block_size=None”. Does this regardless if NFS v3 or v4. InvalidParameterException: Invalid parameter: 'block_size=None' 2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] START createStorageDomain(storageType=1, sdUUID=u'b30c64c4-4b1f-4ebf-828b-e54c330ae84c', domainName=u'nfsdata', typeSpecificArg=u'192.168.19.155:/data/data', domClass=1, domVersion=u'4', block_size=None, max_hosts=2000, options=None) from=::ffff:192.168.19.178,51042, flow_id=67743df7, task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:48) 2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] FINISH createStorageDomain error=Invalid parameter: 'block_size=None' from=::ffff:192.168.19.178,51042, flow_id=67743df7, task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:52) 2019-01-12 20:37:58,241-0700 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='ad82f581-9638-48f1-bcd9-669b9809b34a') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in createStorageDomain File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2583, in createStorageDomain alignment = clusterlock.alignment(block_size, max_hosts) File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py", line 661, in alignment raise se.InvalidParameterException('block_size', block_size) InvalidParameterException: Invalid parameter: 'block_size=None' 2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [storage.TaskManager.Task] (Task='ad82f581-9638-48f1-bcd9-669b9809b34a') aborting: Task is aborted: u"Invalid parameter: 'block_size=None'" - code 100 (task:1181) 2019-01-12 20:37:58,242-0700 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH createStorageDomain error=Invalid parameter: 'block_size=None' (dispatcher:81) 2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call StorageDomain.create failed (error 1000) in 0.00 seconds (__init__:312) 2019-01-12 20:37:58,541-0700 INFO (jsonrpc/1) [vdsm.api] START disconnectStorageServer(domType=1, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'tpgt': u'1', u'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350', u'connection': u'192.168.19.155:/data/data', u'iqn': u'', u'user': u'', u'ipv6_enabled': u'false', u'protocol_version': u'auto', u'password': '********', u'port': u''}], options=None) from=::ffff:192.168.19.178,51042, flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c, task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:48) 2019-01-12 20:37:58,542-0700 INFO (jsonrpc/1) [storage.Mount] unmounting /rhev/data-center/mnt/192.168.19.155:_data_data (mount:212) 2019-01-12 20:37:59,087-0700 INFO (jsonrpc/1) [vdsm.api] FINISH disconnectStorageServer return={'statuslist': [{'status': 0, 'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350'}]} from=::ffff:192.168.19.178,51042, flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c, task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:54) 2019-01-12 20:37:59,089-0700 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call StoragePool.disconnectStorageServer succeeded in 0.55 seconds (__init__:312) Devin Acosta

6 9

Trunk VLAN Ovirt 4.2
by Sebastian Antunez N. 14 Jan '19

14 Jan '19

Hello Guys Have a lab with 6 nodes Ovirt 4.2. All nodes have 4 nic 1GB and two nic are for Management and and I will assign two nic in bonding for VM traffic My problem is the following. The switch Cisco have 2 VLAN (56 and 57) and I need to be able to create a new network with the two vlan but I am not clear how to make it so that the vlan go through this created network. I have read that I must create a network with vlan 56 for example and assign it an IP, and then create the network with vlan 57 and assign it an IP and later assign it to bonding. Is what I indicate or should another process be correct? Thanks for the help. Sebastian

2 1

Re: [ovirt-devel] Hard disk requirement
by Nir Soffer 13 Jan '19

13 Jan '19

On Sun, Jan 13, 2019 at 6:18 PM Hetz Ben Hamo <hetz(a)hetz.biz> wrote: > Hi, > > The old oVirt (3.x?) ISO image wasn't requiring a big hard disk in order > to install the node part on a physical machine, since the HE and other > parts were running using NFS/iSCSI etc. > > oVirt 4.X if I understand correctly - does require hard disk on the node. > I think you can setup temporary storage on a diskless host using NFS or by connecting to temporary LUN and setting up a file system on it. Once the bootstrap engine is ready on the "local" storage, you we move engine disk to shared storage, and you can remove the local storage. Adding Simone to add more info. > Can this requirement be avoided and just use an SD Card? Whats the minimum > storage for the local node? > Another option is to use /dev/shm, if you have a server with lot of memory. Note that this list is for ovirt developers. This question is more about using ovirt, so the users mailing list is better. Others users may already solved this issue and can help more than developers which have much less experience with actual deployment. Nir

1 0

hosted-engine deploy Restore from backup failure
by Callum Smith 12 Jan '19

12 Jan '19

Restoring from backup appears to work perfectly, until it decides it hasn't worked and throws out. I can't see any relevant error here, does anyone have any insight? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

2 1

Ovirt VDI Solution network issue
by mdcarr＠meditech.com 11 Jan '19

11 Jan '19

Hello, first time poster looking for help on setting up the network for a VDI deployment. A little background, I have Ovirt engine running on a Vmware virtual machine and have added a physical host to serve up virtual machines running windows 7 to our developers. The host has a static IP address and when I create a virtual machine I can see the default network is attached and up but does not receive an IP address. It does have a MAC so I'm wondering if I need to have our network team assign an IP for that MAC? I will be creating around 20 vm's that would get wiped after use so assigning static ip's might cause issues. Am I missing something or is there a better way to setup the LAN for this host? Thanks for any help!

3 4

Hypervisor host CPU utilization metrics
by Sigbjorn Lie-Soland 11 Jan '19

11 Jan '19

Hi, Linux see twice the amount of CPUs for a host with SMT/hyperthreading enabled. Inspecting the individual cores presented to the operating system using mpstat shows that the guests are running primarily on the “physical cores”, which is expected as the system is SMT aware. The “hyperthreaded cores” are showing guest activity when the host cpu is heavily loaded. Using the traditional tools such as top and vmstat does not take hyperthreading into consideration when calculating the total cpu% usage, again, as expected. How is the hypervisor host CPU utilization metrics in Ovirt calculated when a hypervisor host has SMT/hyperthreading enabled? Does Ovirt calculate in the same manner as the traditional vmstat/top/etc Linux tools, or does it only count CPU usage on the “physical cores” on the hypervisor? Does it read CPU metrics from the Intel PCM (https://github.com/opcm/pcm <https://github.com/opcm/pcm>) ? Does the “Count Threads as Cores” setting affect how the host hypervisor CPU utilization metrics are calculated? The reason for asking is when using tools for capacity and utilization reporting to attempt to establish cluster growth and to anticipate when and how much hypervisor capacity to add, we need the input utilization data to be a correct representation of what is happening at the hypervisor host. Thanks. Regards, Siggi

1 0

exporting VMs using vdsm-client
by Callum Smith 11 Jan '19

11 Jan '19

Is it possible to export VMs using vdsm-client to import into a new oVirt engine in a case of catastrophic failure such that they can be imported into a new setup? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

1 0

[ANN] oVirt 4.3.0 First Release Candidate is now available for testing
by Sandro Bonazzola 11 Jan '19

11 Jan '19

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 4.3.0, as of January 10th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 120 enhancements and more than 420 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * LLDP Labeler * Support of Neutron from RH OSP 13 as external network provider * Support of using Skydive from RH OSP 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for both CentOS 7 and Fedora 28 (tech preview). Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * 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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 2

quota_name field length missmatch in db schema
by Pavel Šipoš 11 Jan '19

11 Jan '19

Hi! We have a problem with Quotas whose name has a length grater than 60 characters. Such quotas can be created (or renamed) through oVirt-shell but cannot be managed through the oVirt Engine interface. E.g. VMs in that quota can't be started, created, quota comment can't be added... It turns out that the problem is with the engine database definition of "audit_log" table, that declares "quota_name" column as "character varying(60)". However "quota.quota_name" is defined as "character varying(65)". I think this is a bug and should be fixed in the future. Error example: PL/pgSQL function insertauditlog(integer,timestamp with time zone,integer,character varying,integer,text,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,character varying,uuid,uuid,character varying,text,boolean,uuid,text) line 9 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: value too long for type character varying(60) Regards, Pavel

2 1

Datacenter Down Storage error
by ahuser＠web.de 10 Jan '19

10 Jan '19

Hi @all, I have a big problem with my datacenter. After pressing optimization for vm-storage in a active gluster volume are the vms paused. And now, i cant activate the storage in the Data-Center. I have try reboot all Servers. It runs the latest Stable ovirt Version: ovirt-engine-4.2.7.5-1.el7.noarch vdsm-gluster-4.20.43-1.el7.x86_64 glusterfs-3.12.15-1.el7.x86_64 All Servers Up-to Date. Centos 7.6 Gluster Volume Replica 3 with Arbiter /var/log/sanlock.log set scheduler RR|RESET_ON_FORK priority 99 failed: Operation not permitted VDSM ovnode3 command SpmStatusVDS failed: (22, 'Sanlock resource read failure', 'Invalid argument') can anybody help me? thx

2 1

JSON internal error setting bonding using vdsm-client
by Callum Smith 10 Jan '19

10 Jan '19

Dear All, I’m getting the error: “(code=32603, message=Internal JSON-RPC error: {‘reason’: “‘unicode’ object has no attribute ’sort’”}) when trying to apply networking configuration with vdsm-client -f bond.json Host setupNetworks bond.json contains: { “networks”: {}, “bondings”: { “bond0”: { “nics”: “eno1+eno2”, “options”: “mode=4” } }, “options”: {} } Of course python is handling all the arguments as unicode entities rather than strings. Any idea what might be wrong? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

2 1

File level restore of a VM backup located in export domain in Overt
by kevin.doyle＠manchester.ac.uk 10 Jan '19

10 Jan '19

Hi I would like to create backups of VM's using cron. I have installed and ran https://github.com/wefixit-AT/oVirtBackup This works well and saves an image to the export domain I created. I can also carry out a full restore from this by importing from the export domain and selecting the backup. The question I have is how to do a single file recovery from the backup image. I would like to restore /etc/hosts just as an example. What command would I use ? I am not sure of the layout of the export domain directory ── dom_md │ ├── ids │ ├── inbox │ ├── leases │ ├── metadata │ └── outbox ├── images │ └── 622eb98e-f10b-4e96-bec5-8f0a7e7745fe │ ├── b47ce8e1-f552-47f8-af56-33a3b8ce7aed │ └── b47ce8e1-f552-47f8-af56-33a3b8ce7aed.meta └── master ├── tasks └── vms └── c6e6c49c-c9bc-4683-8b19-d18250b5697b └── c6e6c49c-c9bc-4683-8b19-d18250b5697b.ovf The largest file is found is in images folder so I assume this is the backup image ? ./images/622eb98e-f10b-4e96-bec5-8f0a7e7745fe: total 2.7G drwxr-xr-x. 2 vdsm kvm 99 Jan 10 11:48 . drwxr-xr-x. 3 vdsm kvm 50 Jan 10 11:48 .. -rw-rw----. 1 vdsm kvm 50G Jan 10 11:51 b47ce8e1-f552-47f8-af56-33a3b8ce7aed -rw-r--r--. 1 vdsm kvm 269 Jan 10 11:48 b47ce8e1-f552-47f8-af56-33a3b8ce7aed.meta # file b47ce8e1-f552-47f8-af56-33a3b8ce7aed b47ce8e1-f552-47f8-af56-33a3b8ce7aed: x86 boot sector; partition 1: ID=0x83, active, starthead 32, startsector 2048, 2097152 sectors; partition 2: ID=0x8e, starthead 170, startsector 2099200, 102758400 sectors, code offset 0x63 Any help would be appreciated, I am new to Ovirt regards Kevin

1 0

ovirt 4.2.7-1 - adding virtual host ( nested virt. )
by paf1＠email.cz 10 Jan '19

10 Jan '19

Hello guys, I've got problem with adding new host (ESX-virtual) to ovirt 4.2.7-1 ( gluster included) Is this feature supported ??? 2019-01-07 19:38:30,168+01 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler1) [15a4029b] Error while refreshing server data for cluster 'MID' from database: null regs. Paul

2 2

Trouble with my first ovirt-engine installation.
by benzianekarim67＠gmail.com 09 Jan '19

09 Jan '19

I'm having a certificate problem when I'm doing a "ym install ovirt-engine" Can someone help me thank you. [ovirt-4.2] name=Latest oVirt 4.2 Release #baseurl=http://resources.ovirt.org/pub/ovirt-4.2/rpm/el$releasever/ mirrorlist=https://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.2-el… enabled=1 skip_if_unavailable=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 Thank's

2 2

VMs Hung On Booting From Hard Disk
by Douglas Duckworth 09 Jan '19

09 Jan '19

Hi I have deployed 10 VMs in our oVirt cluster using Ansible. Thanks everyone for helping get it working. However, I randomly run into issues where the OS won't load after completing kickstart installation. As you can see the disks are attached while we are booting to it however I keep getting a hang at "booting from hard disk." The kickstart, kernel, and everything else for this VM, matches others. I am unsure why this problem occurs. I have attached repeating vdsm errors from the host which has the VM. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690

1 0

Re: move 'ovirtmgmt' bridge to a bonded NIC team
by Dominik Holler 09 Jan '19

09 Jan '19

On Tue, 8 Jan 2019 17:01:38 +0000 Shawn Southern <shawn.southern(a)entegrus.com> wrote: >We've recently added additional NICs to our oVirt nodes, and want to move the ovirtmgmt interface to one of the bonded interfaces, away from the single ethernet port currently used. This is to provide redundant connectivity to the nodes. > >I've not had any luck finding documentation on how to do this. If we change it manually by editing files in /etc/sysconfig/network-scripts, VDSM simply changes everything back. > Please use oVirt Engine to manage the network configuration. >I'm just looking to be pointed in the right direction here. > I see no reason why the usual way of configuring host networking via Compute > Hosts > hostname > Network Interfaces > Setup Host Networks should not work. ovirtmgmt must not be used by a VM on this host during the change, and ovirtmgmt should use a static IP address in Setup Host Networks > Edit management network: ovirtmgmt > IPv4. It might be a good idea to move the host to maintenance before the change, and ensure connectivity from the bond to oVirt Engine, because the change will be rolled back, if connectivity is lost. >Thanks!

1 0

[ANN] oVirt 4.2.8 Third Release Candidate is now available
by Sandro Bonazzola 09 Jan '19

09 Jan '19

The oVirt Project is pleased to announce the availability of the oVirt 4.2.8 Third Release Candidate, as of January 9th, 2019. This update is a release candidate of the eighth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] Additional Resources: * Read more about the oVirt 4.2.8 release highlights: http://www.ovirt.org/release/4.2.8/ * 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.2.8/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

oVirt upgrade 4.1 to 4.2
by p.staniforth＠leedsbeckett.ac.uk 09 Jan '19

09 Jan '19

Hello when we did a live upgrade of our VDC from 4.1 to 4.2 we had a large number of VMs running that had a Custom Compatibility Version set to 4.1 to allow them to keep running while the cluster and VDC were upgraded. Unfortunately there was a large number of snapshots taken be the users before they were restarted their VMs so they have the Custom_Compatibility_Version set to 4.1 and so can't run in the 4.2 VDC, is there a way to search for them in the API or SDK because I can only find them in the events log when they fail to start. Thanks, Paul S.

2 1

[Cannot edit VM. Maximum number of sockets exceeded.]
by Matthias Leopold 09 Jan '19

09 Jan '19

Hi, when a user is managing a "higher number" (couldn't find the exact number yet, roughly >10) of VMs in VM Portal and wants to edit a VM he gets a "[Cannot edit VM. Maximum number of sockets exceeded.]" error message in the browser, which I also see in engine.log. I couldn't find the reason for this. I'm using squid as a SPICE Proxy at cluster level. oVirt version is 4.2.7, can anybody help me? thx matthias

3 4

ISCSI Domain & LVM
by tehnic＠take3.ro 09 Jan '19

09 Jan '19

Hello all, i have a question regarding this note in ovirt storage documentation: **Important:** If you are using block storage and you intend to deploy virtual machines on raw devices or direct LUNs and to manage them with the Logical Volume Manager, you must create a filter to hide the guest logical volumes. This will prevent guest logical volumes from being activated when the host is booted, a situation that could lead to stale logical volumes and cause data corruption. What does "you must create a filter to hide the guest logical volumes" exactly mean? I assume i have to set some filter in lvm.conf on all ovirt hosts, but im not sure about what to filter? What i already saw is that after creating the ISCSI domain and cloning/moving/creating virtual machines on it there are new PVs and LVs visible on the ovirt hosts having an object UUID in the name (output from "pvs" and "lvs" commands). Is this expected behavior or do i have to filter exactly this ones by allowing only local disks to be scanned for PVs/LVs? Or do i have to setup filter to allow only local disks + ISCSI disks (in my case /dev/sd?) to be scanned for PVs/LVs? I noticed too that after detaching and removing the ISCSI domain i still have UUID PVs. They all show up with "input/output error" in the output of "pvs" and stay there until i reboot the ovirt hosts. On my ISCSI target system i already set the correct lvm filters so that "targetcli" is happy after reboot. Thank you! Happy new year, Robert

4 11

Shutdown VMs when Nobreak is on Battery
by Vinícius Ferrão 08 Jan '19

08 Jan '19

Hello, I would like to know if oVirt support VMs shutdown when a battery threshold on the nobreak device is reached. There are some fencing agents for APC devices, so I’m hoping this is supported. If not, how are you guys doing this kind of thing? A separate device or VM in the datacenter to issue the shutdown commands? Thanks,

1 0