- Users - oVirt List Archives

Windows service applications migrated to the ovirt platform
by xilazz＠126.com 26 Feb '19

26 Feb '19

Hi，I now have a physical machine on which I want to migrate Windows applications to the ovirt management platform. May I ask if virt-p2v can be used for migration? Does ovirt itself have a migration tool to use?

1 0

Re: oVirt Node install failed
by Strahil 26 Feb '19

26 Feb '19

What is the output of 'hosted-engine --vm-status' from the host that is hosting the HostedEngine VM? Best Regards, Strahil NikolovOn Feb 26, 2019 05:50, kiv(a)intercom.pro wrote: > > The crown icon on the left of the second host is gray. When I try to migrate the engine, I get the error: > > Migration of VM 'HostedEngine' to host 'ovirt2' failed: VM destroyed during the startup > EVENT_ID: VM_MIGRATION_NO_VDS_TO_MIGRATE_TO(166), No available host was found to migrate VM HostedEngine to. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NHG7MBNCPYMSX…

3 2

Python-SDK4- Issue following links
by Don Dupuis 26 Feb '19

26 Feb '19

Hi I am trying to write some code to update the names of existing vnicprofiles in ovirt-4.2. The problem I am having is trying to follow the links to the vnicprofiles. Below is web info that I am trying to get: <network href="/ovirt-engine/api/networks/740cae1f-c49f-4563-877a-5ce173e83be4" id="740cae1f-c49f-4563-877a-5ce173e83be4"><name>ovirtmgmt</name><description>LOOKING</description><comment/><link href="/ovirt-engine/api/networks/740cae1f-c49f-4563-877a-5ce173e83be4/permissions" rel="permissions"/><link href="/ovirt-engine/api/networks/740cae1f-c49f-4563-877a-5ce173e83be4/vnicprofiles" rel="vnicprofiles"/><link href="/ovirt-engine/api/networks/740cae1f-c49f-4563-877a-5ce173e83be4/networklabels" rel="networklabels"/><mtu>0</mtu><stp>false</stp><usages><usage>vm</usage></usages><vlan id="4050"/><data_center href="/ovirt-engine/api/datacenters/1d00d32b-abdc-43cd-b990-257aaf01d514" id="1d00d32b-abdc-43cd-b990-257aaf01d514"/></network> Below is the code that I am trying to do the same thing and I want to follow the vnicprofiles link to get to the actual data that I want to change: #!/usr/bin/env python import logging import time import string import sys import os import MySQLdb import ovirtsdk4 as sdk import ovirtsdk4.types as types #logging.basicConfig(level=logging.DEBUG, filename='/tmp/addhost.log') ### Variables to be used ### #NUMANODE = 3 #MEM = 20 GB = 1024 * 1024 * 1024 #MEMORY = MEM * GB GB = 1024 * 1024 * 1024 URL = 'https://host/ovirt-engine/api' CAFILE = '/etc/pki/ovirt-engine/ca.pem' USERNAME = 'admin@internal' PASSWORD = 'password' HOSTNAME = 'rvs06' connection = sdk.Connection( url=URL, username=USERNAME, password=PASSWORD, # ca_file='ca.pem', debug='True', insecure='True', # log=logging.getLogger(), ) #dcs_service = connection.system_service().data_centers_service() #dc = dcs_service.list(search='cluster=%s-local' % HOSTNAME)[0] #network = dcs_service.service(dc.id).networks_service() networks_service = connection.system_service().networks_service() network = networks_service.list( search='name=ovirtmgmt and datacenter=%s-local' % HOSTNAME) [0] print ("Network name is %s" % network.name) print ("Network id is %s" % network.id) vnic = connection.follow_link(network.vnicprofiles) connection.close() Below is the output of my code: ./update-vnic.py Network name is ovirtmgmt Network id is 740cae1f-c49f-4563-877a-5ce173e83be4 Traceback (most recent call last): File "./update-vnic.py", line 46, in <module> vnic = connection.follow_link(network.vnicprofiles) AttributeError: 'Network' object has no attribute 'vnicprofiles' The network name and network id is correct. Any help would be appreciated on what I am missing or what I am doing wrong. The actual updating of the name with code isn't written yet as I can't get past this part. Thanks Don

2 7

Unrecognized message received error when ISO domain is put in Maintenance
by Wood Peter 26 Feb '19

26 Feb '19

Hi all, We are running oVirt 4.1.1 on engine and nodes. The ISO storage domain is NFS. Everything has been working great for years. Now I need to move the ISO and Export domains to a different storage server. When I put the ISO domain in maintenance the Master domain and the Export domain start flipping active-non active. The Events tab in the Web UI shows this message scrolling every 30 sec. or so: "Datacenter is being initialized. Please wait for initialization to complete" ... but it never completes. It also starts cycling the SPM assignment from one node to another. As soon as I activate back the ISO domain everything calms down and no more errors are recorded in the logs. In engine.log I see this "Unrecognized message received" error: 2019-02-25 19:45:20,467-08 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages Unrecognized message received 2019-02-25 19:45:20,481-08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler6) [76363b98] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), Correlation ID: null, Call Stack: null, Custom E vent ID: -1, Message: VDSM command GetStoragePoolInfoVDS failed: Unrecognized message received 2019-02-25 19:45:20,481-08 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (DefaultQuartzScheduler6) [76363b98] ERROR, org.ovirt.engine.core.vdsbroker.irsbroker.GetStoragePoolInfoVDSCommand, exception: VDSGenericExce ption: VDSNetworkException: Unrecognized message received , log id: 1635c439 2019-02-25 19:45:20,481-08 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (DefaultQuartzScheduler6) [76363b98] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetwor kException: Unrecognized message received In vdsm.log on the nodes I see this: 2019-02-25 19:45:29,817-0800 ERROR (upgrade/b5b7a10) [storage.StoragePool] Unhandled exception (utils:371) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 232, in _upgradePoolDomain self._finalizePoolUpgradeIfNeeded() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state And I believe that after that error it moves the SPM to another host, gets the same error and continues moving it to the next host and so on. I really need to move the ISO and Export domains to a different storage server. Any idea what is causing this or how to fix it? Appreciate any help. Thanks, -- Peter

