- Users - oVirt List Archives

OVN Provider setup issues
by Andrea Fagiani 23 Nov '16

23 Nov '16

Hi all, I've been messing around with the ovirt-ovn-provider [1] and I've run into some issues during the initial setup. I have a 5-node cluster (running the hosted-engine VA), LEGACY virtual switch; this test was done on a single host. Following the instructions from the aforementioned blog post, I have downloaded the ovirt-provider-ovn and ovirt-provider-ovn-driver rpms, and built the rpm packages for: - openvswitch (2.6.90) - openvswitch-ovn-common - openvswitch-ovn-host - openvswitch-ovn-central - python-openvswitch I set up a dedicated VM for the OVN controller, installed ovs and ovn-central, started the ovn-northd and ovirt-provider-ovn services. So far so good. I then moved on to the oVirt host and installed the above packages (minus ovn-central) as well as the ovirt-provider-ovn-driver provided, started the ovn-controller service and ran # vdsm-tool ovn-config <ovn controller IP> <host management IP> Executing the suggested checks I noticed that something didn't quite go as planned. Below is the /var/log/openvswitch/ovn-controller.log from the host machine. There are no firewalls involved (not even on the servers) and I also tried disabling SELinux but to no avail. Any ideas? Thanks, Andrea [1] http://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/ 2016-11-07T14:22:09.552Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2016-11-07T14:22:09.553Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2016-11-07T14:22:09.553Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2016-11-07T14:22:09.555Z|00004|reconnect|INFO|tcp:10.100.248.11:6642: connecting... 2016-11-07T14:22:09.555Z|00005|reconnect|INFO|tcp:10.100.248.11:6642: connected 2016-11-07T14:22:09.556Z|00006|ofctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch 2016-11-07T14:22:09.556Z|00007|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... 2016-11-07T14:22:09.557Z|00008|pinctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch 2016-11-07T14:22:09.557Z|00009|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... 2016-11-07T14:22:09.557Z|00010|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected 2016-11-07T14:22:09.557Z|00011|rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected 2016-11-07T14:22:09.558Z|00012|ofctrl|INFO|OpenFlow error: OFPT_ERROR (OF1.3) (xid=0x9): OFPBMC_BAD_FIELD OFPT_FLOW_MOD (OF1.3) (xid=0x9): (***truncated to 64 bytes from 240***) 00000000 04 0e 00 f0 00 00 00 09-00 00 00 00 00 00 00 00 |................| 00000010 00 00 00 00 00 00 00 00-22 00 00 00 00 00 00 00 |........".......| 00000020 ff ff ff ff ff ff ff ff-ff ff ff ff 00 00 00 00 |................| 00000030 00 01 00 04 00 00 00 00-00 04 00 b8 00 00 00 00 |................|

4 11

Cannot remove disk error for ovirt-image-repository VMs
by Gianluca Cecchi 23 Nov '16

23 Nov '16

