- Users - oVirt List Archives

IPTables firewall to firewalld
by p.staniforth＠leedsbeckett.ac.uk 21 Aug '18

21 Aug '18

Hello, I get the following messages. "Cluster Default uses IPTables firewall, which has been deprecated in 4.2 of the engine, and will no longer be supported starting with version 4.3. Make sure to switch to Firewalld before upgrading to 4.3." If the correct way to change to firewalld edit cluster, and run reinstall? Thanks, Paul S.

2 1

Re: Upgrade 4.1 to 4.2 lsot gfapi Disk Access for VM's
by Alex K 20 Aug '18

20 Aug '18

Hi, On Mon, Aug 20, 2018 at 10:45 AM Ralf Schenk <rs(a)databay.de> wrote: > Hello, > > very interesting output. Feature Lost... > > [root@engine-mciii ~]# engine-config -g LibgfApiSupported > LibgfApiSupported: false version: 3.6 > LibgfApiSupported: false version: 4.0 > LibgfApiSupported: true version: 4.1 > LibgfApiSupported: false version: 4.2 > Did you enable it? did it fix your issue? > Bye > > Am 17.08.2018 um 17:57 schrieb Alex K: > > CORRECTION > > On Fri, Aug 17, 2018 at 6:55 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> Hi, >> >> On Fri, Aug 17, 2018 at 6:21 PM Ralf Schenk <rs(a)databay.de> wrote: >> >>> Hello, >>> >>> after upgradeing my whole cluster of 8 Hosts to ovirt 4.2.5 and setting >>> compability of cluster and datacenter to 4.2 my existing virtual machines >>> start using FUSE mounted disk-images on my gluster volumes. >>> >>> One bad and slow thing I thought that I got rid of starting with 4.1.x >>> finally ! >>> >>> Disk definition from virsh -r dumpxml VM of old running vm (not >>> restarted yet !): >>> >>> <disk type='network' device='disk' snapshot='no'> >>> <driver name='qemu' type='raw' cache='none' error_policy='stop' >>> io='threads'/> >>> <source protocol='gluster' >>> name='gv0/5d99af76-33b5-47d8-99da-1f32413c7bb0/images/d5f3657f-ac7a-4d89-8a83-e7c47ee0ef05/f99c6cb4-1791-4a55-a0b9-2ff0ec1a4dd7'> >>> <host name='glusterfs.mylocal.domain' port='24007'/> >>> </source> >>> <backingStore/> >>> <target dev='sda' bus='scsi'/> >>> <serial>d5f3657f-ac7a-4d89-8a83-e7c47ee0ef05</serial> >>> <boot order='1'/> >>> <alias name='scsi0-0-0-0'/> >>> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >>> </disk> >>> >>> Disk definition from virsh -r dumpxml VM of new started running vm: >>> >>> <disk type='file' device='disk' snapshot='no'> >>> <driver name='qemu' type='raw' cache='none' error_policy='stop' >>> io='threads'/> >>> <source file='/rhev/data-center/mnt/glusterSD/ >>> glusterfs.mylocal.domain >>> :_gv0/5d99af76-33b5-47d8-99da-1f32413c7bb0/images/1f0db0ef-a6af-4e3e-90e6-f681d071496b/1b3c3a >>> <backingStore/> >>> <target dev='sda' bus='scsi'/> >>> <serial>1f0db0ef-a6af-4e3e-90e6-f681d071496b</serial> >>> <boot order='1'/> >>> <alias name='ua-1f0db0ef-a6af-4e3e-90e6-f681d071496b'/> >>> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >>> </disk> >>> >>> >>> How do I get back my gfapi gluster-based Disks ? >>> >> Can you check at engine the gfapi support with: >> >> engine-config -g LibgfApiSupported >> >> >> If not enabled you can try: >> >> engine-config -s LibgfApiSupported=true >> >> >> >> Then restart ovirt-engine service, then shutdown/power up one VM to see. >> >> >>> >>> -- >>> >>> >>> *Ralf Schenk* >>> fon +49 (0) 24 05 / 40 83 70 >>> fax +49 (0) 24 05 / 40 83 759 >>> mail *rs(a)databay.de* <rs(a)databay.de> >>> >>> *Databay AG* >>> Jens-Otto-Krag-Straße 11 >>> D-52146 Würselen >>> *www.databay.de* <http://www.databay.de> >>> >>> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 >>> Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. >>> Philipp Hermanns >>> Aufsichtsratsvorsitzender: Wilhelm Dohmen >>> ------------------------------ >>> _______________________________________________ >>> 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/27UBFV326G5O4… >>> >> -- > > > *Ralf Schenk* > fon +49 (0) 24 05 / 40 83 70 > fax +49 (0) 24 05 / 40 83 759 > mail *rs(a)databay.de* <rs(a)databay.de> > > *Databay AG* > Jens-Otto-Krag-Straße 11 > D-52146 Würselen > *www.databay.de* <http://www.databay.de> > > Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 > Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. > Philipp Hermanns > Aufsichtsratsvorsitzender: Wilhelm Dohmen > ------------------------------ >

