April 2019 - Users - oVirt List Archives

oVirt 4.3.2 Error: genev_sys_6081 is not present in the system
by Dee Slaw 29 Apr '19

29 Apr '19

Hello, I've installed oVirt 4.3.2 and the problem is that it log messages: VDSM ovirt-04 command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '[Errno 19] genev_sys_6081 is not present in the system'} in Open Virtualization Manager. It also keeps on logging in /var/log/messages: Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9861] device (genev_sys_6081): carrier: link connected Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9864] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34160) Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9866] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9906] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0038] device (genev_sys_6081): carrier: link connected Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0042] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34161) Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0044] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0082] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Also I can see the following in /var/log/openvswitch: 2019-03-22T08:53:12.413Z|131047|bridge|WARN|could not add network device ovn-034a1c-0 to ofproto (File exists) 2019-03-22T08:53:12.431Z|131048|tunnel|WARN|ovn-a21088-0: attempting to add tunnel port with same config as port 'ovn-0836d7-0' (::->192.168.10.24, key=flow, legacy_l2, dp port=2) 2019-03-22T08:53:12.466Z|131055|connmgr|WARN|accept failed (Too many open files) 2019-03-22T08:53:12.466Z|131056|unixctl|WARN|punix:/var/run/openvswitch/ovs-vswitchd.9103.ctl: accept failed: Too many open files In ovsdb-server.log: 2019-03-22T03:24:12.583Z|05792|jsonrpc|WARN|unix#28684: receive error: Connection reset by peer 2019-03-22T03:24:12.583Z|05793|reconnect|WARN|unix#28684: connection dropped (Connection reset by peer) How to fix this issue with geneve tunnels?

4 11

Re: All Windows vms report "Actual timezone in guest doesn't match configuration"
by Strahil 29 Apr '19

29 Apr '19

What happens when you restart ovirt agent services ? Best Regards, Strqhil NikolovOn Apr 26, 2019 03:06, michael(a)wanderingmad.com wrote: > > All of my windows VMs have a yellow exclamation point with the timezone error. The configuration in ovirt says eastern time, and I've tried changing the VM from eastern time to US eastern time, and error does not go away. This is with the latest ovirt guest tools for windows. > _______________________________________________ > 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/XL6XHN5KIEM7G…

2 1

Fetching DiskAttachmentService in ovirt-python-sdk-4
by Kaustav Majumder 29 Apr '19

29 Apr '19

Hi, I am trying to detach and delete disk from my vm. I found this service in the docs DiskAttachmentService http://ovirt.github.io/ovirt-engine-sdk/master/services.m.html#ovirtsdk4.se… I am not able to fetch this service. Below if the snippet of code I am trying. https://pastebin.com/UUu0Pfc8 Error--> File "./pre_setup/delete_vm_disk.py", line 19, in remove_attached_vm_disk attachment.remove(detach_only=False) AttributeError: 'DiskAttachment' object has no attribute 'remove' -- Thanks, Kaustav Majumder

3 4

One Way Flights Deals - Tripiflights
by marketings＠tripiflights.com 29 Apr '19

29 Apr '19

searching for one way flights deals . tripiflights is the perfect place for you. Here you will get best options at reasonable rates - https://go2article.com/article/one-way-flights-deals-tripiflights/

1 0

unable to upload disk images after upgrade to 4.3.3 -- ticket failures
by Edward Berger 29 Apr '19

29 Apr '19

Previously I had issues with the upgrades to 4.3.3 failing because of "stale" image transfer data, so I removed it from the database using the info given here on the mailing list and was able to complete the oVirt node and engine upgrades. Now I have a new problem. I can't upload a disk image anymore, which used to work. "test connection" returns success. In the dashboard Storage/Disks view, it starts and then stops with "paused by system" I tried pointing it at another node, same problem. I tried restarting services ovirt-imageio-proxy on engine and ovirt-imageio-daemon on the node, same failure. in the dashboard events when trying to upload disk I get this error Transfer was stopped by system. Reason: failed to add image ticket to ovirt-imageio-proxy. or when trying to resume transfer "paused by system" giving it the local path again. Transfer was stopped by system. Reason: failure in transfer image ticket renewal. I'm not sure what logs I should be looking deeper into.. Here's what the database says engine=# select * from image_transfers; -[ RECORD 1 ]-------------+------------------------------------- command_id | 59dce2b1-f8ba-44dd-9df9-c6e39773a3f9 command_type | 1024 phase | 4 last_updated | 2019-04-23 12:22:25.098-04 message | Uploading from byte 0 vds_id | disk_id | 6693d5ac-d3eb-43d7-9abe-97c5197efc23 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1996488704 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 -[ RECORD 2 ]-------------+------------------------------------- command_id | 16898219-be5b-4826-8f20-3355fa47272a command_type | 1024 phase | 4 last_updated | 2019-04-23 16:15:34.591-04 message | Uploading from byte 0 vds_id | disk_id | 3b8e3053-bfe4-49d3-abd2-5452b1674400 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1998585856 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 I really need the image uploading to work. Any suggestions on what to do next?