1 0

/boot partition of oVirt node missing after reboot
by andy.law＠hactlsolutions.com 26 Feb '19

26 Feb '19

I've installed oVirt Node 4.2 on one of my servers. Recently I've upgraded the kernel version to 3.10.0-957.5.1.el7.x86_64. After such update, I've rebooted the server to take effect and then the /boot partition cannot be recognized. The server then enters emergency mode and I've tried to run the command blkid but I cannot find the uuid of /boot and /boot/efi. Before reboot: # blkid /dev/mapper/onn-var_crash: UUID="2aa920d6-c2d2-4313-8df1-8be16a5718ae" TYPE="ext4" /dev/mapper/3600508b1001cede21ec59eb753184259p3: UUID="Vy9K1K-e4uI-oM73-blSV-eU29-FnZP-3FIh4Y" TYPE="LVM2_member" PARTUUID="57cfd006-60d0-4826-8f58-6d11d4e1cb94" /dev/mapper/3600508b1001cede21ec59eb753184259p1: SEC_TYPE="msdos" UUID="7408-0A3B" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="56cadb64-9099-4ec8-9c0c-94596c80b2a9" /dev/mapper/3600508b1001cede21ec59eb753184259p2: UUID="3e920048-3b2e-4c09-b507-c9debe7d98f0" TYPE="ext4" PARTUUID="9ee53bdd-3051-443b-960f-9801d7245d33" /dev/mapper/onn-ovirt--node--ng--4.2.7.1--0.20181219.0+1: UUID="111ed68a-a7e8-4b17-8add-5c8fd9035bbc" TYPE="ext4" /dev/mapper/onn-swap: UUID="0fcbdcfe-92da-43d4-a773-ef6f7dac0556" TYPE="swap" /dev/mapper/onn-var_log_audit: UUID="48531956-48cc-4faa-9dfc-e7baaab89b3b" TYPE="ext4" /dev/mapper/onn-var_log: UUID="15c57452-0333-4a9a-a8e6-220155e819b3" TYPE="ext4" /dev/mapper/onn-var: UUID="772613a5-be4f-4044-8b95-c846852f5421" TYPE="ext4" /dev/mapper/onn-tmp: UUID="1ee263bf-9dcb-46e8-92f7-f21a8c87eeb5" TYPE="ext4" /dev/mapper/onn-home: UUID="738d2e6f-d7e0-4d3a-acc0-6db1392a0222" TYPE="ext4" /dev/sdc: UUID="e2pRkW-V1Vd-XxqK-5PBK-5Vtb-8Mgr-YjgB1M" TYPE="LVM2_member" /dev/mapper/360060e80122ed80050402ed800000a00: UUID="e2pRkW-V1Vd-XxqK-5PBK-5Vtb-8Mgr-YjgB1M" TYPE="LVM2_member" /dev/sdd: UUID="WlBAsN-q2YR-vYGL-Syx4-HJ30-CbVk-v2Q7yt" TYPE="LVM2_member" /dev/mapper/360060e80122ed80050402ed800000a01: UUID="WlBAsN-q2YR-vYGL-Syx4-HJ30-CbVk-v2Q7yt" TYPE="LVM2_member" /dev/sde: UUID="e2pRkW-V1Vd-XxqK-5PBK-5Vtb-8Mgr-YjgB1M" TYPE="LVM2_member" /dev/sdf: UUID="WlBAsN-q2YR-vYGL-Syx4-HJ30-CbVk-v2Q7yt" TYPE="LVM2_member" /dev/mapper/c0d0ef19--826b--44d7--a380--658adb915964-master: UUID="a409bf9f-63b6-42ac-8759-038f1bc3337f" TYPE="ext3" /dev/mapper/e399fd7f--c884--4e3d--89cf--7d8ddae16058-master: UUID="887319bd-d3e4-4dfe-9f8c-3e4ee2498ccb" SEC_TYPE="ext2" TYPE="ext3" /dev/mapper/3600508b1001cede21ec59eb753184259: PTTYPE="gpt" /dev/sdb: PTTYPE="gpt" /dev/mapper/c0d0ef19--826b--44d7--a380--658adb915964-a72e9370--0649--4e6f--b10a--1015b6b2134f: PTTYPE="dos" #cat /etc/fstab /dev/onn/ovirt-node-ng-4.2.7.1-0.20181219.0+1 / ext4 defaults,discard 1 1 UUID=3e920048-3b2e-4c09-b507-c9debe7d98f0 /boot ext4 defaults 1 2 UUID=7408-0A3B /boot/efi vfat umask=0077,shortname=winnt 0 0 /dev/mapper/onn-home /home ext4 defaults,discard 1 2 /dev/mapper/onn-tmp /tmp ext4 defaults,discard 1 2 /dev/mapper/onn-var /var ext4 defaults,discard 1 2 /dev/mapper/onn-var_log /var/log ext4 defaults,discard 1 2 /dev/mapper/onn-var_log_audit /var/log/audit ext4 defaults,discard 1 2 /dev/mapper/onn-swap swap swap defaults 0 0 Any ideas what caused this?

1 0

Stuck completing last step of 4.3 upgrade
by Jayme 25 Feb '19

25 Feb '19

Environment setup: 3 Host HCI GlusterFS setup. Identical hosts, Dell R720s w/ Intel E5-2690 CPUs 1 default data center (4.2 compat) 1 default cluster (4.2 compat) Situation: I recently upgraded my three node HCI cluster from Ovirt 4.2 to 4.3. I did so by first updating the engine to 4.3 then upgrading each ovirt-node host to 4.3 and rebooting. Currently engine and all hosts are running 4.3 and all is working fine. To complete the upgrade I need to update cluster compatibility to 4.3 and then data centre to 4.3. This is where I am stuck. The CPU type on cluster is "Intel SandyBridge IBRS Family". This option is no longer available if I select 4.3 compatibility. Any other option chosen such as SandyBridge IBRS SSBD will not allow me to switch to 4.3 as all hosts must be in maintenance mode (which is not possible w/ self hosted engine). I saw another post about this where someone else followed steps to create a second cluster on 4.3 with new CPU type then move one host to it, start engine on it then perform other steps to eventually get to 4.3 compatibility. I tried to add a 4.3 cluster with gluster service and put one of my hosts in to maintenance mode but could not move it to the new cluster, it gave me an error about the host having gluster service. If I try to import gluster config in cluster add UI it fails in engine log with "SERVER_ALREADY_EXISTS_IN_ANOTHER_CLUSTER" My question is, what is the proper procedure for me to complete upgrading my three node HCI environment to 4.3 cluster compatibility along with changing CPU type? Do I really need to create a second cluster and move host(s) to it? If so how can I move an existing host with running gluster service to a new cluster? Thanks in advance!