4 3

Failed to run check-update of host
by Jayme 20 Aug '18

20 Aug '18

I have a fairly recent three node HCI setup running 4.2.5. I've recently updated hosted engine to the latest version (including yum updates). When I check for host updates through the engine gui I get the following error for all three of my hosts: Failed to check for available updates on host XXXXX with message 'Failed to run check-update of host 'XXXXXX'.'. The engine.log shows not much more detail: 2018-08-20 14:26:28,396-03 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [4400c1d5-5412-4f1a-9c25-40fe0fb53295] Failed to run check-update of host 'XXXXX'. 2018-08-20 14:26:28,397-03 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [4400c1d5-5412-4f1a-9c25-40fe0fb53295] Failed to check if updates are available for host 'Orchard2' with error message 'Failed to run check-update of host 'XXXXX'.' 2018-08-20 14:26:28,411-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [4400c1d5-5412-4f1a-9c25-40fe0fb53295] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates on host Orchard2 with message 'Failed to run check-update of host 'XXXXX'.'. Yum seems to run ok manually on the server (although not showing any updates available). Here is node and yum info/output from one of my hosts: nodectl check; nodectl info; yum update Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK layers: ovirt-node-ng-4.2.5.1-0.20180806.0: ovirt-node-ng-4.2.5.1-0.20180806.0+1 bootloader: default: ovirt-node-ng-4.2.5.1-0.20180806.0+1 entries: ovirt-node-ng-4.2.5.1-0.20180806.0+1: index: 0 title: ovirt-node-ng-4.2.5.1-0.20180806.0 kernel: /boot/ovirt-node-ng-4.2.5.1-0.20180806.0+1/vmlinuz-3.10.0-862.9.1.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn_orchard0/swap rd.lvm.lv=onn_orchard0/ovirt-node-ng-4.2.5.1-0.20180806.0+1 rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.5.1-0.20180806.0+1" initrd: /boot/ovirt-node-ng-4.2.5.1-0.20180806.0+1/initramfs-3.10.0-862.9.1.el7.x86_64.img root: /dev/onn_orchard0/ovirt-node-ng-4.2.5.1-0.20180806.0+1 current_layer: ovirt-node-ng-4.2.5.1-0.20180806.0+1 Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade 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-epel: ewr.edge.kernel.org No packages marked for update Uploading Enabled Repositories Report Loaded plugins: fastestmirror, product-id, subscription-manager 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? Thanks!

1 1

after upgrade from 4.2.3 to 4.2.5, problems with consoles + cockpit
by Jason Keltz 20 Aug '18

20 Aug '18

Hi.. After an upgrade from 4.2.3 to 4.2.5 last week, I notice that I have a console + cockpit problem. Immediately following the upgrade, everything seemed to be working fine. However, today, a couple of days after the upgrade, when I try to view any CentOS VM console, virt-viewer starts, and I see "Connected to graphic server", but there's no console output. This happens on all Linux VMs, though on my two windows VMs, the console still works. If I restart a Linux VM, I get the console back again, but what made me lose access to all the consoles? In addition, if I right click on one of my 4 hosts, and choose "Host Console", it connects to cockpit which reports: "No VM is running or defined on this host" even though there are plenty. I brought one host into maintenance mode, and rebooted it. I then started a few VMs there, and cockpit still doesn't show anything running. All of the hosts have all available ovirt updates, and are running the latest CentOS 7 kernel + O/S updates. Any ideas? There is no issue with firewall. Jason.

1 1

Configuring Single Sign-On (SSO) for guests VMs
by Николаев Алексей 20 Aug '18

20 Aug '18

1 0

Hosted Engine Setup Issues on Ovirt Node 4.2.5.1
by Jeremy Tourville 20 Aug '18

20 Aug '18