2 2

removal of vdsm-hook-macspoof
by Dan Kenigsberg 28 Apr '19

28 Apr '19

vdsm-hook-macspoof was created to let VM owners override the vdsm-no-mac-spoofing that was once hard-coded on each vNIC. Since ovirt-4.0's Bug 1317441 - [RFE] Allow MAC Anti-Spoofing per interface instead of globally the hook is no longer needed, because ovirt-engine supports selection of filters, including the "Empty" one. Thus, we can finally drop vdsm-hook-macspoof from vdsm code. https://gerrit.ovirt.org/#/c/94613/ does that. If someone still depends on setting the ifacemacspoof custom property, they can find and fix the vnic profiles using a script similar to the following one. Note that ovirtlib does not yet have an easy-to-pull canonical location. from __future__ import print_function import sys from ovirtlib.system import SDKSystemRoot from ovirtlib.netlib import Network, VnicProfile, CustomProperty, NetworkFilter from ovirtlib.datacenterlib import DataCenter system = SDKSystemRoot() system.connect(url=URL, insecure=True, password=PASSWORD, username=USER) spoof_cp = CustomProperty(name='ifacemacspoof', value='true') broken_profiles = [ profile for profile in VnicProfile.iterate(system) if spoof_cp in profile.custom_properties and profile.filter and profile.filter.name == 'vdsm-no-mac-spoofing'] if broken_profiles: if '--modify' in sys.argv: print('clearing vdsm-no-mac-spoof filter from profiles:') for profiles in broken_profiles: print(profile.name) profile.filter = None else: print('''ifacemacspoof custom property is no longer supported by vdsm. vnic profiles that depended on it for connectivity, e.g they serve VMs with in-guest bonds or vlans, must use an empty network filter instead. profiles with ifacemacspoof and vdsm-no-mac-spoof filter:''') for profiles in broken_profiles: print(profile.name) print('run again with --modify to remove the filter') else: print('no profile with ifacemacspoof and vdsm-no-mac-spoof was found.')

1 0

Resuming VM from suspend that is based on iscsi/fc raise an exception.
by 王猛 28 Apr '19

28 Apr '19

Hi, When I resume a VM from suspend that is based on iscsi or fcp, there's always an exception: ----- 2019-04-17 19:33:58,835+0800 ERROR (vm/baaabf11) [virt.vm] (vmId='baaabf11-172d-4fac-9862-86ff05feb085') The vm start process failed (vm:937) 378 Traceback (most recent call last): 379 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 866, in _startUnderlyingVm 380 self._run() 381 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2819, in _run 382 self._connection.restore(fname) 383 File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper 384 ret = f(*args, **kwargs) 385 File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper 386 return func(inst, *args, **kwargs) 387 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4513, in restore 388 if ret == -1: raise libvirtError ('virDomainRestore() failed', conn=self) 389 libvirtError: internal error: Child process (gzip -dc) unexpected exit status 2: 390 gzip: stdin: decompression OK, trailing garbage ignored 391 392 2019-04-17 19:33:58,835+0800 INFO (vm/baaabf11) [virt.vm] (vmId='baaabf11-172d-4fac-9862-86ff05feb085') Changed state to Down: internal error: Child process (gzip -dc) unexpected exit status 2: 393 gzip: stdin: decompression OK, trailing garbage ignored 394 (code=1) (vm:1675) ---------- After i read the Bug 1503468 (https://bugzilla.redhat.com/show_bug.cgi?id=1503468#c40) I know the reason why that happened. But how should I avoid this exception? The only method i know and tested is to change gzip to lzop in /etc/libvirt/qemu.conf. But this is not the way to solve the problem. -- 王猛软件研发手机：13021702660 地址：济南市高新区银荷大厦B座10层 250101 邮箱: wang_meng(a)massclouds.com 网址: www.massclouds.com 山东乾云启创信息科技有限公司

1 0

Re: Arbiter brick disk performance
by Strahil 28 Apr '19

28 Apr '19

I think 2 small ssds (raid 1 mdadm) can do the job better as ssds have lower latencies .You can use them both for OS (minimum needed is 60 GB) and the rest will be plenty for an arbiter. By the way, if you plan using gluster snapshots - use thin LVM for the brick. Best Regards, Strahil NikolovOn Apr 24, 2019 16:20, Leo David <leoalex(a)gmail.com> wrote: > > Hello Everyone, > I need to look into adding some enterprise grade sas disks ( both ssd and spinning ), and since the prices are not too low, I would like to benefit of replica 3 arbitrated. > Therefore, I intend to buy some smaller disks for use them as arbiter brick. > My question is, what performance ( regarding iops, througput ) the arbiter disks need to be. Should they be at least the same as the real data disks ? > Knowing that they only keep metadata, I am thinking that will not be so much pressure on the arbiters. > Any thoughts? > > Thank you ! > > > -- > Best regards, Leo David

3 3

Uncaught exception when open Host "Edit" window
by Vrgotic, Marko 27 Apr '19

27 Apr '19

Dear oVIrt, Short platform summary: * 5 Hosts * 3/5 in Shared DC/Cluster with NetApp NFS storage * 1/5 with Local Storage * 1/5 with Local Storage * oVirt version 4.3.2 , recently upgraded from 4.2.8 Each time I click on “Edit” from Hosts View, for each Host: following error is shown in ui.log: 2019-04-23 10:39:09,064Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-241) [] Permutation name: 0D2DB7A91B469CC36C64386E5632FAC5 2019-04-23 10:39:09,064Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-241) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : oab(...) is null at org.ovirt.engine.ui.webadmin.section.main.view.popup.host.HostPopupView.$lambda$0(HostPopupView.java:693) at org.ovirt.engine.ui.webadmin.section.main.view.popup.host.HostPopupView$lambda$0$Type.eventRaised(HostPopupView.java:693) at org.ovirt.engine.ui.uicompat.Event.$raise(Event.java:99) at org.ovirt.engine.ui.uicommonweb.models.ListModel.$setSelectedItem(ListModel.java:82) at org.ovirt.engine.ui.uicommonweb.models.ListModel.setSelectedItem(ListModel.java:78) at org.ovirt.engine.ui.uicommonweb.models.ListModel.itemsChanged(ListModel.java:236) at org.ovirt.engine.ui.uicommonweb.models.ListModel.$itemsChanged(ListModel.java:224) at org.ovirt.engine.ui.uicommonweb.models.ListModel.$setItems(ListModel.java:102) at org.ovirt.engine.ui.uicommonweb.models.hosts.HostModel.$updateClusterList(HostModel.java:1037) at org.ovirt.engine.ui.uicommonweb.models.hosts.HostModel.$lambda$13(HostModel.java:1017) at org.ovirt.engine.ui.uicommonweb.models.hosts.HostModel$lambda$13$Type.onSuccess(HostModel.java:1017) at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:227) [frontend.jar:] at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:227) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:270) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:270) [frontend.jar:] at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) [gwt-servlet.jar:] at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) [gwt-servlet.jar:] at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) [gwt-servlet.jar:] at Unknown.onreadystatechange<(https://ovirt-staging-engine.avinity.tv/ovirt-engine/webadmin/?locale=en_US line 9 > scriptElement) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:275) [gwt-servlet.jar:] at Unknown.Su/<(https://ovirt-staging-engine.avinity.tv/ovirt-engine/webadmin/?locale=en_US line 9 > scriptElement) at Unknown.anonymous(Unknown) Screenshot of what is shown on UI: [cid:image001.png@01D4F9D2.637FDF40] Please assist. Kindly awaiting your reply. Marko Vrgotic

1 1

NVME-oF
by Daniel Menzel 26 Apr '19

26 Apr '19

Hi guys, just out of curiosity: Have there been any attempts yet to use NVMe over Fabrics as Storage-Backend in oVirt? We have used NVMe-oF several times in the past few weeks/month and its an absolutely gorgeous technology - and more than perfect for virtualization. Best Daniel -- Daniel Menzel Geschäftsführer Menzel IT GmbH Charlottenburger Str. 33a 13086 Berlin +49 (0) 30 / 5130 444 - 00 daniel.menzel(a)menzel-it.net https://menzel-it.net Geschäftsführer: Daniel Menzel Unternehmenssitz: Berlin Handelsregister: Amtsgericht Charlottenburg Handelsregister-Nummer: HRB 149835 B USt-ID: DE 309 226 751

1 0

Re: Ovirt 4.3.2 VM Failover
by Strahil 26 Apr '19

26 Apr '19

I have noticed after full power failiure (all nodes simultaneously - labs don't have UPS yet) one of my VMs was in that state, and I had to restart VDSM in order the engine to notice the crash. Definitely , there is something phishy here... I guess Sahina & Sandro can take a look in your case.. Best Regards, Strahil NikolovOn Apr 26, 2019 02:56, michael(a)wanderingmad.com wrote: > > Is there something in the 4.3.x series that has changed when it comes to VM failover? I have the cluster configurated to automatically migrate all server VMs, but whenever One of the nodes goes down, all the VMs that were on that host switch to a ? status and I have to go and click "host has been rebooted" to have them failed over. > _______________________________________________ > 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/ABOBHQGF2U6JC…

1 0

Ovirt 4.3.2 VM Failover
by michael＠wanderingmad.com 26 Apr '19

26 Apr '19

Is there something in the 4.3.x series that has changed when it comes to VM failover? I have the cluster configurated to automatically migrate all server VMs, but whenever One of the nodes goes down, all the VMs that were on that host switch to a ? status and I have to go and click "host has been rebooted" to have them failed over.

2 1

All Windows vms report "Actual timezone in guest doesn't match configuration"
by michael＠wanderingmad.com 26 Apr '19

26 Apr '19

All of my windows VMs have a yellow exclamation point with the timezone error. The configuration in ovirt says eastern time, and I've tried changing the VM from eastern time to US eastern time, and error does not go away. This is with the latest ovirt guest tools for windows.

1 0

Adding network to VM - What stupid thing have I missed?
by eshwayri＠gmail.com 25 Apr '19

25 Apr '19

When creating a new VM, it looks like I connect it's nic(s) under the "Instantiate VM network interfaces by picking a vNIC profile." setting. The problem I am seeing is that the drop down only has "Empty" and "br-kvm-prod" (my production bridge). I should have two more. Under Networks and vNIC Profiles tabs, I also have a br-kvm-stor and kvm_heart-22 defined which don't appear in that list. Am I missing something I need to do for these additional profiles to also appear in the drop-down? Some of my VMs will need access to the other physical networks.

3 3

New disk creation very slow after upgrade to 4.3.3
by Steffen Luitz 25 Apr '19

25 Apr '19

This is on a 3-node hyperconverged environment with glusterfs. After upgrading to oVirt 4.3.3 (from 4.3.2) creating a new disk takes very long (hours for a 100GByte disk, making it essentially impossible to create a new disk image). In the UI the default is "preallocated" but changing it to thin provision does not make any difference. Regardless of this setting, an fallocate process gets started on the SDM host: /usr/bin/python2 /usr/libexec/vdsm/fallocate 107374182400 /rhev/data-center/mnt/glusterSD/s-vmhost2-ovir.t... Using fallocate to create a file directly on the underlying file system is fast. Using it to create a file through the glusterfs fuse mount is very slow. Thanks for any insights. Steffen

3 2

Upgrade from 4.3.2 to 4.3.3 fails on database schema update
by eshwayri＠gmail.com 24 Apr '19

24 Apr '19

Tried to upgrade to 4.3.3, and during engine-setup I get: 2019-04-20 14:24:47,041-0400 Running upgrade sql script '/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql'... 2019-04-20 14:24:47,043-0400 dbfunc_psql_die --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql ********* QUERY ********** SELECT fn_db_create_constraint('image_transfers', 'fk_image_transfers_command_enitites', 'FOREIGN KEY (command_id) REFERENCES command_entities(command_id) ON DELETE CASCADE'); ************************** 2019-04-20 14:24:47,060-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.executeRaw:863 execute-result: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190420142153-s5heq0.log', '-c', 'apply'], rc=1 2019-04-20 14:24:47,060-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:921 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190420142153-s5heq0.log', '-c', 'apply'] stdout: 2019-04-20 14:24:47,061-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190420142153-s5heq0.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql:3: ERROR: insert or update on table "image_transfers" violates foreign key constraint "fk_image_transfers_command_enitites" DETAIL: Key (command_id)=(7d68555a-71ee-41f5-9f12-0b26b6b9d449) is not present in table "command_entities". CONTEXT: SQL statement "ALTER TABLE image_transfers ADD CONSTRAINT fk_image_transfers_command_enitites FOREIGN KEY (command_id) REFERENCES command_entities(command_id) ON DELETE CASCADE" PL/pgSQL function fn_db_create_constraint(character varying,character varying,text) line 9 at EXECUTE FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql 2019-04-20 14:24:47,061-0400 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:432 schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql 2019-04-20 14:24:47,061-0400 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 434, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed 2019-04-20 14:24:47,064-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': Engine schema refresh failed 2019-04-20 14:24:47,065-0400 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2019-04-20 14:24:47,065-0400 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback

2 2

Re: Upgrading from 4.2.8 to 4.3.3 broke Node NG GlusterFS
by Strahil 24 Apr '19

24 Apr '19

Fix those disconnectes node and run find against a node that has successfully mounted the volume. Best Regards, Strahil NikolovOn Apr 24, 2019 15:31, Andreas Elvers <andreas.elvers+ovirtforum(a)solutions.work> wrote: > > The file handle is stale so find will display: > > "find: '/rhev/data-center/mnt/glusterSD/node01.infra.solutions.work:_vmstore': Transport endpoint is not connected" > > "stat /rhev/data-center/mnt/glusterSD/node01.infra.solutions.work:_vmstore" will output > stat: cannot stat '/rhev/data-center/mnt/glusterSD/node01.infra.solutions.work:_vmstore': Transport endpoint is not connected > > All Nodes are peering with the other nodes: > ----- > Saiph:~ andreas$ ssh node01 gluster peer status > Number of Peers: 2 > > Hostname: node02.infra.solutions.work > Uuid: 87fab40a-2395-41ce-857d-0b846e078cdb > State: Peer in Cluster (Connected) > > Hostname: node03.infra.solutions.work > Uuid: 49025f81-e7c1-4760-be03-f36e0f403d26 > State: Peer in Cluster (Connected) > ---- > Saiph:~ andreas$ ssh node02 gluster peer status > Number of Peers: 2 > > Hostname: node03.infra.solutions.work > Uuid: 49025f81-e7c1-4760-be03-f36e0f403d26 > State: Peer in Cluster (Disconnected) > > Hostname: node01.infra.solutions.work > Uuid: f25e6bff-e5e2-465f-a33e-9148bef94633 > State: Peer in Cluster (Connected) > ---- > ssh node03 gluster peer status > Number of Peers: 2 > > Hostname: node02.infra.solutions.work > Uuid: 87fab40a-2395-41ce-857d-0b846e078cdb > State: Peer in Cluster (Connected) > > Hostname: node01.infra.solutions.work > Uuid: f25e6bff-e5e2-465f-a33e-9148bef94633 > State: Peer in Cluster (Connected) > _______________________________________________ > 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/DI6AWTLIQIPWN…

2 1

error while setup
by W3SERVICES 24 Apr '19

24 Apr '19

PLAY [gluster_servers] ********************************************************* TASK [Run a shell script] ****************************************************** changed: [localhost.localdomain] => (item=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h localhost.localdomain) PLAY RECAP ********************************************************************* localhost.localdomain : ok=1 changed=1 unreachable=0 failed=0 PLAY [gluster_servers] ********************************************************* TASK [Enable or disable services] ********************************************** ok: [localhost.localdomain] => (item=chronyd) PLAY RECAP ********************************************************************* localhost.localdomain : ok=1 changed=0 unreachable=0 failed=0 PLAY [gluster_servers] ********************************************************* TASK [start/stop/restart/reload services] ************************************** changed: [localhost.localdomain] => (item=chronyd) PLAY RECAP ********************************************************************* localhost.localdomain : ok=1 changed=1 unreachable=0 failed=0 PLAY [gluster_servers] ********************************************************* TASK [Run a command in the shell] ********************************************** changed: [localhost.localdomain] => (item=vdsm-tool configure --force) PLAY RECAP ********************************************************************* localhost.localdomain : ok=1 changed=1 unreachable=0 failed=0 PLAY [gluster_servers] ********************************************************* TASK [Run a shell script] ****************************************************** changed: [localhost.localdomain] => (item=/usr/share/gdeploy/scripts/blacklist_all_disks.sh) PLAY RECAP ********************************************************************* localhost.localdomain : ok=1 changed=1 unreachable=0 failed=0 PLAY [gluster_servers] ********************************************************* TASK [Clean up filesystem signature] ******************************************* skipping: [localhost.localdomain] => (item=/dev/sdb) TASK [Create Physical Volume] ************************************************** failed: [localhost.localdomain] (item=/dev/sdb) => {"changed": false, "failed_when_result": true, "item": "/dev/sdb", "msg": " Device /dev/sdb not found.\n", "rc": 5} to retry, use: --limit @/tmp/tmpQtig6r/pvcreate.retry PLAY RECAP ********************************************************************* localhost.localdomain : ok=0 changed=0 unreachable=0 failed=1 From *Sunil Kumar | 09967222267Tech Head and Cloud Solution Architect* *-----------------------------------------------------------------------* *Website : * *https://w3services.net <https://www.w3services.net/>* https://w3services.com (Tech Consultancy) Office Tel. +91 09300670068 | Write A Google Review ( Help Us ) <https://goo.gl/tKGa79> *-----------------------------------------------------------------------*

1 0

[ANN] oVirt 4.3.3 second async update is now available
by Sandro Bonazzola 24 Apr '19

24 Apr '19

The oVirt Team has just released a new version of the following packages: - ovirt-engine-4.3.3.6 The async release addresses the following bugs: - Bug 1701205 <https://bugzilla.redhat.com/show_bug.cgi?id=1701205> - Creating a new VM over the not defaulted cluster fails with "CPU Profile doesn't match provided Cluster" error. - Bug 1700759 <https://bugzilla.redhat.com/show_bug.cgi?id=1700759> - engine failed schema refresh v4.3.2 -> v4.3.3 Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Arbiter brick disk performance
by Leo David 24 Apr '19

24 Apr '19

Hello Everyone, I need to look into adding some enterprise grade sas disks ( both ssd and spinning ), and since the prices are not too low, I would like to benefit of replica 3 arbitrated. Therefore, I intend to buy some smaller disks for use them as arbiter brick. My question is, what performance ( regarding iops, througput ) the arbiter disks need to be. Should they be at least the same as the real data disks ? Knowing that they only keep metadata, I am thinking that will not be so much pressure on the arbiters. Any thoughts? Thank you ! -- Best regards, Leo David

1 0

Upgrading from 4.2.8 to 4.3.3 broke Node NG GlusterFS
by Andreas Elvers 24 Apr '19

24 Apr '19

Hi, I am currently upgrading my oVirt setup from 4.2.8 to 4.3.3.1. The setup consists of: Datacenter/Cluster Default: [fully upgraded to 4.3.3.1] 2 nodes (node04,node05)- NFS storage domain with self hosted engine Datacenter Luise: Cluster1: 3 nodes (node01,node02,node03) - Node NG with GlusterFS - Ceph Cinder storage domain [Node1 and Node3 are upgraded to 4.3.3.1, Node2 is on 4.2.8] Cluster2: 1 node (node06) - only Ceph Cinder storage domain [fully upgraded to 4.3.3.1] Problems started when upgrading Luise/Cluster1 with GlusterFS: (I always waited for GlusterFS to be fully synced before proceeding to the next step) - Upgrade node01 to 4.3.3 -> OK - Upgrade node03 to 4.3.3.1 -> OK - Upgrade node01 to 4.3.3.1 -> GlusterFS became unstable. I now get the error message: VDSM node03.infra.solutions.work command ConnectStoragePoolVDS failed: Cannot find master domain: u'spUUID=f3218bf7-6158-4b2b-b272-51cdc3280376, msdUUID=02a32017-cbe6-4407-b825-4e558b784157' And on node03 there is a problem with Gluster: node03#: ls -l /rhev/data-center/mnt/glusterSD/node01.infra.solutions.work:_vmstore ls: cannot access /rhev/data-center/mnt/glusterSD/node01.infra.solutions.work:_vmstore: Transport endpoint is not connected The directory is available on node01 and node02. The engine is reporting the brick on node03 as down. Node03 and Node06 are shown as NonOperational, because they are not able to access the gluster storage domain. A “gluster peer status” on node1, node2, and node3 shows all peers connected. “gluster volume heal vmstore info” shows for all nodes: gluster volume heal vmstore info Brick node01.infra.solutions.work:/gluster_bricks/vmstore/vmstore Status: Transport endpoint is not connected Number of entries: - Brick node02.infra.solutions.work:/gluster_bricks/vmstore/vmstore <gfid:0bcb7825-e649-4178-a899-c5cc04c95286> <gfid:71ec8035-f5a5-4e61-bb34-5ad9db28c0eb> <gfid:16d5961e-c3bb-4493-a51d-bf83074c4cc7> /02a32017-cbe6-4407-b825-4e558b784157/dom_md/ids /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.66 <gfid:5fe350e4-1eb5-4b6f-a3fb-42c98b7b2f8d> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.60 /02a32017-cbe6-4407-b825-4e558b784157/images/a3a10398-9698-4b73-84d9-9735448e3534/6161e310-4ad6-42d9-8117-5a89c5b2b4b6 <gfid:8eb9fd30-fdb9-442b-9c54-8ba256d7981b> <gfid:c72001be-e7d3-4b34-bac5-9ab50b609eea> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.96 <gfid:447ec09b-336e-4d2b-8338-f31329ee7a55> <gfid:9d7db516-d6fb-43d8-a069-dcbc1d72e62a> /.shard/d66880de-3fa1-4362-8c43-574a173c5f7d.133 <gfid:2412d449-d3ed-40ef-b7eb-d81bdf7c5c05> <gfid:0fae358b-2cdd-4064-b63c-7f31a35bc35a> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.38 /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.67 /__DIRECT_IO_TEST__ <gfid:a7945526-9ff3-40fe-b1e2-3921117ef738> <gfid:e78e9c1f-ce6b-4871-b5bf-9bde34685b99> /02a32017-cbe6-4407-b825-4e558b784157/images/493188b2-c137-4440-99ee-43a753842a7d/9aa2d139-e3bd-406b-8fe0-b189123eaa73 <gfid:3aed3fb6-044a-4371-9302-e0bd54cbd794> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.64 /.shard/d66880de-3fa1-4362-8c43-574a173c5f7d.132 <gfid:f7631be7-2ab5-4985-904d-69174c0e1267> <gfid:43001625-1aad-4032-a76e-4cc2a51de2b3> <gfid:6ae3fe7f-15c9-4103-960c-faba0ba59cb3> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.44 /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.9 /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.69 <gfid:f20cc6f7-9391-4260-9238-3e1d0cabbfa3> /02a32017-cbe6-4407-b825-4e558b784157/images/12e647fb-20aa-4957-b659-05fa75a9215e/f7e4b2a3-ab84-4eb5-a4e7-7208ddad8156 <gfid:c540368a-4431-4405-9a59-e11a217d0ea6> <gfid:4e698a74-39dc-40a3-ac9c-14456420ab66> <gfid:afd48e71-ff23-42d7-aef4-b2e2167b75e8> <gfid:194589b3-0760-4150-80ef-d87376813835> <gfid:6e17ead1-88cc-4e3e-84fa-7495c4fc3a0e> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.35 /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.32 <gfid:982d071f-2081-4371-b007-bc48d8167e7c> <gfid:e2285905-a8da-44f5-8c56-1f8a4d6326a8> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.39 <gfid:956c7d9c-2f96-42d1-bf6e-57bc9e534f84> <gfid:16162bc7-201a-4842-a41a-af2cc4fb8a9e> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.34 /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.68 Status: Connected Number of entries: 47 Brick node03.infra.solutions.work:/gluster_bricks/vmstore/vmstore /02a32017-cbe6-4407-b825-4e558b784157/images/12e647fb-20aa-4957-b659-05fa75a9215e/f7e4b2a3-ab84-4eb5-a4e7-7208ddad8156 <gfid:c540368a-4431-4405-9a59-e11a217d0ea6> <gfid:4e698a74-39dc-40a3-ac9c-14456420ab66> <gfid:afd48e71-ff23-42d7-aef4-b2e2167b75e8> <gfid:194589b3-0760-4150-80ef-d87376813835> <gfid:6e17ead1-88cc-4e3e-84fa-7495c4fc3a0e> <gfid:099284a6-9538-4f9a-928a-d9b704fe0735> <gfid:75d3c8f7-d67a-49a4-9cd4-7fff202df40d> <gfid:982d071f-2081-4371-b007-bc48d8167e7c> <gfid:e2285905-a8da-44f5-8c56-1f8a4d6326a8> <gfid:447ec09b-336e-4d2b-8338-f31329ee7a55> <gfid:956c7d9c-2f96-42d1-bf6e-57bc9e534f84> /.shard/d66880de-3fa1-4362-8c43-574a173c5f7d.133 <gfid:43001625-1aad-4032-a76e-4cc2a51de2b3> <gfid:6ae3fe7f-15c9-4103-960c-faba0ba59cb3> <gfid:1a0b2737-9172-4c51-aa77-e93e9671840c> <gfid:eb471e13-6749-4f62-b1f5-15a44f8990c2> <gfid:a7945526-9ff3-40fe-b1e2-3921117ef738> <gfid:e78e9c1f-ce6b-4871-b5bf-9bde34685b99> /02a32017-cbe6-4407-b825-4e558b784157/images/493188b2-c137-4440-99ee-43a753842a7d/9aa2d139-e3bd-406b-8fe0-b189123eaa73 <gfid:6b418e80-9f61-4d6e-ba77-8a1969d9a99b> <gfid:914c72d2-e45e-48f2-b7ef-5846b13f7a91> <gfid:2bd28bdb-1dc6-41d5-96be-c696f452e3f2> <gfid:9d7db516-d6fb-43d8-a069-dcbc1d72e62a> <gfid:f7631be7-2ab5-4985-904d-69174c0e1267> <gfid:16162bc7-201a-4842-a41a-af2cc4fb8a9e> /.shard/40948f85-2212-47f9-bd5e-102a8dd632b8.44 <gfid:afc6d611-528d-441b-b74e-c5fae6672088> <gfid:707308e9-e8e5-487a-b0f1-a816720c4243> <gfid:5f1a81a7-7c42-4226-9142-1b5b35c2b1e9> <gfid:f20cc6f7-9391-4260-9238-3e1d0cabbfa3> <gfid:0bcb7825-e649-4178-a899-c5cc04c95286> <gfid:71ec8035-f5a5-4e61-bb34-5ad9db28c0eb> <gfid:16d5961e-c3bb-4493-a51d-bf83074c4cc7> /02a32017-cbe6-4407-b825-4e558b784157/dom_md/ids <gfid:7661180b-1917-4a7b-9749-5dfb826c4449> <gfid:5fe350e4-1eb5-4b6f-a3fb-42c98b7b2f8d> <gfid:a6197593-7e09-4d3f-b538-9cd1ebadd6c9> /02a32017-cbe6-4407-b825-4e558b784157/images/a3a10398-9698-4b73-84d9-9735448e3534/6161e310-4ad6-42d9-8117-5a89c5b2b4b6 <gfid:8eb9fd30-fdb9-442b-9c54-8ba256d7981b> <gfid:c72001be-e7d3-4b34-bac5-9ab50b609eea> <gfid:3aed3fb6-044a-4371-9302-e0bd54cbd794> /.shard/d66880de-3fa1-4362-8c43-574a173c5f7d.132 <gfid:2412d449-d3ed-40ef-b7eb-d81bdf7c5c05> <gfid:0fae358b-2cdd-4064-b63c-7f31a35bc35a> <gfid:c0ca2784-a8af-44b3-9091-a1eaf4c8676f> /__DIRECT_IO_TEST__ Status: Connected Number of entries: 47 On Node03 there are several self healing processes, that seem to be doing nothing. Oh well.. What now? Best regards, - Andreas

2 4

Unable to use MAC address starting with reserved value 0xFE
by Ricardo Alonso 24 Apr '19

24 Apr '19

Is there a way to use a mac starting with FE? The machine has a license requirement attached to the mac address, and when I try to start it, it fails with the message: VM is down with error. Exit message: unsupported configuration: Unable to use MAC address starting with reserved value 0xFE - 'fe:XX:XX:XX:XX:XX'

1 0

Upgrade Initiation fails without obvious reason
by Vrgotic, Marko 24 Apr '19

24 Apr '19

Dear oVIrt, Short platform summary: * 5 Hosts * 3/5 in Shared DC/Cluster with NetApp NFS storage * 1/5 with Local Storage * 1/5 with Local Storage * oVirt version 4.3.2 , recently upgraded from 4.2.8 Host related: ovirt-staging-hv-04 Host is moved to Maintenance. Selected Upgrade, following log lines are written: 2019-04-23 10:58:32,639Z INFO [org.ovirt.engine.core.bll.hostdeploy.UpgradeHostCommand] (default task-247) [11381573-01c0-4e48-8634-c577988a8f79] Running command: UpgradeHostCommand internal: false. Entities affected : ID: 9462386e-74d1-4000-96b0-0e081ec7d069 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN 2019-04-23 10:58:32,648Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-247) [11381573-01c0-4e48-8634-c577988a8f79] EVENT_ID: HOST_UPGRADE_STARTED(840), Host ovirt-staging-hv-04 upgrade was started (User: mvrgotic@ictv.com@ictv.com-authz<mailto:mvrgotic@ictv.com@ictv.com-authz>). However, the host is still in Maintenance mode, expected is Installing: [cid:image001.png@01D4F9D5.35D3A4C0] Tail YUM logs also shows the procedure did not start and packages are not being updated. Kindly awaiting you reply. Marko Vrgotic

3 2

Prevent 2 different VMs from running on the same host
by Paulo Silva 24 Apr '19

24 Apr '19

Hi, I have a cluster of 6 hosts using ovirt 4.3 and I want to make sure that 2 VMs are always started on different hosts. Is it possible to prevent 2 different VMs from running on the same physical host without specifying manually a different set of hosts where each VM can start running? Thanks -- Paulo Silva <paulojjs(a)gmail.com>

2 1

Scale out ovirt 4.3 (from 3 to 6 or 9 nodes) with hyperconverged setup and Gluster
by adrianquintero＠gmail.com 24 Apr '19

24 Apr '19

Hello, I have a 3 node Hyperconverged setup with gluster and added 3 new nodes to the cluster for a total of 6 servers. I am now taking advantage of more compute power but cant scale out my storage volumes. Current Hyperconverged setup: - host1.mydomain.com ---> Bricks: engine data1 vmstore1 - host2.mydomain.com ---> Bricks: engine data1 vmstore1 - host3.mydomain.com ---> Bricks: engine data1 vmstore1 From these 3 servers we get the following Volumes: - engine(host1:engine, host2:engine, host3:engine) - data1 (host1:data1, host2:data1, host3:data1) - vmstore1 (host1:vmstore1, host2:vmstore1, host3:vmstore11) The following are the newly added servers to the cluster, however as you can see there are no gluster bricks - host4.mydomain.com - host5.mydomain.com - host6.mydomain.com I know that the bricks must be added in sets of 3 and per the first 3 hosts that is how it was deployed thru the web UI. Questions: -how can i extend the gluster volumes engine, data1 and vmstore using host4, host5 and host6? -Do I need to configure gluster volumes manually through the OS CLI in order for them to span amongst all 6 servers? -If I configure the fail storage scenario manually will oVirt know about it?, will it still be hyperconverged? I have only seen 3 host hyperconverged setup examples with gluster, but have not found examples for 6, 9 or 12 host cluster with gluster. I know it might be a lack of understanding from my end on how ovirt and gluster integrate with one another. If you can point me in the right direction would be great. thanks,

4 6