7 20

Re: Problem deploying self-hosted engine on ovirt 4.3.0
by Strahil 25 Feb '19

25 Feb '19

Your /var/tmp is full. Clean it up a little bit and give it a try. Best Regards, Strahil Nikolov

1 0

Re: Ovirt Glusterfs
by Strahil 25 Feb '19

25 Feb '19

Hi Sahina, Thanks for your reply. Let me share my test results with gluster v3 . I have a 3-node hyperconverged setup with 1 Gbit/s network and SSD (sata-based) for LVM caching. Testing the bricks showed higher than the network performance. 1. Tested ovirt 4.2.7/4.2.8 with fuse mounts. Using 'dd if=/dev/zero of=/default/gluster/Mount point/from/ovirt bs=1M count=5000'. Results: 56MB/s directly on the mount point, 20+-2 MB/s from a VM. Reads on fuse mount point -> 500+ MB/s Disabling sharing increased performance from the fuse mount point, nothing beneficial from a VM. Converting the bricks of a volume to 'tmpfs' does not bring any performance gain for FUSE mount. 2. Tested ovirt 4.2.7/4.2.8 with gfapi - performance in VM -> approx 30 MB/s 3. Gluster native NFS (now deprecated) on ovirt 4.2.7/4.2.8 -> 120MB/s on mount point, 100+ MB/s in VM My current setup: Storhaug + ctdb + nfs-ganesha (ovirt 4.2.7/4.2.8) -> 80+-2 MB/s in the VM. Reads are around the same speed. Sadly, I didn't have the time to test performance on gluster v5 (ovirt 4.3.0) , but I haven't noticed any performance gain for the engine. My suspicion with FUSE is that when a gluster node is also playing the role of a client -> it still uses network bandwidth to communicate to itself, but I could be wrong. According to some people on the gluster lists, the FUSE performance is expected ,but my tests with disabled sharing shows better performance. Most of the time 'gtop' does not show any spikes and iftop shows that network usage is not going over 500 Mbit/s As I hit some issues with the deployment on 4.2.7 , I decided to stop my tests for now. Best Regards, Strahil Nikolov On Feb 25, 2019 09:17, Sahina Bose <sabose(a)redhat.com> wrote: > > The options set on the gluster volume are tuned for data consistency and reliability. > > Some of the changes that you can try > 1. use gfapi - however this will not provide you HA if the server used to access the gluster volume is down. (the backup-volfile-servers are not used in case of gfapi). You can change this using the engine-config tool for your cluster level. > 2. Change the remote-dio:enable to turn on client side brick caching. Ensure that you have a power backup in place, so that you don't end up with data loss in case server goes down before data is flushed. > > If you're seeing issues with a particular version of glusterfs, please provide gluster profile output for us to help identify bottleneck. (check https://docs.gluster.org/en/latest/Administrator%20Guide/Monitoring%20Workl… on how to do this) > > On Fri, Feb 22, 2019 at 1:39 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >> Adding Sahina >> >> Il giorno ven 22 feb 2019 alle ore 06:51 Strahil <hunter86_bg(a)yahoo.com> ha scritto: >>> >>> I have done some testing and it seems that storhaug + ctdb + nfs-ganesha is showing decent performance in a 3 node hyperconverged setup. >>> Fuse mounts are hitting some kind of limit when mounting gluster -3.12.15 volumes. >>> >>> 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/site/privacy-policy/ >>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7U5J4KYDJJS4W… >> >> >> >> -- >> >> SANDRO BONAZZOLA >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA >> >> sbonazzo(a)redhat.com

1 0

HC : JBOD or RAID5/6 for NVME SSD drives?
by Guillaume Pavese 25 Feb '19

25 Feb '19

Hi, We have been evaluating oVirt HyperConverged for 9 month now with a test cluster of 3 DELL Hosts with Hardware RAID5 on PERC card. We were not impressed with the performance... No SSD for LV Cache on these hosts but I tried anyway with LV Cache on a ram device. Perf were almost unchanged. It seems that LV Cache is its own source of bugs and problems anyway, so we are thinking going for full NVME drives when buying the production cluster. What would the recommandation be in that case, JBOD or RAID? Thanks Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

3 3

Re: HostedEngine Unreachable
by Simone Tiraboschi 25 Feb '19

25 Feb '19

On Mon, Feb 25, 2019 at 2:53 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi Simone, > > The name resolution is working fine. > > Running: > getent ahosts engine.sanren.ac.za > > gives the same output: > > 192.168.x.x STREAM engine.sanren.ac.za > 192.168.x.x DGRAM > 192.168.x.x RAW > The IP address being the engine IP Address. > > The hosts are on the same subnet as the HostedEngine. I can ping the hosts > from each other. There is a NATting device, that NATs the private IP > addresses to public IP addresses. From the hosts I can reach the internet, > but I cant ping from outside (security measure). We also using this device > to VPN to the cluster > > *[root@gohan ~]# virsh -r list* > * Id Name State* > *----------------------------------------------------* > * 13 HostedEngine running* > > *[root@gohan ~]# virsh -r dumpxml HostedEngine | grep -i tlsPort > <graphics type='spice' port='5901' tlsPort='5902' autoport='yes' > listen='192.168.x.x' passwdValidTo='1970-01-01T00:00:01'>* > > *[root@gohan ~]# virsh -r vncdisplay HostedEngine* > *192.168.x.x:0* > > *[root@gohan ~]# hosted-engine --add-console-password* > *Enter password:* > > *You can now connect the hosted-engine VM with VNC at 192.168.x.x:5900* > > VNCing with the above gives me the blank black screen and a cursor (See > attached). I cant do anything on that screen. > OK, I can suggest to to power off the engine VM with hosted-engine --vm-poweroff and then start it again with hosted-engine --vm-start in order to follow the whole boot process over VNC > > > Please help > > > > On Mon, Feb 25, 2019 at 11:34 AM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >> >> >> On Mon, Feb 25, 2019 at 10:27 AM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: >> >>> Hi Simone, >>> >>> Thank you for your response. Executing the command below, gives this: >>> >>> [root@ovirt-host]# curl http://$(grep fqdn /etc/ovirt-hosted-engine/hosted-engine.conf >>> | cut -d= -f2)/ovirt-engine/services/health >>> curl: (7) Failed to connect to engine.sanren.ac.za:80; No route to host >>> >>> I tried to enable http traffic on the ovirt-host, but the error persists >>> >> >> Run, on your hosts, >> getent ahosts engine.sanren.ac.za >> >> and ensure that it got resolved as you wish. >> Fix name resolution and routing on your hosts in a coherent manner. >> >> > > -- > Regards, > Sakhi Hadebe > > Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR > > Tel: +27 12 841 2308 <+27128414213> > Fax: +27 12 841 4223 <+27128414223> > Cell: +27 71 331 9622 <+27823034657> > Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> > >

1 0

[oVirt 4.3.1 Test Day] cmdline HE Deployment
by Guillaume Pavese 25 Feb '19

25 Feb '19

He deployment with "hosted-engine --deploy" fails at TASK [ovirt.hosted_engine_setup : Get local VM IP] See following Error : 2019-02-25 12:46:50,154+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Get local VM IP] 2019-02-25 12:55:26,823+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {u'_ansible_parsed': True, u'stderr_lines': [], u'cmd': u"virsh -r net-dhcp-leases default | grep -i 00 :16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", u'end': u'2019-02-25 12:55:26.666925', u'_ansible_no_log': False, u'stdout': u'', u'changed': True, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u"virsh -r net-dhcp-leases default | grep -i 00:16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'std in': None}}, u'start': u'2019-02-25 12:55:26.584686', u'attempts': 50, u'stderr': u'', u'rc': 0, u'delta': u'0:00:00.082239', u'stdout_lines': []} 2019-02-25 12:55:26,924+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.082239", "end": "2019-02-25 12:55:26.666925", "rc": 0, "start": "2019-02-25 12:55:26.584686", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

3 5

Gluster - performance.strict-o-direct and other performance tuning in different storage backends
by Leo David 25 Feb '19

25 Feb '19

Hello Everyone, As per some previous posts, this "performance.strict-o-direct=on" setting caused trouble or poor vm iops. I've noticed that this option is still part of default setup or automatically configured with "Optimize for virt. store" button. In the end... is this setting a good or a bad practice for setting the vm storage volume ? Does it depends ( like maybe other gluster performance options ) on the storage backend: - raid type / jbod - raid controller cache size I am usually using jbod disks attached to lsi hba card ( no cache ). Any gluster recommendations regarding this setup ? Is there any documentation for best practices on configurating ovirt's gluster for different types of storage backends ? Thank you very much ! Have a great week, Leo -- Best regards, Leo David

2 2

Problem deploying self-hosted engine on ovirt 4.3.0
by matteo fedeli 25 Feb '19

25 Feb '19

after several attempts I managed to install and deploying the ovel gluster but during the self-hosted engine deploy stuck on [INFO] TASK ["oVirt.engine-setup: Install oVirt Engine package"] for 30 minutes ... How to safely interrupt ? I let it go on while I look at some logs?

2 4

[oVirt 4.3.1 Test Day] Cockpit HE Deployment
by Guillaume Pavese 25 Feb '19

25 Feb '19

As indicated on Trello, HE deployment though cockpit is stuck at the beginning with "Please correct errors before moving to next step", but no Error is explicitly shown or highlighted. Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Unable to change cluster and data center compatibility version
by Jonathan Mathews 25 Feb '19

25 Feb '19

Good Day I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run into an issue where I am unable to change the cluster and data center compatibility version. I get the following error in the GUI: Ovirt: Some of the hosts still use legacy protocol which is not supported by cluster 3.6 or higher. In order to change it a host needs to be put to maintenance and edited in advanced options section. This error was received with all VM's off and all hosts in maintenance. The environment has the following currently installed: Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5 Host1 - CentOS 6.9 - VDSM 4.16.30 Host2 - CentOS 6.9 - VDSM 4.16.30 Host3 - CentOS 6.9 - VDSM 4.16.30 I also have the following from engine.log [root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log 2018-09-22 07:11:33,920 INFO [org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher] (DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS 'd82a026c-31b4-4efc-8567-c4a6bdcaa826' 2018-09-22 07:11:34,685 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH, DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9 2018-09-22 07:11:34,687 INFO [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command: DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2018-09-22 07:11:34,706 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START, DisconnectStorageServerVDSCommand(HostName = ovhost3, StorageServerConnectionManagementVDSParameters:{runAsync='true', hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826', storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS', connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e', connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606', connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117', connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2', connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null', vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6 2018-09-22 07:11:34,991 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH, DisconnectStorageServerVDSCommand, return: {3fdffb4c-250b-4a4e-b914-e0da1243550e=0, 29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0, 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0, 4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6 2018-09-22 07:11:56,367 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-29) [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:12:41,017 WARN [org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default task-29) [efd285b] CanDoAction of action 'UpdateStoragePool' failed for user admin@internal. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS 2018-09-22 07:13:15,717 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-6) [4c9f3ee8] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:15:21,460 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-28) [649bae65] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:18:44,633 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-8) [23167cfd] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:24:20,372 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-15) [5d2ce633] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION I would appreciate some advice in resolving this. Thanks