If I try to setup hosted engine with the option to use Ansible it eventually fails on me. See https://lists.ovirt.org/archives/list/users@ovirt.org/thread/LPK7OGFALSQFAN… However if I run hosted-engine --deploy --noansible the setup does complete. There is further trouble though, it seems the networks are not being configured properly. If I browse to Compute>Hosts>Hostname and click on the Setup Host Networks button I am presented with a new window that contains an unassigned logical network of "oivrtmgmt" On the left side pane there are two columns for Interfaces and Assigned Logical Networks. Both of those columns are completely empty. I think if I understand correctly the interfaces column should at least have some info in it. [cid:2a4d1038-bdf0-4d1e-be64-e8a23c1c88d9] So my best guess is that for some unknown reason (at least to me) the Engine doesn't '"know how to get setup properly" either with or without Ansible. That's about as well as I can describe it. I hope it makes sense.... Anyone have ideas on what is going wrong here? Thanksfor any troubleshooting advice you can provide!

1 0

Upgrade 4.1 to 4.2 lsot gfapi Disk Access for VM's
by Ralf Schenk 17 Aug '18

17 Aug '18

Hello, after upgradeing my whole cluster of 8 Hosts to ovirt 4.2.5 and setting compability of cluster and datacenter to 4.2 my existing virtual machines start using FUSE mounted disk-images on my gluster volumes. One bad and slow thing I thought that I got rid of starting with 4.1.x finally ! Disk definition from virsh -r dumpxml VM of old running vm (not restarted yet !): <disk type='network' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source protocol='gluster' name='gv0/5d99af76-33b5-47d8-99da-1f32413c7bb0/images/d5f3657f-ac7a-4d89-8a83-e7c47ee0ef05/f99c6cb4-1791-4a55-a0b9-2ff0ec1a4dd7'> <host name='glusterfs.mylocal.domain' port='24007'/> </source> <backingStore/> <target dev='sda' bus='scsi'/> <serial>d5f3657f-ac7a-4d89-8a83-e7c47ee0ef05</serial> <boot order='1'/> <alias name='scsi0-0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> Disk definition from virsh -r dumpxml VM of new started running vm: <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/glusterSD/glusterfs.mylocal.domain:_gv0/5d99af76-33b5-47d8-99da-1f32413c7bb0/images/1f0db0ef-a6af-4e3e-90e6-f681d071496b/1b3c3a <backingStore/> <target dev='sda' bus='scsi'/> <serial>1f0db0ef-a6af-4e3e-90e6-f681d071496b</serial> <boot order='1'/> <alias name='ua-1f0db0ef-a6af-4e3e-90e6-f681d071496b'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> How do I get back my gfapi gluster-based Disks ? -- *Ralf Schenk* fon +49 (0) 24 05 / 40 83 70 fax +49 (0) 24 05 / 40 83 759 mail *rs(a)databay.de* <mailto:rs@databay.de> *Databay AG* Jens-Otto-Krag-Straße 11 D-52146 Würselen *www.databay.de* <http://www.databay.de> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Wilhelm Dohmen ------------------------------------------------------------------------

2 1

info about changing engine ip mode from dhcp to static
by Gianluca Cecchi 17 Aug '18

17 Aug '18

Hello, a colleague of mine installed oVirt engine 4.2.5 on a test CentOS 7.5 system and in its initial configuration he configured its ip via dhcp (using static ip assignment configured at dhcp server side). Now he would like to maintain the same ip/hostname for the engine but with a static configuration on the server. Any hint about how to achieve this? Thanks in advance, Gianluca

1 0

Network issues with oVirt 4.2 and cloud-init
by Berger, Sandy 17 Aug '18

17 Aug '18

