- 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