Hello, I am in 4.0.5 with 3 hosts, Gluster and self hosted engine. If I create a VM through iso and install OS then I can then delete the VM and its related disks without errors If I do the same creating a template (or directly a VM) using CentOS 7 Atomic Host Image in ovirt-image-repository I get these events in sequence hen I delete the VM 10:47:29 VM atomic was successfully removed. 10:47:54 VDSM hosted_engine_1 command failed: Could not remove all image's volumes 10:50:05 Refresh image list succeeded for domain(s): ovirt-image-repository (All file type) tried many times with same behavior The VM has been removed, from web admin gui All disks in "Disks" tab are marked as "OK" Any commands to check actual integrity... in db and filesystems...? Basic messages in engine.log: 2016-11-23 09:47:54,860 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler10) [53f3be13] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM hosted_engine_1 command failed: Could not remove all image's volumes 2016-11-23 09:47:54,860 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler10) [53f3be13] SPMAsyncTask::PollTask: Polling task '555e7dd0-dc32-4cf7-be10-d469fc8b2f8d' (Parent Command 'RemoveVm', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'. 2016-11-23 09:47:54,880 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler10) [53f3be13] BaseAsyncTask::logEndTaskFailure: Task '555e7dd0-dc32-4cf7-be10-d469fc8b2f8d' (Parent Command 'RemoveVm', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Result: 'cleanSuccess' -- Message: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = Could not remove all image's volumes', -- Exception: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = Could not remove all image's volumes' full files: engine.log in gzip format: https://drive.google.com/file/d/0BwoPbcrMv8mvQlVwVDlGTVEtR00/view?usp=shari… vdsm.log of related host in gzip format: https://drive.google.com/file/d/0BwoPbcrMv8mvdDFFOEhTQ3o1ZXM/view?usp=shari… supervdsm.log in gzip format https://drive.google.com/file/d/0BwoPbcrMv8mvbE5ZdXMyc0w1S1U/view?usp=shari… Gianluca

1 0

Fedora 25 images uploaded to oVirt's image repository
by Barak Korren 23 Nov '16

23 Nov '16

The Fedora 25 images had been uploaded to oVirt's public Glance image repository. Both the Atomic image as well as the generic cloud image have been made available. To gain access to the images please select "ovirt-image-repository" from the "Storage" tab in the Web Administration console while "System" is selected in the left-hand tree. If you don't have "ovirt-image-repository" configured as an external provider in your oVirt instance, you can add it by selecting "External Providers" in the left-hand tree clicking on "Add" and filling in the following details: Name: ovirt-image-repository Description: Public Glance repository for oVirt Type: OpenStack Image Provider URL: http://glance.ovirt.org:9292 "Requires Authentication" should be checked off. -- Barak Korren bkorren(a)redhat.com oVirt Infra Team

1 0

Hook to add firewall rules
by Claude Durocher 22 Nov '16

22 Nov '16

------=_=-_OpenGroupware_org_NGMime-9224-1479426132.656558-0------ content-type: text/plain; charset=utf-8 content-length: 176 content-transfer-encoding: quoted-printable I've implemented sucessfully a hook to edit the configuration of some o= f my nics on my ovirt hosts. Is there a way to add firewall rules (iptables) with vdsm hooks? =C2=A0 ------=_=-_OpenGroupware_org_NGMime-9224-1479426132.656558-0------ content-type: text/html; charset=utf-8 content-length: 210 content-transfer-encoding: quoted-printable <html>I've implemented sucessfully a hook to edit the configuration= of some of my nics on my ovirt hosts.<br /><br />Is there a way to add= firewall rules (iptables) with vdsm hooks?<br /> </html> ------=_=-_OpenGroupware_org_NGMime-9224-1479426132.656558-0--------

3 5

Cloning a VM with Ceph/Cinder based disk leaves disk in locked state
by Thomas Klute 22 Nov '16

22 Nov '16

Dear oVirt Users, we're using cinder (based on the Kolla setup) to provide storage for ovirt. Everything works fine except the clone process of a VM. Cloning a VM with NFS based storage works as expected, thus I think it's the cinder integration that causes the problem here. When cloning a VM with cinder/ceph-based storage we see, that the VM clone is created, the attached image is cloned as well, but the disk/image remains in locked state. We then need to issue a "update images set imagestatus=1 where imagestatus=2;" on the engine to make the VM clone work. Is this a bug in the cinder integration? Thanks and best regards, Thomas engine.log: 2016-11-21 10:00:20,216 INFO [org.ovirt.engine.core.bll.CloneVmCommand] (default task-19) [2dd83801] Lock Acquired to object 'EngineLock:{exclusiveLocks='[vm-vertr-kp-klon=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[897d96c8-0ea9-4d06-b815-66a42b63c49b=<VM, ACTION_TYPE_FAILED_VM_IS_BEING_CLONED>, e5e06033-e099-4efe-a5cd-9de2ebc0238b=<DISK, ACTION_TYPE_FAILED_DISK_IS_USED_FOR_CREATE_VM$VmName vm-vertr-kp-klon>]'}' 2016-11-21 10:00:21,290 INFO [org.ovirt.engine.core.bll.CloneVmCommand] (default task-19) [] Running command: CloneVmCommand internal: false. Entities affected : ID: 897d96c8-0ea9-4d06-b815-66a42b63c49b Type: VMAction group CREATE_VM with role type USER 2016-11-21 10:00:21,846 INFO [org.ovirt.engine.core.bll.storage.disk.cinder.CloneSingleCinderDiskCommand] (default task-19) [4c8e58b8] Running command: CloneSingleCinderDiskCommand internal: true. Entities affected : ID: 1f342ea3-49f8-4f65-bf15-ce48514e9bd3 Type: StorageAction group CONFIGURE_VM_STORAGE with role type USER 2016-11-21 10:00:23,143 INFO [org.ovirt.engine.core.bll.AddGraphicsDeviceCommand] (default task-19) [420ca5bf] Running command: AddGraphicsDeviceCommand internal: true. Entities affected : ID: b9f78fd2-9a55-42f0-9ae9-7bca4ae93d9a Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2016-11-21 10:00:23,151 INFO [org.ovirt.engine.core.bll.AddGraphicsDeviceCommand] (default task-19) [7f72e8e4] Running command: AddGraphicsDeviceCommand internal: true. Entities affected : ID: b9f78fd2-9a55-42f0-9ae9-7bca4ae93d9a Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2016-11-21 10:00:23,222 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-19) [7f72e8e4] Correlation ID: 2dd83801, Job ID: a02e5069-a9ef-4b1b-8ec1-b1922d2e3135, Call Stack: null, Custom Event ID: -1, Message: VM vm-vertr-kp-klon was created by admin@internal-authz. 2016-11-21 10:00:23,240 INFO [org.ovirt.engine.core.bll.CloneVmCommand] (default task-19) [7f72e8e4] Lock freed to object 'EngineLock:{exclusiveLocks='[vm-vertr-kp-klon=<VM_NAME, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[897d96c8-0ea9-4d06-b815-66a42b63c49b=<VM, ACTION_TYPE_FAILED_VM_IS_BEING_CLONED>, e5e06033-e099-4efe-a5cd-9de2ebc0238b=<DISK, ACTION_TYPE_FAILED_DISK_IS_USED_FOR_CREATE_VM$VmName vm-vertr-kp-klon>]'}' 2016-11-21 10:00:29,283 INFO [org.ovirt.engine.core.bll.storage.disk.cinder.CloneSingleCinderDiskCommandCallback] (DefaultQuartzScheduler9) [4c8e58b8] Command 'CloneSingleCinderDisk' id: 'a76696d7-f698-4591-9a26-888f47462888' child commands '[]' executions were completed, status 'SUCCEEDED' 2016-11-21 10:00:29,284 INFO [org.ovirt.engine.core.bll.storage.disk.cinder.CloneSingleCinderDiskCommandCallback] (DefaultQuartzScheduler9) [4c8e58b8] Command 'CloneSingleCinderDisk' id: 'a76696d7-f698-4591-9a26-888f47462888' Updating status to 'SUCCEEDED', The command end method logic will be executed by one of its parent commands. Packets: ovirt-engine-jboss-as-7.1.1-1.el7.centos.x86_64 ovirt-vmconsole-proxy-1.0.4-1.el7.centos.noarch ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch ovirt-engine-setup-base-4.0.5.5-1.el7.centos.noarch ovirt-guest-agent-common-1.0.12-3.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-host-deploy-1.5.3-1.el7.centos.noarch ovirt-engine-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-engine-extensions-api-impl-4.0.5.5-1.el7.centos.noarch ovirt-engine-wildfly-10.1.0-1.el7.x86_64 ovirt-engine-dbscripts-4.0.5.5-1.el7.centos.noarch ovirt-engine-restapi-4.0.5.5-1.el7.centos.noarch ovirt-vmconsole-1.0.4-1.el7.centos.noarch ovirt-release36-3.6.6-1.noarch ovirt-engine-lib-4.0.5.5-1.el7.centos.noarch ovirt-setup-lib-1.0.2-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.5.5-1.el7.centos.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-host-deploy-java-1.5.3-1.el7.centos.noarch ovirt-iso-uploader-4.0.2-1.el7.centos.noarch ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch ovirt-engine-extension-aaa-jdbc-1.1.1-1.el7.noarch ovirt-imageio-common-0.4.0-1.el7.noarch ovirt-imageio-proxy-setup-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-image-uploader-4.0.1-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-release40-4.0.5-2.noarch ovirt-engine-tools-4.0.5.5-1.el7.centos.noarch ovirt-engine-dashboard-1.0.5-1.el7.centos.noarch ovirt-engine-backend-4.0.5.5-1.el7.centos.noarch ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-engine-dwh-4.0.5-1.el7.centos.noarch ovirt-engine-cli-3.6.8.1-1.el7.centos.noarch ovirt-imageio-proxy-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-guest-tools-iso-4.0-1.fc23.noarch ovirt-engine-dwh-setup-4.0.5-1.el7.centos.noarch python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64 ovirt-engine-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-tools-backup-4.0.5.5-1.el7.centos.noarch ovirt-engine-webadmin-portal-4.0.5.5-1.el7.centos.noarch ovirt-engine-userportal-4.0.5.5-1.el7.centos.noarch Sollten noch Fragen offen sein, stehen wir Ihnen natürlich jederzeit gerne zur Verfügung. Mit Grüßen aus Dortmund, Thomas Klute -- ________________________________________________________________________ Dipl.-Inform. Thomas Klute klute(a)ingenit.com Geschäftsführer / CEO ---------------------------------------------------------------------- ingenit GmbH & Co. KG Tel. +49 (0)231 58 698-120 Emil-Figge-Strasse 76-80 Fax. +49 (0)231 58 698-121 D-44227 Dortmund www.ingenit.com Registergericht: Amtsgericht Dortmund, HRA 13 914 Gesellschafter : Thomas Klute, Marc-Christian Schröer ________________________________________________________________________

2 1

engine-setup failed on master on Centos 7
by Martin Perina 22 Nov '16

22 Nov '16

Hi, if you have recently tried to install master engine on Centos 7, you may have encountered following error during engine-setup: Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute This is currently tracked by [1] and it's caused by faulty slfj4 1.7.10 package in virt7-ovirt-common-candidate repository. We have untagged faulty package from the repository, but to fix the error you need to downgrade package version to slf4j 1.7.4 provided by Centos [2]. Sorry for inconvenience Martin Perina [1] https://bugzilla.redhat.com/show_bug.cgi?id=1394656 [2] http://mirror.centos.org/centos/7/os/x86_64/Packages/slf4j-1.7.4-3.el7.noar…

1 0

HELP ESXI SERVER UNDER OVIRT-ENGINE
by Ali Mumcu 22 Nov '16

22 Nov '16

Hello Friends; I wanna to learn something about if it is possible or not. Can we run esxı servers under the ovirt-engine ? Thanks.

3 5

Unable to add host
by Oscar Segarra 21 Nov '16

21 Nov '16

Hi, When I try to add the second host from the ovirt interface I get the following error: [image: Imágenes integradas 2] Of course, host vdicnode02 does not appear in the GUI and the gluster looks perfectly up und sync: [root@vdicnode02 ~]# gluster volume status Status of volume: vdic-infr-gv0 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick vdicnode01-priv:/vdic-infr/gv0 49152 0 Y 3039 Brick vdicnode02-priv:/vdic-infr/gv0 49152 0 Y 1999 Brick vdicnode03-priv:/vdic-infr/gv0 49152 0 Y 3456 Self-heal Daemon on localhost N/A N/A Y 3043 Self-heal Daemon on vdicnode03-priv N/A N/A Y 3496 Self-heal Daemon on vdicnode01-priv N/A N/A Y 3267 Task Status of Volume vdic-infr-gv0 ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vdic-infr2-gv0 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick vdicnode01-priv:/vdic-infr2/gv0 49153 0 Y 3048 Brick vdicnode02-priv:/vdic-infr2/gv0 49153 0 Y 2026 Brick vdicnode03-priv:/vdic-infr2/gv0 49153 0 Y 3450 Self-heal Daemon on localhost N/A N/A Y 3043 Self-heal Daemon on vdicnode01-priv N/A N/A Y 3267 Self-heal Daemon on vdicnode03-priv N/A N/A Y 3496 Task Status of Volume vdic-infr2-gv0 ------------------------------------------------------------------------------ There are no active volume tasks [root@vdicnode02 ~]# May I activate self-heal? I'd like to know the difference between None, Deploy and Undeploy from the Hosted Engine option as well: [image: Imágenes integradas 1] Thanks a lot.

3 2

Ovirt SPICE: keyboard does not work
by Oscar Segarra 21 Nov '16

21 Nov '16

Hi, I have deployed a CENTOS 7.2 server in oVirt infraestructure (vdicmysql01) and I want to connect the console session using SPICE from my Windows 10 client. I have installed Remote Viewer but when I click on the console icon on the VMs: [image: Imágenes integradas 3] It downloads the .vv file and it launches the console: [image: Imágenes integradas 4] But keyboard does not work and I cannot interact with machine. I have also tried to connect from users portal but It does not appear: [image: Imágenes integradas 5] Anybody has experienced the same behaviour? Thanks a lot.

1 0

Fail after update (Centos 7.2 oVirt 4.0)
by Marcio Costa 21 Nov '16

21 Nov '16

Hello friends. After I have updated one host with "yum update -y", I have this message and the host fails to connect to storage server (ISO type) (other host not updated yet are working fine): Thread-25::WARNING::2016-11-21 17:26:18,152::lvm::376::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 [] [' WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!', ' Volume group "b55443b5-39a0-4cb6-8018-9c508815dd28" not found', ' Cannot process volume group b55443b5-39a0-4cb6-8018-9c508815dd28'] Thread-25::ERROR::2016-11-21 17:26:18,155::sdc::146::Storage.StorageDomainCache::(_findDomain) domain b55443b5-39a0-4cb6-8018-9c508815dd28 not found Traceback (most recent call last): File "/usr/share/vdsm/storage/sdc.py", line 144, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 174, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'b55443b5-39a0-4cb6-8018-9c508815dd28',) Thread-25::ERROR::2016-11-21 17:26:18,156::monitor::328::Storage.Monitor::(_setupLoop) Setting up monitor for b55443b5-39a0-4cb6-8018-9c508815dd28 failed Traceback (most recent call last): File "/usr/share/vdsm/storage/monitor.py", line 325, in _setupLoop self._setupMonitor() File "/usr/share/vdsm/storage/monitor.py", line 348, in _setupMonitor self._produceDomain() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 405, in wrapper value = meth(self, *a, **kw) File "/usr/share/vdsm/storage/monitor.py", line 366, in _produceDomain self.domain = sdCache.produce(self.sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 101, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 125, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 144, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 174, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'b55443b5-39a0-4cb6-8018-9c508815dd28',) The status of the host is "UP", but I still receiving the messages about the host trying connect to iso domain. I appreciate any help about, thanks!

1 0