--_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We're using cloud-init to customize VMs built from a template. We're using = static IPV4 settings so we're specifying an IP address, subnet mask, and ga= teway. There is apparently a bug in the current version of cloud-init shipp= ing as part of CentOS 7.4 (https://bugzilla.redhat.com/show_bug.cgi?id=3D14= 92726) that fails to set the gateway properly. In the description of the bu= g, it says it is fixed in RHEL 7.5 but also says one can use https://people= .redhat.com/rmccabe/cloud-init/cloud-init-0.7.9-20.el7.x86_64.rpm which is = what we're doing. When the new VM first boots, the 3 IPv4 settings are all set correctly. Reb= oots of the VM maintain the settings properly. But, if the VM is shut down = and started again via the oVirt GUI, all of the IPV4 settings on the eth0 v= irtual NIC are lost and the /etc/sysconfig/network-scripts/ifcfg-eth0 shows= that the NIC is now set up for DHCP. Are we doing something incorrectly? Sandy Berger IT - Infrastructure Engineer II Quad/Graphics Performance through Innovation Sussex, Wisconsin 414.566.2123 phone 414.566.4010/2123 pager/PIN sandy.berger(a)qg.com<mailto:sandy.berger@qg.com> www.QG.com<http://www.qg.com/> Follow Us: Facebook<http://www.qg.com/social1> | Twitter<http://www.qg.com/= social2> | LinkedIn<http://www.qg.com/social3> | YouTube<http://www.qg.com/= social4> --_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> We’re using cloud-init to customize VMs built = from a template. We’re using static IPV4 settings so we’re spec= ifying an IP address, subnet mask, and gateway. There is apparently a bug i= n the current version of cloud-init shipping as part of CentOS 7.4 (<a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D14= 92726">https://bugzilla.redhat.com/show_bug.cgi?id=3D1492726</a>) that fail= s to set the gateway properly. In the description of the bug, it says it is= fixed in RHEL 7.5 but also says one can use <a href=3D"https://people.redhat.com/rmccabe/cloud-init/cloud-init-0.7= .9-20.el7.x86_64.rpm"> https://people.redhat.com/rmccabe/cloud-init/cloud-init-0.7.9-20.el7.x86_64= .rpm</a> which is what we’re doing.<o:p></o:p> <o:p> </o:p> When the new VM first boots, the 3 IPv4 settings are= all set correctly. Reboots of the VM maintain the settings properly. But, = if the VM is shut down and started again via the oVirt GUI, all of the IPV4= settings on the eth0 virtual NIC are lost and the /etc/sysconfig/network-scripts/ifcfg-eth0 shows that the = NIC is now set up for DHCP.<o:p></o:p> <o:p> </o:p> Are we doing something incorrectly?<o:p></o:p> <o:p> </o:p> Sandy Berger <o:p></o:p> IT – Infrastructure Engineer I= I<o:p></o:p>  <o:p></o:p> Quad/Graphics<o:p><= /o:p> Performance&nb= sp;through Innovation<o:= p></o:p>  <o:p></o:p></= span> Sussex, Wisconsin<o= :p></o:p> 414.566.2123 phone<= o:p></o:p> 414.566.4010/2123 pager/PIN<span= style=3D"font-size:10.5pt;font-family:"Arial",sans-serif;color:#= 444444"><o:p></o:p>  <= /span><o:p></o:p> <a href=3D"mailto:sandy.berger@qg.com"><s= pan style=3D"color:blue">sandy.berger(a)qg.com</a><o:p></o:p> <a href=3D"http://www.qg.com/">www.QG.com</a><o:p></o:p></span= > <o:p> </o:p> </div> Follow Us: <a href=3D"http://www.qg.com/social1">Facebook</a> | <a href=3D"= http://www.qg.com/social2"> Twitter</a> | <a href=3D"http://www.qg.com/social3">LinkedIn</a> | <a href= =3D"http://www.qg.com/social4"> YouTube</a> </body> </html> --_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_--

4 5

Poor performance of oVirt Export Domain
by Aleksey.I.Maksimov＠yandex.ru 17 Aug '18

17 Aug '18

Hello I deployed a dedicated server (fs05.holding.com) on CentOS 7.5 and created a VDO volume on it. The local write test in the VDO volume on this server gives us an acceptable result # dd if=/dev/zero of=/mnt/vdo-vd1/nfs/testfile count=1000000 1000000+0 records in 1000000+0 records out 512000000 bytes (512 MB) copied, 6.26545 s, 81.7 MB/s The disk capacity of the VDO volume is connected to the oVirt 4.2.5 cluster as the Export Domain via NFS. I'm seeing a problem with the low performance of Export Domain. Snapshots of virtual machines are copied very slowly to the Export Domain, approximately 6-8 MB/s. At the same time, if I try to run a write test in an mounted NFS-directory on any of the oVit cluster hosts, I get about 50-70 MB/s. # dd if=/dev/zero of=/rhev/data-center/mnt/fs05.holding.com:_mnt_vdo-vd1_nfs_ovirt-vm-backup/testfile count=10000000 10000000+0 records in 10000000+0 records out 5120000000 bytes (5.1 GB) copied, 69.5506 s, 73.6 MB/s Help me understand the reason for the slow copying to Export Domain on oVirt.

3 2

oVirt 4.2.5 : VM snapshot creation does not work : command HSMGetAllTasksStatusesVDS failed: Could not acquire resource
by Aleksey Maksimov 17 Aug '18

17 Aug '18

