- Users - oVirt List Archives

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

26 Feb '19

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

1 0

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

26 Feb '19

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

3 2

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

26 Feb '19

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

2 7

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

26 Feb '19

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

1 0

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

26 Feb '19

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

1 0

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

25 Feb '19

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

7 20

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

25 Feb '19

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

1 0

Re: Ovirt Glusterfs
by Strahil 25 Feb '19

25 Feb '19

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

1 0

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

25 Feb '19

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

3 3

Re: HostedEngine Unreachable
by Simone Tiraboschi 25 Feb '19

25 Feb '19

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

1 0