3 5

Problem with snapshots in illegal status
by Bruno Rodriguez 25 Feb '19

25 Feb '19

Hello, We are experiencing some problems with some snapshots in illegal status generated with the python API. I think I'm not the only one, and that is not a relief but I hope someone can help about it. I'm a bit scared because, for what I see, the creation date in the engine for every snapshot is way different from the date when it was really created. The name of the snapshot is in the format backup_snapshot_YYYYMMDD-HHMMSS, but as you can see in the following examples, the stored date is totally random... Size Creation Date Snapshot Description Status Disk Snapshot ID 33 GiB Mar 2, 2018, 5:03:57 PM backup_snapshot_20190217-011645 Illegal 5734df23-de67-41a8-88a1-423cecfe7260 33 GiB May 8, 2018, 10:02:56 AM backup_snapshot_20190216-013047 Illegal f649d9c1-563e-49d4-9fad-6bc94abc279b 10 GiB Feb 21, 2018, 11:10:17 AM backup_snapshot_20190217-010004 Illegal 2929df28-eae8-4f27-afee-a984fe0b07e7 43 GiB Feb 2, 2018, 12:55:51 PM backup_snapshot_20190216-015544 Illegal 4bd4360e-e0f4-4629-ab38-2f0d80d3ae0f 11 GiB Feb 13, 2018, 12:51:08 PM backup_snapshot_20190217-010541 Illegal fbaff53b-30ce-4b20-8f10-80e70becb48c 11 GiB Feb 13, 2018, 4:05:39 PM backup_snapshot_20190217-011207 Illegal c628386a-da6c-4a0d-ae7d-3e6ecda27d6d 11 GiB Feb 13, 2018, 4:38:25 PM backup_snapshot_20190216-012058 Illegal e9ddaa5c-007d-49e6-8384-efefebb00aa6 11 GiB Feb 13, 2018, 10:52:09 AM backup_snapshot_20190216-012550 Illegal 5b6db52a-bfe3-45f8-b7bb-d878c4e63cb4 55 GiB Jan 22, 2018, 5:02:29 PM backup_snapshot_20190217-012659 Illegal 7efe2e7e-ca24-4b27-b512-b42795c79ea4 When I'm getting the logs for the first one, to check what happened to it, I get the following 2019-02-17 01:16:45,839+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-100) [96944daa-c90a-4ad7-a556-c98e66550f87] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', ignoreFailoverLimit='false', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageSizeInBytes='32212254720', volumeFormat='COW', newImageId='fa154782-0dbb-45b5-ba62-d6937259f097', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='5734df23-de67-41a8-88a1-423cecfe7260', sourceImageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f'}), log id: 497c168a 2019-02-17 01:18:26,506+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] START, GetVolumeInfoVDSCommand(HostName = hood13.pic.es, GetVolumeInfoVDSCommandParameters:{hostId='0a774472-5737-4ea2-b49a-6f0ea4572199', storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageId='5734df23-de67-41a8-88a1-423cecfe7260'}), log id: 111a34cf 2019-02-17 01:18:26,764+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Successfully added Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') for image transfer command '11104d8c-2a9b-4924-96ce-42ef66725616' 2019-02-17 01:18:27,310+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] START, AddImageTicketVDSCommand(HostName = hood11.pic.es, AddImageTicketVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e', ticketId='0d389c3e-5ea5-4886-8ea7-60a1560e3b2d', timeout='300', operations='[read]', size='35433480192', url='file:///rhev/data-center/mnt/blockSD/e655abce-c5e8-44f3-8d50-9fd76edf05cb/images/c5cc464e-eb71-4edf-a780-60180c592a6f/5734df23-de67-41a8-88a1-423cecfe7260', filename='null'}), log id: f5de141 2019-02-17 01:22:28,898+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Renewing transfer ticket for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:26:33,588+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Renewing transfer ticket for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:26:49,319+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Finalizing successful transfer for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:27:17,771+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hood11.pic.es command TeardownImageVDS failed: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/5734df23-de67-41a8-88a1-423cecfe7260 in use.\', \' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/fa154782-0dbb-45b5-ba62-d6937259f097 in use.\']\\ne655abce-c5e8-44f3-8d50-9fd76edf05cb/[\'5734df23-de67-41a8-88a1-423cecfe7260\', \'fa154782-0dbb-45b5-ba62-d6937259f097\']",)',) 2019-02-17 01:27:17,772+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Command 'TeardownImageVDSCommand(HostName = hood11.pic.es, ImageActionsVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e'})' execution failed: VDSGenericException: VDSErrorException: Failed in vdscommand to TeardownImageVDS, error = Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/5734df23-de67-41a8-88a1-423cecfe7260 in use.\', \' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/fa154782-0dbb-45b5-ba62-d6937259f097 in use.\']\\ne655abce-c5e8-44f3-8d50-9fd76edf05cb/[\'5734df23-de67-41a8-88a1-423cecfe7260\', \'fa154782-0dbb-45b5-ba62-d6937259f097\']",)',) 2019-02-17 01:27:19,204+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-6) [e73bfbec-d6bd-40e5-8009-97e6005ad1d4] START, MergeVDSCommand(HostName = hood11.pic.es, MergeVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e', vmId='addd5eba-9078-41aa-9244-fe485aded951', storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageId='fa154782-0dbb-45b5-ba62-d6937259f097', baseImageId='5734df23-de67-41a8-88a1-423cecfe7260', topImageId='fa154782-0dbb-45b5-ba62-d6937259f097', bandwidth='0'}), log id: 1d956d48 2019-02-17 01:27:29,923+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-49) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Transfer was successful. Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:27:30,997+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-46) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Successfully transferred disk '5734df23-de67-41a8-88a1-423cecfe7260' (command id '11104d8c-2a9b-4924-96ce-42ef66725616') For what I understand, there was a "Cannot deactivate logical volume" problem that I would thank very much if someone can help me about how to solve Thanks again -- Bruno Rodríguez Rodríguez "Si algo me ha enseñado el tetris, es que los errores se acumulan y los triunfos desaparecen"

2 5

VM creation using python api specifying an appropriate timezone
by ckennedy288＠gmail.com 25 Feb '19

25 Feb '19

Hi, I'm looking for a way to accurately specify the timezone of a VM at VM creation time. At the moment all VMs that get created using a simple in-house python script are set with a GMT timezone e.g.: if ( "windows" in OS ): vm_tz="GMT Standard Time" else: vm_tz="Etc/GMT" Is there a better way to choose a more appropriate timezone based on the VMs global location? is there a way to get a list of ovirt supported time zones for Windows and Linux and compare that with the VMs location and OS type and then choose an appropriate timezone?

1 0

Info about AD integration and Root CA
by Gianluca Cecchi 25 Feb '19

25 Feb '19

Hello, in docs for 4.2 RHV (I think it applies to oVirt 4.2 too) for attaching to AD there is the statement " To set up secure connection between the LDAP server and the Manager, ensure a PEM- encoded CA certificate has been prepared. See Section D.2, “Setting Up Encrypted Communication between the Manager and an LDAP Server” for more information. " and in Appendix " To set up encrypted communication between the Red Hat Virtualization Manager and an LDAP server, obtain the root CA certificate of the LDAP server. . . " and in readme file referred in the Appendix (/usr/share/doc/ovirt-engine-extension-aaa-ldap-1.3.8/README) there is the command: " Active Directory Windows: > certutil -ca.cert myrootca.der Linux: $ openssl -in myrootca.der -inform DER -out myrootca.pem " In my case on Windows DC (that is a Windows 2012 R2 server with "Domain functional level: Windows Server 2003") I get this error: C:\Users\Administrator.MYDOMAIN>certutil -ca.cert mydomain.der CertUtil: The system cannot find the file specified. C:\Users\Administrator.MYDOMAIN> What does it mean exactly? Thanks in advance, Gianluca

2 2

HostedEngine Unreachable
by Sakhi Hadebe 25 Feb '19

25 Feb '19

Hi, Our cluster was running fine, until we moved it to the new network. Looking at the agent.log file, it stills pings the old gateway. Not sure if this is the reason it's failing the liveliness check. Please help. On Thu, Feb 21, 2019 at 4:39 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi, > > I need some help. We had a working ovirt cluster in the testing > environment. We have just moved it to the production environment with the > same network settings. The only thing we changed is the public VLAN. In > production we're using a different subnet. > > The problem is we can't get the HostedEngine Up. It does come up but it > fails the LIVELINESS CHECK and its health status is bad. We can't ping even > ping it. It is on the same subnet as host machines: 192.168.x.x/24: > > *HostedEngine VM status:* > > [root@garlic qemu]# hosted-engine --vm-status > > > --== Host 1 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : goku.sanren.ac.za > Host ID : 1 > Engine status : {"reason": "vm not running on this > host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 57b2ece9 > local_conf_timestamp : 8463 > Host timestamp : 8463 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=8463 (Thu Feb 21 16:32:29 2019) > host-id=1 > score=3400 > vm_conf_refresh_time=8463 (Thu Feb 21 16:32:29 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > > > --== Host 2 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : garlic.sanren.ac.za > Host ID : 2 > Engine status : {"reason": "failed liveliness check", > "health": "bad", "vm": "up", "detail": "Powering down"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 71dc3daf > local_conf_timestamp : 8540 > Host timestamp : 8540 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=8540 (Thu Feb 21 16:32:31 2019) > host-id=2 > score=3400 > vm_conf_refresh_time=8540 (Thu Feb 21 16:32:31 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineStop > stopped=False > timeout=Thu Jan 1 04:24:29 1970 > > > --== Host 3 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : gohan.sanren.ac.za > Host ID : 3 > Engine status : {"reason": "vm not running on this > host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 49645620 > local_conf_timestamp : 5480 > Host timestamp : 5480 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=5480 (Thu Feb 21 16:32:22 2019) > host-id=3 > score=3400 > vm_conf_refresh_time=5480 (Thu Feb 21 16:32:22 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > You have new mail in /var/spool/mail/root > > The service are running but with errors: > *vdsmd.service:* > [root@garlic qemu]# systemctl status vdsmd > ● vdsmd.service - Virtual Desktop Server Manager > Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor > preset: enabled) > Active: active (running) since Thu 2019-02-21 16:12:12 SAST; 3min 31s > ago > Process: 40117 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh > --post-stop (code=exited, status=0/SUCCESS) > Process: 40121 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh > --pre-start (code=exited, status=0/SUCCESS) > Main PID: 40224 (vdsmd) > Tasks: 47 > CGroup: /system.slice/vdsmd.service > ├─40224 /usr/bin/python2 /usr/share/vdsm/vdsmd > └─40346 /usr/libexec/ioprocess --read-pipe-fd 65 > --write-pipe-fd 64 --max-threads 10 --max-queued-requests 10 > > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running nwfilter > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: libvirt: > Network Filter Driver error : Requested operation is not valid: nwfilter is > in use > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running dummybr > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running tune_system > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running test_space > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running test_lo > Feb 21 16:12:12 garlic.sanren.ac.za systemd[1]: Started Virtual Desktop > Server Manager. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN MOM not available. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN MOM not available, > KSM stats will be missing. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN Not ready yet, > ignoring event '|virt|VM_status|e2608f14-39fe-4ab6-b6be-9c60679e8c76' > args={'e2608f14-39fe-4ab6-b6be-9c606..., 'type': ' > Hint: Some lines were ellipsized, use -l to show in full. > > *libvirtd.service:* > [root@garlic qemu]# systemctl status libvirtd > ● libvirtd.service - Virtualization daemon > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; > vendor preset: enabled) > Drop-In: /etc/systemd/system/libvirtd.service.d > └─unlimited-core.conf > Active: active (running) since Thu 2019-02-21 16:06:50 SAST; 9min ago > Docs: man:libvirtd(8) > https://libvirt.org > Main PID: 38485 (libvirtd) > Tasks: 17 (limit: 32768) > CGroup: /system.slice/libvirtd.service > └─38485 /usr/sbin/libvirtd --listen > > Feb 21 16:06:50 garlic.sanren.ac.za systemd[1]: Starting Virtualization > daemon... > Feb 21 16:06:50 garlic.sanren.ac.za systemd[1]: Started Virtualization > daemon. > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: info : libvirt version: 3.9.0, package: > 14.el7_5.8 (CentOS BuildSystem <http://bugs.c...centos.org) > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: info : hostname: garlic.sanren.ac.za > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: error : virNetSocketReadWire:1808 : End of file > while reading data: Input/output error > Feb 21 16:12:08 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:12:08.791+0000: 38485: error : virNetSocketReadWire:1808 : End of file > while reading data: Input/output error > Hint: Some lines were ellipsized, use -l to show in full. > > *ovirt-ha-broker & ovirt-ha-agent services:* > [root@garlic qemu]# systemctl restart ovirt-ha-broker > ^[[A[root@garlic qemu]# systemctl status ovirt-ha-broker > ● ovirt-ha-broker.service - oVirt Hosted Engine High Availability > Communications Broker > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; > enabled; vendor preset: disabled) > Active: active (running) since Thu 2019-02-21 16:18:43 SAST; 30s ago > Main PID: 41493 (ovirt-ha-broker) > Tasks: 13 > CGroup: /system.slice/ovirt-ha-broker.service > ├─41493 /usr/bin/python > /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker > ├─41688 /bin/sh /usr/sbin/hosted-engine --check-liveliness > └─41689 python -m ovirt_hosted_engine_setup.check_liveliness > > Feb 21 16:18:43 garlic.sanren.ac.za systemd[1]: Started oVirt Hosted > Engine High Availability Communications Broker. > Feb 21 16:18:43 garlic.sanren.ac.za systemd[1]: Starting oVirt Hosted > Engine High Availability Communications Broker... > [root@garlic qemu]# systemctl status ovirt-ha-agent > ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability > Monitoring Agent > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; > enabled; vendor preset: disabled) > Active: active (running) since Thu 2019-02-21 16:18:53 SAST; 25s ago > Main PID: 41581 (ovirt-ha-agent) > Tasks: 2 > CGroup: /system.slice/ovirt-ha-agent.service > └─41581 /usr/bin/python > /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent > > Feb 21 16:18:53 garlic.sanren.ac.za systemd[1]: Started oVirt Hosted > Engine High Availability Monitoring Agent. > Feb 21 16:18:53 garlic.sanren.ac.za systemd[1]: Starting oVirt Hosted > Engine High Availability Monitoring Agent... > > Attached are logs of files that might contain some useful information to > troubleshoot. > > > Your assistance will be highly appreciated > > -- > Regards, > Sakhi Hadebe > > Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR > > Tel: +27 12 841 2308 <+27128414213> > Fax: +27 12 841 4223 <+27128414223> > Cell: +27 71 331 9622 <+27823034657> > Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> > > -- Regards, Sakhi Hadebe Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR Tel: +27 12 841 2308 <+27128414213> Fax: +27 12 841 4223 <+27128414223> Cell: +27 71 331 9622 <+27823034657> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za>

2 3

Move infrastructure ,how to change FQDN
by Fabrice SOLER 25 Feb '19

25 Feb '19

Hello, I need to move all the physical infrastructure oVirt to another site (for student education). The node's FQDN and the hosted engine's FQDN must change. The version is ovirt 4.2.8 for the hosted engine and nodes. Is there sommone who know how to do ? Fabrice SOLER

2 1

Ovirt 4.2.8.. Possible bug?
by matteo fedeli 25 Feb '19

25 Feb '19

Hi considering that the deploy with 4.2.7.8 failed I try to reinstall ovirt to version 4.2.8 and there are appened two strange things. During the volume step if i choose jbod mode in the deploy conf remain raid6 type... Why? To solve I have only tried to editing manually the file at line about volume type and the deploy stuck on creating physical volume... this is my conf file: (I used 3 HDDs 500GB each, node,engine + vmstore and data) #gdeploy configuration generated by cockpit-gluster plugin [hosts] kansas.planet.bn germany.planet.bn singapore.planet.bn [script1:kansas.planet.bn] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h kansas.planet.bn, germany.planet.bn, singapore.planet.bn [script1:germany.planet.bn] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h kansas.planet.bn, germany.planet.bn, singapore.planet.bn [script1:singapore.planet.bn] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h kansas.planet.bn, germany.planet.bn, singapore.planet.bn [disktype] jbod [diskcount] 12 [stripesize] 256 [service1] action=enable service=chronyd [service2] action=restart service=chronyd [shell2] action=execute command=vdsm-tool configure --force [script3] action=execute file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh ignore_script_errors=no [pv1:kansas.planet.bn] action=create devices=sdb ignore_pv_errors=no [pv1:germany.planet.bn] action=create devices=sdb ignore_pv_errors=no [pv1:singapore.planet.bn] action=create devices=sdb ignore_pv_errors=no [vg1:kansas.planet.bn] action=create vgname=gluster_vg_sdb pvname=sdb ignore_vg_errors=no [vg1:germany.planet.bn] action=create vgname=gluster_vg_sdb pvname=sdb ignore_vg_errors=no [vg1:singapore.planet.bn] action=create vgname=gluster_vg_sdb pvname=sdb ignore_vg_errors=no [lv1:kansas.planet.bn] action=create poolname=gluster_thinpool_sdb ignore_lv_errors=no vgname=gluster_vg_sdb lvtype=thinpool size=1005GB poolmetadatasize=5GB [lv2:germany.planet.bn] action=create poolname=gluster_thinpool_sdb ignore_lv_errors=no vgname=gluster_vg_sdb lvtype=thinpool size=1005GB poolmetadatasize=5GB [lv3:singapore.planet.bn] action=create poolname=gluster_thinpool_sdb ignore_lv_errors=no vgname=gluster_vg_sdb lvtype=thinpool size=1005GB poolmetadatasize=5GB [lv4:kansas.planet.bn] action=create lvname=gluster_lv_engine ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/engine size=100GB lvtype=thick [lv5:kansas.planet.bn] action=create lvname=gluster_lv_data ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/data lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [lv6:kansas.planet.bn] action=create lvname=gluster_lv_vmstore ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/vmstore lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [lv7:germany.planet.bn] action=create lvname=gluster_lv_engine ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/engine size=100GB lvtype=thick [lv8:germany.planet.bn] action=create lvname=gluster_lv_data ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/data lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [lv9:germany.planet.bn] action=create lvname=gluster_lv_vmstore ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/vmstore lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [lv10:singapore.planet.bn] action=create lvname=gluster_lv_engine ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/engine size=100GB lvtype=thick [lv11:singapore.planet.bn] action=create lvname=gluster_lv_data ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/data lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [lv12:singapore.planet.bn] action=create lvname=gluster_lv_vmstore ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/vmstore lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=500GB [selinux] yes [service3] action=restart service=glusterd slice_setup=yes [firewalld] action=add ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,54322/tcp services=glusterfs [script2] action=execute file=/usr/share/gdeploy/scripts/disable-gluster-hooks.sh [shell3] action=execute command=usermod -a -G gluster qemu [volume1] action=create volname=engine transport=tcp replica=yes replica_count=3 key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable brick_dirs=kansas.planet.bn:/gluster_bricks/engine/engine,germany.planet.bn:/gluster_bricks/engine/engine,singapore.planet.bn:/gluster_bricks/engine/engine ignore_volume_errors=no [volume2] action=create volname=data transport=tcp replica=yes replica_count=3 key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable brick_dirs=kansas.planet.bn:/gluster_bricks/data/data,germany.planet.bn:/gluster_bricks/data/data,singapore.planet.bn:/gluster_bricks/data/data ignore_volume_errors=no [volume3] action=create volname=vmstore transport=tcp replica=yes replica_count=3 key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable brick_dirs=kansas.planet.bn:/gluster_bricks/vmstore/vmstore,germany.planet.bn:/gluster_bricks/vmstore/vmstore,singapore.planet.bn:/gluster_bricks/vmstore/vmstore ignore_volume_errors=no

3 4

Re: Ovirt Glusterfs
by Strahil 25 Feb '19

25 Feb '19

I have done some testing and it seems that storhaug + ctdb + nfs-ganesha is showing decent performance in a 3 node hyperconverged setup. Fuse mounts are hitting some kind of limit when mounting gluster -3.12.15 volumes. Best Regards, Strahil Nikolov

3 2

Creating new VM
by Yujin Boby 24 Feb '19

24 Feb '19

I installed oVirt, when i try to create a new VM, it says This host is managed by a virtualization manager, so creation of new VM from this host is not possible. https://imgur.com/a/hpqV6ML Any idea why i am getting this error ? Do i need more than 1 server to create Virtual machines ? Like adding a node ?

2 1

update to 4.2.8 fails
by Vincent Royer 24 Feb '19

24 Feb '19

trying to update from 4.2.6 to 4.2.8 yum update fails with: --> Finished Dependency Resolution Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2) Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3 Installed: libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64 (installed) libvirt-daemon-kvm = 3.9.0-14.el7_5.8 Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libepoxy.so.0()(64bit) Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libibumad.so.3()(64bit) Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libgbm.so.1()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Uploading Enabled Repositories Report 2019-02-13 16:42:14,190 [INFO] yum:17779:Dummy-18 @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False Loaded plugins: fastestmirror, product-id, subscription-manager 2019-02-13 16:42:14,199 [WARNING] yum:17779:Dummy-18 @logutil.py:141 - logging already initialized 2019-02-13 16:42:14,200 [ERROR] yum:17779:Dummy-18 @identity.py:145 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem' 2019-02-13 16:42:14,200 [INFO] yum:17779:Dummy-18 @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False 2019-02-13 16:42:14,201 [INFO] yum:17779:Dummy-18 @repolib.py:471 - repos updated: Repo updates Total repo updates: 0 Updated <NONE> Added (new) <NONE> Deleted <NONE> This system is not registered with an entitlement server. You can use subscription-manager to register. Cannot upload enabled repos report, is this client registered? [root@brian yum.repos.d]# yum repolist Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade 2019-02-13 16:42:36,489 [ERROR] yum:17809:MainThread @identity.py:145 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem' 2019-02-13 16:42:36,490 [INFO] yum:17809:MainThread @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False 2019-02-13 16:42:36,491 [INFO] yum:17809:MainThread @repolib.py:471 - repos updated: Repo updates Total repo updates: 0 Updated <NONE> Added (new) <NONE> Deleted <NONE> This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * ovirt-4.2: mirrors.rit.edu * ovirt-4.2-epel: mirror.sjc02.svwh.net repo id repo name status centos-sclo-rh-release/x86_64 CentOS-7 - SCLo rh 8,113 ovirt-4.2/7 Latest oVirt 4.2 Release 2,558 ovirt-4.2-centos-gluster312/x86_64 CentOS-7 - Gluster 3.12 262 ovirt-4.2-centos-opstools/x86_64 CentOS-7 - OpsTools - release 853 ovirt-4.2-centos-ovirt42/x86_64 CentOS-7 - oVirt 4.2 631 ovirt-4.2-centos-qemu-ev/x86_64 CentOS-7 - QEMU EV 71 ovirt-4.2-epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 *Help!*