Hello We use oVirt 4.2.5.2-1.el7 (Hosted engine / 4 hosts in cluster / about twenty virtual machines) Virtual machine disks are located on the Data Domain from FC SAN. Snapshots of all virtual machines are created normally. But for one virtual machine, we can not create a snapshot. When we try to create a snapshot in the oVirt web console, we see such errors: Aug 13, 2018, 1:05:06 PM Failed to complete snapshot 'KOM-APP14_BACKUP01' creation for VM 'KOM-APP14'. Aug 13, 2018, 1:05:01 PM VDSM KOM-VM14 command HSMGetAllTasksStatusesVDS failed: Could not acquire resource. Probably resource factory threw an exception.: () Aug 13, 2018, 1:05:00 PM Snapshot 'KOM-APP14_BACKUP01' creation for VM 'KOM-APP14' was initiated by petya@sub.holding.com@sub.holding.com-authz. At this time on the server with the role of "SPM" in the vdsm.log we see this: ... 2018-08-13 05:05:06,471-0500 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.getStats succeeded in 0.00 seconds (__init__:573) 2018-08-13 05:05:06,478-0500 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Image.deleteVolumes succeeded in 0.05 seconds (__init__:573) 2018-08-13 05:05:06,478-0500 INFO (tasks/3) [storage.ThreadPool.WorkerThread] START task bb45ae7e-77e9-4fec-9ee2-8e1f0ad3d589 (cmd=<bound method Task.commit of <vdsm.storage.task.Task instance at 0x7f06b85a2128>>, args=None) (threadPool:208) 2018-08-13 05:05:07,009-0500 WARN (tasks/3) [storage.ResourceManager] Resource factory failed to create resource '01_img_6db73566-0f7f-4438-a9ef-6815075f45ea.cdf1751b-64d3-42bc-b9ef-b0174c7ea068'. Canceling request. (resourceManager:543) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py", line 539, in registerResource obj = namespaceObj.factory.createResource(name, lockType) File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceFactories.py", line 193, in createResource lockType) File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceFactories.py", line 122, in __getResourceCandidatesList imgUUID=resourceName) File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 213, in getChain if srcVol.isLeaf(): File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 1430, in isLeaf return self._manifest.isLeaf() File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 139, in isLeaf return self.getVolType() == sc.type2name(sc.LEAF_VOL) File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 135, in getVolType self.voltype = self.getMetaParam(sc.VOLTYPE) File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 119, in getMetaParam meta = self.getMetadata() File "/usr/lib/python2.7/site-packages/vdsm/storage/blockVolume.py", line 112, in getMetadata md = VolumeMetadata.from_lines(lines) File "/usr/lib/python2.7/site-packages/vdsm/storage/volumemetadata.py", line 103, in from_lines "Missing metadata key: %s: found: %s" % (e, md)) MetaDataKeyNotFoundError: Meta Data key not found error: ("Missing metadata key: 'DOMAIN': found: {'NONE': '######################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################'}",) 2018-08-13 05:05:07,010-0500 WARN (tasks/3) [storage.ResourceManager.Request] (ResName='01_img_6db73566-0f7f-4438-a9ef-6815075f45ea.cdf1751b-64d3-42bc-b9ef-b0174c7ea068', ReqID='3d924e5e-60d1-47b0-86a7-c63585b56f09') Tried to cancel a processed request (resourceManager:187) 2018-08-13 05:05:07,010-0500 ERROR (tasks/3) [storage.TaskManager.Task] (Task='bb45ae7e-77e9-4fec-9ee2-8e1f0ad3d589') 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 "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1966, in deleteVolume with rm.acquireResource(img_ns, imgUUID, rm.EXCLUSIVE): File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py", line 1025, in acquireResource return _manager.acquireResource(namespace, name, lockType, timeout=timeout) File "/usr/lib/python2.7/site-packages/vdsm/storage/resourceManager.py", line 475, in acquireResource raise se.ResourceAcqusitionFailed() ResourceAcqusitionFailed: Could not acquire resource. Probably resource factory threw an exception.: () 2018-08-13 05:05:07,059-0500 INFO (tasks/3) [storage.ThreadPool.WorkerThread] FINISH task bb45ae7e-77e9-4fec-9ee2-8e1f0ad3d589 (threadPool:210) 2018-08-13 05:05:07,246-0500 INFO (jsonrpc/1) [root] /usr/libexec/vdsm/hooks/after_get_caps/50_openstacknet: rc=0 err= (hooks:110) 2018-08-13 05:05:07,660-0500 INFO (jsonrpc/1) [root] /usr/libexec/vdsm/hooks/after_get_caps/openstacknet_utils.py: rc=0 err= (hooks:110) 2018-08-13 05:05:08,152-0500 INFO (jsonrpc/1) [root] /usr/libexec/vdsm/hooks/after_get_caps/ovirt_provider_ovn_hook: rc=0 err= (hooks:110) Please help us to solve this problem.

3 8

Clarifications regarding ovirt-provider-ovn network
by Anurag Porripireddi 17 Aug '18

17 Aug '18

Hi, I had some questions a overt-provider-ovn based external network which is built on top of an physical network. I notice that VLAN tagging gets greyed out when I try to create an external provider network. Is it not supported by overt right now?I am on version 4.2.5.3. Also, if I create NICs with the external provider network built atop a physical network on VMs that are on different hosts, but the same cluster, I see they are unable to ping each other, though it seems to work fine if they are on the same host. Is that elected behaviour? Could you you please help me understand why? Thanks, Anurag

3 3

[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to resolve address\n"}
by Ariez Ahito 17 Aug '18

17 Aug '18

failed hosted-engine deployment i tried using command line but encountered this error i also tried downloading ovirt-node iso and using WEBUI but encountered same problem i deployed this hosted-engine 3.5 without any problems. any thoughts?

3 5

Hosted Engine Deployment Fails - Ansible Playbook
by jeremy_tourville＠hotmail.com 17 Aug '18

17 Aug '18

Can someone help me troubleshoot what my issue is? I have tried to setup hosted engine using static and DHCP addresses and both times it fails. Many thanks in advance! [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [root@vmh /]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp96s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP group default qlen 1000 link/ether 0c:c4:7a:f9:b9:88 brd ff:ff:ff:ff:ff:ff 3: enp96s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 0c:c4:7a:f9:b9:89 brd ff:ff:ff:ff:ff:ff 20: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 0c:c4:7a:f9:b9:88 brd ff:ff:ff:ff:ff:ff inet 172.30.50.2/24 brd 172.30.50.255 scope global dynamic ovirtmgmt valid_lft 84266sec preferred_lft 84266sec inet6 fe80::ec4:7aff:fef9:b988/64 scope link valid_lft forever preferred_lft forever 21: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:e2:1c:89 brd ff:ff:ff:ff:ff:ff inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0 valid_lft forever preferred_lft forever 22: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e2:1c:89 brd ff:ff:ff:ff:ff:ff 23: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:52:19:f4 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe52:19f4/64 scope link valid_lft forever preferred_lft forever 24: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 82:43:87:7f:eb:62 brd ff:ff:ff:ff:ff:ff [root@vmh /]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/onn_vmh-ovirt--node--ng--4.2.5.1--0.20180731.0+1 145G 3.1G 134G 3% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 4.0K 63G 1% /dev/shm tmpfs 63G 19M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/mapper/onn_vmh-var 15G 4.5G 9.4G 33% /var /dev/mapper/onn_vmh-tmp 976M 4.1M 905M 1% /tmp /dev/mapper/onn_vmh-home 976M 2.6M 907M 1% /home /dev/mapper/PNY_CS900_240GB_SSD_PNY14182241350103ED2p1 976M 365M 545M 41% /boot /dev/mapper/onn_vmh-var_log 7.8G 70M 7.3G 1% /var/log /dev/mapper/onn_vmh-var_log_audit 2.0G 9.2M 1.8G 1% /var/log/audit /dev/mapper/3600605b00a2faca222fb4da81ac9bdb1p1 7.4T 93M 7.1T 1% /srv tmpfs 13G 0 13G 0% /run/user/0 I have pasted my log file- https://pastebin.com/dyYksxaC

1 0

ovirt-ansible download/upload of snapshots for backup
by Николаев Алексей 16 Aug '18

16 Aug '18

2 2

Issue with NFS and Storage domain setup
by Inquirer Guy 16 Aug '18

16 Aug '18

Hi Ovirt, I successfully installed both ovirt-engine(ENGINE01) and ovirt node(NODE01) on a separate machines. I also created a FreeNAS(NAS01) with NFS share and already connected to my NODE01, all of these server though I haven't setup a DNS server, was manually added hostname on every machines and I can lookup and ping on them without a problem, I was able to add the NODE01 to my ENGINE01 as well. My issue was when I tried creating a storage domain on my ENGINE01, I did the below steps before running the engine-setup while also following the guide on the ovirt url: https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-… #touch /etc/exports #systemctl start rpcbind nfs-server #systemctl enable rpcbind nfs-server #engine-setup #mkdir /var/lib/exports/data #chown vdsm:kvm /var/lib/exports/data I added the 2 just in case but I have tried each alone but all fails #vi /etc/exports /var/lib/exports/data *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36) /var/lib/exports/data 0.0.0.0/0.0.0.0(rw) #systemctl restart rpc-statd nfs-server Once I started to add my storage domain I get the below error Attached is the engine log for your reference. Hope you guys can help me with these, Im really interested with this great product. Thanks!

3 3

Snapshots - Preview button greyed out
by Leo David 16 Aug '18

16 Aug '18

Hi Everyone, I am encountering an issue on my oVirt 4.2 self-hosted engine installation. Suddenly the "Preview" button in snapshots menu became inactive, I just cannot revert any previews snapshots. This feature worked fine over the last month, but now it seems to be just inactive. Any thoughts on this ? Thank you very much ! Leo -- Best regards, Leo David

3 3

Patches for L1FT?
by Eduardo Mayoral 16 Aug '18

16 Aug '18

Hi, For mitigation of the recently announced L1TF vulnerability, is it sufficient to update the compute nodes to the updated kernel? Are any other updates to KVM / vdsm / ovirt-engine required? Also, for the concurrent variant. Should we disable hyperthreading altogether? Is there any remediation (even if expensive from a performance view), that can be enabled? Thanks for your help! -- Eduardo Mayoral.

2 2

Do I need to set VM vnic profile for GlusterFS network?
by Jayme 16 Aug '18

16 Aug '18

I followed this guide to get my three node HCI cluster up and running: https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-gluste… The docs were a bit out of date but most things matched up. I have configured an internal GlusterFS network on a separate subnet on 10Gbe switch and have set it as the glusterFS and migration network. Is this all that is needed to be done for all glusterFS traffic to pass through that network or must the glusterFS vnic profile also be selected for each VM? I'm not sure if my VMs should be using ovirtmgmnt vnic or GlusterFS vnic.

2 1

storage domain sync problem and fail to run vm after change LUN mapping
by dvotrak 16 Aug '18

16 Aug '18

Environment: Ovirt version: 4.2.5 Centos 7.5 During a planned maintenance window, multipath configuration was changed according to the storage vendor guidelines. The new configuration modify user_friendly_names from no to yes, so the multipath -ll output changed from this "360060160a6213400fa2d31acbbfce511 dm-8 DGC" to this: "mpathh (360060160a6213400fa2d31acbbfce511) dm-8 DGC". After this change, the following errors are displayed: 1) when attempting to start a VM with direct LUN: Failed to run VM <VMNAME> on Host <HYPERVISOR> VM <VMNAME> is down. Exit message: Bad volume specification <LUN_ID> Inspecting the VM disk, the lun id remains the previous one (360060160a6213400fa2d31acbbfce511) insted of the new one (mpathh) Remove/detach and re-add/re-attach the disk to VM doesen't help. 2) randomly: Storage domains with IDs [<ID>] could not be synchronized. To synchronize them, please move them to maintenance and then activate. Moving it to maintenance and then activate it doesen't help. Inspecting storage domain luns, almost all change the lun id to the new ones (mpathXX), but this one remain in "the old style" (maybe because lun_id is a primary key and this one was already taken?) Any idea on how to resolve these problems? Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 3

Re: Issue with NFS and Storage domain setup
by Douglas Duckworth 15 Aug '18

15 Aug '18

https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-… Try the script outlined in section "nfs-check-program." Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit Weill Cornell Medicine E: doug(a)med.cornell.edu O: 212-746-6305 F: 212-746-8690 On Mon, Aug 13, 2018 at 11:21 PM, Inquirer Guy <inquirerguy(a)gmail.com> wrote: > Adding to the below issue, my NODE01 can see the NFS share i created from > the ENGINE01 which I don't know how it got through because when I add a > storage domain from the ovirt engine I still get the error > > > > > > > > On 14 August 2018 at 10:22, Inquirer Guy <inquirerguy(a)gmail.com> wrote: > >> Hi Ovirt, >> >> I successfully installed both ovirt-engine(ENGINE01) and ovirt >> node(NODE01) on a separate machines. I also created a FreeNAS(NAS01) with >> NFS share and already connected to my NODE01, all of these server though I >> haven't setup a DNS server, was manually added hostname on every machines >> and I can lookup and ping on them without a problem, I was able to add the >> NODE01 to my ENGINE01 as well. >> >> My issue was when I tried creating a storage domain on my ENGINE01, I did >> the below steps before running the engine-setup while also following the >> guide on the ovirt url: https://www.ovirt.org/document >> ation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_document…> >> >> #touch /etc/exports >> #systemctl start rpcbind nfs-server >> #systemctl enable rpcbind nfs-server >> #engine-setup >> #mkdir /var/lib/exports/data >> #chown vdsm:kvm /var/lib/exports/data >> >> I added the 2 just in case but I have tried each alone but all fails >> #vi /etc/exports >> /var/lib/exports/data *(rw,sync,no_subtree_check,all >> _squash,anonuid=36,anongid=36) >> /var/lib/exports/data 0.0.0.0/0.0.0.0(rw) >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__0.0.0.0_0.0.0.0-28rw-29…> >> >> #systemctl restart rpc-statd nfs-server >> >> >> Once I started to add my storage domain I get the below error >> >> >> >> Attached is the engine log for your reference. >> >> Hope you guys can help me with these, Im really interested with this >> great product. Thanks! >> > >

2 1

Timezone error when trying to import VMWare created .ova
by jthomasp＠gmualumni.org 15 Aug '18

15 Aug '18

I get: Cannot import VM. Invalid time zone for given OS type. Attribute: vm.vmStatic I found an old thread here: https://lists.ovirt.org/pipermail/users/2014-January/019363.html But it states the issue was resolved in 3.3.1. Running oVirt 4.2.5.1 The VM has the proper time zone set and the clock synced with a time server. Hardware compatibility of the VM has been upgraded to VM Version 9 as recommended on the oVirt IRC channel. I appreciate any help! Thanks, Jason

1 0

"ISCSI multipathing" tab isn't appear in datacenter settings
by navigator80＠tut.by 15 Aug '18

15 Aug '18

Hello. We have 6 servers in our cluster, which use 2 storage through iSCSI connections. Each storage has 2 nodes. Each node has 2 IP addresses in two different VLANs. Each host has 2 networks in this VLANs, so, the iSCSI traffic is separated from other types of traffic. I want to turn on iSCSI multipathing beetween hosts and storage, but "ISCSI multipathing" tab isn't appear in datacenter settings. But when I'm add a additional storage domain, "ISCSI multipathing" tab is displaying. If I want to detach this additional storage domain, "ISCSI multipathing" tab is disappear at once. Why is this happening?

2 1

ovirt-node-ng update to 4.2.5 failed
by p.staniforth＠leedsbeckett.ac.uk 15 Aug '18

15 Aug '18

Hello, I tried to update a ovirt-ng-node from 4.2.4 via the engine and it failed, I also tried using "yum update ovirt-node-ng-image-update". What is the correct way to update a node and how do I delete old layers Thanks, Paul S. The output from "nodectl info" is layers: ovirt-node-ng-4.2.4-0.20180626.0: ovirt-node-ng-4.2.4-0.20180626.0+1 ovirt-node-ng-4.1.9-0.20180124.0: ovirt-node-ng-4.1.9-0.20180124.0+1 ovirt-node-ng-4.2.5.1-0.20180731.0: ovirt-node-ng-4.2.5.1-0.20180731.0+1 bootloader: default: ovirt-node-ng-4.2.4-0.20180626.0+1 entries: ovirt-node-ng-4.2.4-0.20180626.0+1: index: 0 title: ovirt-node-ng-4.2.4-0.20180626.0 kernel: /boot/ovirt-node-ng-4.2.4-0.20180626.0+1/vmlinuz-3.10.0-862.3.3.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn/ovirt-node-ng-4.2.4-0.20180626.0+1 rd.lvm.lv=onn/swap rhgb quiet LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.2.4-0.20180626.0+1" initrd: /boot/ovirt-node-ng-4.2.4-0.20180626.0+1/initramfs-3.10.0-862.3.3.el7.x86_64.img root: /dev/onn/ovirt-node-ng-4.2.4-0.20180626.0+1 ovirt-node-ng-4.1.9-0.20180124.0+1: index: 1 title: ovirt-node-ng-4.1.9-0.20180124.0 kernel: /boot/ovirt-node-ng-4.1.9-0.20180124.0+1/vmlinuz-3.10.0-693.11.6.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn/ovirt-node-ng-4.1.9-0.20180124.0+1 rd.lvm.lv=onn/swap rhgb quiet LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.1.9-0.20180124.0+1" initrd: /boot/ovirt-node-ng-4.1.9-0.20180124.0+1/initramfs-3.10.0-693.11.6.el7.x86_64.img root: /dev/onn/ovirt-node-ng-4.1.9-0.20180124.0+1 current_layer: ovirt-node-ng-4.2.4-0.20180626.0+1

1 0

oVirt 4.2.6.1 - 4.2.6.2 upgrade fails
by Maton, Brett 15 Aug '18

15 Aug '18

Just tried to update my test cluster to 4.2.6.2 : [ INFO ] Stage: Misc configuration [ INFO ] Running vacuum full on the engine schema [ INFO ] Running vacuum full elapsed 0:00:04.523561 [ INFO ] Upgrading CA [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20180814071815.xVSlda.dump'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Configuring Image I/O Proxy [ INFO ] Configuring WebSocket Proxy [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20180814071825.af3Hq2.dump'. [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_1220_default_all_search_engine_string_fields_to_not_null.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed [ INFO ] Yum Performing yum transaction rollback May or may not be relevant in this case but /tmp and /var/tmp are mounted noexec. Any more logs you need let me know. Regards, Brett

5 6