6 11

How to recreate Ovirt CA from scratch
by Giorgio Biacchi 24 Feb '19

24 Feb '19

Hi list, during our datacenter lifetime many things changed. We moved the engine twice on different hosts with, of course, different FQDNs, and many other changes. Now we are stuck with an error when we try to upload an image to a data domain. The error is somehow bound to a failure to validate the ovirt-imageio-proxy certificate and, since the current root CA certificate is still signed with sha1WithRSAEncryption we'd like to regenerate the whole CA. That's the steps we've done.. without success... 1) Make a tar.gz of the /etc/pki/ovirt-engine as backup 2) Create a new CA cert using the same private key: openssl req -key /etc/pki/ovirt-engine/private/ca.pem -new -x509 -days 3650 -sha256 -extensions v3_ca -out newca.cert.pem 3) Put the new CA cert in place mv ca.pem ca.pem.orig.20190219;mv newca.cert.pem ca.pem 4) Resign all the other certs names="engine apache websocket-proxy jboss imageio-proxy" for name in $names; do subject="$( openssl \ x509 \ -in /etc/pki/ovirt-engine/certs/"${name}".cer \ -noout \ -subject \ | sed \ 's;subject= $.*$;\1;' \ )" /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \ --name="${name}" \ --password=mypass \ --subject="${subject}" \ --keep-key done 5) Restart all the services systemctl restart httpd systemctl restart ovirt-engine systemctl restart ovirt-websocket-proxy systemctl restart ovirt-imageio-proxy The following step was to take the backup at 1) and fall back to the initial state because nothing worked as expected. There's any documented procedure about how to recreate Ovirt CA from scratch?? Thanks in advance -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

2 3