- Users - oVirt List Archives

sanlock ids file broken after server crash
by Johan Bernhardsson 02 Aug '17

02 Aug '17

Hello, The ids file for sanlock is broken on one setup. The first host id in the file is wrong. >From the logfile i have: verify_leader 1 wrong space name 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 0924ff77-ef51-435b-b90d-50bfbf2e8de7 /rhev/data-center/mnt/glusterSD/ Note the broken char in the space name. This also apears. And it seams as the hostid too is broken in the ids file: leader4 sn 0924ff77-ef51-435b-b90d-50bfbf2e�ke7 rn ��7afa5-3a91-415b- a04c-221d3e060163.vbgkvm01.a ts 4351980 cs eefa4dd7 Note the broken chars there as well. If i check the ids file with less or strings the first row where my vbgkvm01 host are. That has broken chars. Can this be repaired in some way without taking down all the virtual machines on that storage? /Johan

3 6

VDSM Command failed: Heartbeat Exceeded
by Neil 02 Aug '17

02 Aug '17

Hi guys, Please could someone assist me, my DC seems to be trying to re-negotiate SPM and apparently it's failing. I tried to delete an old autogenerated snapshot and shortly after that the issue seemed to start, however after about an hour, the snapshot said successfully deleted, and then SPM negotiated again albeit for a short period before it started trying to re-negotiate again. Last week I upgraded from ovirt 3.5 to 3.6, I also upgraded one of my 4 hosts using the 3.6 repo to the latest available from that repo and did a yum update too. I have 4 nodes and my ovirt engine is a KVM guest on another physical machine on the network. I'm using an FC SAN with ATTO HBA's and recently we've started seeing some degraded IO. The SAN appears to be alright and the disks all seem to check out, but we are having rather slow IOPS at the moment, which we trying to track down. ovirt engine CentOS release 6.9 (Final) ebay-cors-filter-1.0.1-0.1.ovirt.el6.noarch ovirt-engine-3.6.7.5-1.el6.noarch ovirt-engine-backend-3.6.7.5-1.el6.noarch ovirt-engine-cli-3.6.2.0-1.el6.noarch ovirt-engine-dbscripts-3.6.7.5-1.el6.noarch ovirt-engine-extension-aaa-jdbc-1.0.7-1.el6.noarch ovirt-engine-extensions-api-impl-3.6.7.5-1.el6.noarch ovirt-engine-jboss-as-7.1.1-1.el6.x86_64 ovirt-engine-lib-3.6.7.5-1.el6.noarch ovirt-engine-restapi-3.6.7.5-1.el6.noarch ovirt-engine-sdk-python-3.6.7.0-1.el6.noarch ovirt-engine-setup-3.6.7.5-1.el6.noarch ovirt-engine-setup-base-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-3.6.7.5-1.el6.noarch ovirt-engine-setup-plugin-websocket-proxy-3.6.7.5-1.el6.noarch ovirt-engine-tools-3.6.7.5-1.el6.noarch ovirt-engine-tools-backup-3.6.7.5-1.el6.noarch ovirt-engine-userportal-3.6.7.5-1.el6.noarch ovirt-engine-vmconsole-proxy-helper-3.6.7.5-1.el6.noarch ovirt-engine-webadmin-portal-3.6.7.5-1.el6.noarch ovirt-engine-websocket-proxy-3.6.7.5-1.el6.noarch ovirt-engine-wildfly-8.2.1-1.el6.x86_64 ovirt-engine-wildfly-overlay-8.0.5-1.el6.noarch ovirt-host-deploy-1.4.1-1.el6.noarch ovirt-host-deploy-java-1.4.1-1.el6.noarch ovirt-image-uploader-3.6.0-1.el6.noarch ovirt-iso-uploader-3.6.0-1.el6.noarch ovirt-release34-1.0.3-1.noarch ovirt-release35-006-1.noarch ovirt-release36-3.6.7-1.noarch ovirt-setup-lib-1.0.1-1.el6.noarch ovirt-vmconsole-1.0.2-1.el6.noarch ovirt-vmconsole-proxy-1.0.2-1.el6.noarch node01 (CentOS 6.9) vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.16.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-62.el6.x86_64 libvirt-client-0.10.2-62.el6.x86_64 libvirt-lock-sanlock-0.10.2-62.el6.x86_64 libvirt-python-0.10.2-62.el6.x86_64 node01 was upgraded out of desperation after I tried changing my DC and cluster version to 3.6, but then found that none of my hosts could be activated out of maintenance due to an incompatibility with 3.6 (I'm still not sure why as searching seemed to indicate Centos 6.x was compatible. I then had to remove all 4 hosts, and change the cluster version back to 3.5 and then re-add them. When I tried changing the cluster version to 3.6 I did get a complaint about using the "legacy protocol" so on each host under Advanced, I changed them to use the JSON protocol, and this seemed to resolve it, however once changing the DC/Cluster back to 3.5 the option to change the protocol back to Legacy is no longer shown. node02 (Centos 6.7) vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.14.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-54.el6_7.6.x86_64 libvirt-client-0.10.2-54.el6_7.6.x86_64 libvirt-lock-sanlock-0.10.2-54.el6_7.6.x86_64 libvirt-python-0.10.2-54.el6_7.6.x86_64 node03 CentOS 6.7 vdsm-4.16.30-0.el6.x86_64 vdsm-cli-4.16.30-0.el6.noarch vdsm-jsonrpc-4.16.30-0.el6.noarch vdsm-python-4.16.30-0.el6.noarch vdsm-python-zombiereaper-4.16.30-0.el6.noarch vdsm-xmlrpc-4.16.30-0.el6.noarch vdsm-yajsonrpc-4.16.30-0.el6.noarch gpxe-roms-qemu-0.9.7-6.14.el6.noarch qemu-img-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-0.12.1.2-2.479.el6_7.2.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.479.el6_7.2.x86_64 libvirt-0.10.2-54.el6_7.6.x86_64 libvirt-client-0.10.2-54.el6_7.6.x86_64 libvirt-lock-sanlock-0.10.2-54.el6_7.6.x86_64 libvirt-python-0.10.2-54.el6_7.6.x86_64 node04 (Centos 6.7) vdsm-4.16.20-1.git3a90f62.el6.x86_64 vdsm-cli-4.16.20-1.git3a90f62.el6.noarch vdsm-jsonrpc-4.16.20-1.git3a90f62.el6.noarch vdsm-python-4.16.20-1.git3a90f62.el6.noarch vdsm-python-zombiereaper-4.16.20-1.git3a90f62.el6.noarch vdsm-xmlrpc-4.16.20-1.git3a90f62.el6.noarch vdsm-yajsonrpc-4.16.20-1.git3a90f62.el6.noarch gpxe-roms-qemu-0.9.7-6.15.el6.noarch qemu-img-0.12.1.2-2.491.el6_8.1.x86_64 qemu-kvm-0.12.1.2-2.491.el6_8.1.x86_64 qemu-kvm-tools-0.12.1.2-2.503.el6_9.3.x86_64 libvirt-0.10.2-60.el6.x86_64 libvirt-client-0.10.2-60.el6.x86_64 libvirt-lock-sanlock-0.10.2-60.el6.x86_64 libvirt-python-0.10.2-60.el6.x86_64 I'm seeing a rather confusing error in the /var/log/messages on all 4 hosts as follows.... Jul 31 16:41:36 node01 multipathd: 36001b4d80001c80d0000000000000000: sdb - directio checker reports path is down Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Jul 31 16:41:41 node01 kernel: sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 Jul 31 16:41:41 node01 kernel: end_request: I/O error, dev sdb, sector 0 I say confusing, because I don't have a 3000GB LUN [root@node01 ~]# fdisk -l | grep 3000 Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes I did have one on Friday, last week, but I trashed it and changed it to a 1500GB LUN instead, so I'm not sure if perhaps this error is still trying to connect to the old LUN perhaps? My LUNS are as follows... Disk /dev/sdb: 3000.0 GB, 2999999528960 bytes (this one doesn't actually exist anymore) Disk /dev/sdc: 1000.0 GB, 999999668224 bytes Disk /dev/sdd: 1000.0 GB, 999999668224 bytes Disk /dev/sde: 1000.0 GB, 999999668224 bytes Disk /dev/sdf: 1000.0 GB, 999999668224 bytes Disk /dev/sdg: 1000.0 GB, 999999668224 bytes Disk /dev/sdh: 1000.0 GB, 999999668224 bytes Disk /dev/sdi: 1000.0 GB, 999999668224 bytes Disk /dev/sdj: 1000.0 GB, 999999668224 bytes Disk /dev/sdk: 1000.0 GB, 999999668224 bytes Disk /dev/sdm: 1000.0 GB, 999999668224 bytes Disk /dev/sdl: 1000.0 GB, 999999668224 bytes Disk /dev/sdn: 1000.0 GB, 999999668224 bytes Disk /dev/sdo: 1000.0 GB, 999999668224 bytes Disk /dev/sdp: 1000.0 GB, 999999668224 bytes Disk /dev/sdq: 1000.0 GB, 999999668224 bytes Disk /dev/sdr: 1000.0 GB, 999988133888 bytes Disk /dev/sds: 1500.0 GB, 1499999764480 bytes Disk /dev/sdt: 1500.0 GB, 1499999502336 bytes I'm quite low on SAN disk space currently so I'm a little hesitant to migrate VM's around for fear of the migrations creating too many snapshots and filling up my SAN. We are in the process of expanding the SAN Array too, but we trying to get to the bottom of the bad IOPS at the moment before adding on addition overhead. Ping tests between hosts and engine all look alright, so I don't suspect network issues. I know this is very vague, everything is currently operational, however as you can see in the attached logs, I'm getting lots of ERROR messages. Any help or guidance is greatly appreciated. Thanks. Regards. Neil Wilson.

2 2

Pass Discard guest OS support?
by Doug Ingham 01 Aug '17

01 Aug '17

Hi All, Just today I noticed that guests can now pass discards to the underlying shared filesystem. http://www.ovirt.org/develop/release-management/features/storage/pass-disca… Is this supported by all of the main Linux guest OS's running the virt agent? And what about Windows guests? (specifically, 2012 & 2016) Cheers, -- Doug

2 1

oVirt and Foreman
by Davide Ferrari 01 Aug '17

01 Aug '17

Hello list is anybody successfully using oVirt + Foreman for VM creation + provisioning? I'm using Foremn (latest version, 1.15.2) with latest oVirt version (4.1.3) but I'm encountering several problem, especially related to disks. For example: - cannot create a VM with multiple disks though Foreman CLI (hammer) - if I create a multidisk VM from Foreman, the second disk always gets the "bootable" flag and not the primary image, making the VMs not bootable at all. Any other Foreman user sharing the pain here? Foramn's list is not so useful so I'm trying to ask here. How do you programmatically create virtual machines with oVirt and Foreman? Should I switch do directly using oVirt API? Thanks in advance Davide

5 15

Deploying training lab
by Andy Michielsen 01 Aug '17

01 Aug '17

Hello all, Don't know if this is the right place to ask this but I would like to set up a trainingslab with oVirt. I have deployed an engine and a host with local storage and want to run 1 server and 5 desktops off it. But the desktops will be used on thin clients or old laptops with some minimal os installation running spice client or a webbrowser. I was wondering if anyone can give me pointer in how to set up a minimal laptop which only need to run an spice client. Kind regards.

3 5

Re: [ovirt-users] Yum error while installing host on Centos7
by Yanir Quinn 01 Aug '17

01 Aug '17

where did you manually install the packages ? engine or host machine ? you can you provide the engine.log to see what might cause the error on the engine's side. maybe rollback the last yum transaction you did and try to run the engine again. as far as for the host installation you might need to check the exiting repositories (Cenots or other existing repos on the machine) , its not recommended to use --skip-broken usually when adding a host. On Tue, Aug 1, 2017 at 11:51 AM, Iurcev, Massimiliano <miurcev(a)inogs.it> wrote: > Unfortunately this didn't work. I tried also to disable totally selinux > without success. > > Then I decided to install gtk2 manually with the --skip-broken option, and > apparently everything went fine. > After this, the host installation goes on without errors. > It says "Installation is closing up", then gets stuck indefinitely. > Now the host-engine looks dead or messed up, even after a reboot... more > in detail, the web portal is no longer accessible. :( > > > > On 30 July 2017 at 10:58, Yanir Quinn <yquinn(a)redhat.com> wrote: > >> Might be a selinux related issue, similar threads suggest either to >> disable selinux completely or run on host: >> >> # setenforce 0 >> # yum clean expire-cache >> # yum update selinux-policy\* >> # setenforce 1 >> >> keeping an eye out for other reasons/solutions. >> >> Regards, >> Yanir Quinn >> >> On Thu, Jul 27, 2017 at 5:32 PM, Iurcev, Massimiliano <miurcev(a)inogs.it> >> wrote: >> >>> I installed ovirt-engine on Centos7. My target is to have a single host >>> machine. >>> During the installation of the (first and unique) host, I get an error: >>> >>> Failed to install Host xxxx. Yum Non-fatal POSTIN scriptlet failure in >>> rpm package gtk2-2.24.28-8.el7.x86_64. >>> >>> This error is followed by other errors: >>> >>> Failed to install Host xxxx. Failed to execute stage 'Package >>> installation': One or more elements within Yum transaction failed. >>> >>> and finally: >>> Host xxxx installation failed. Command returned failure code 1 during >>> SSH session 'root(a)xxxx.mydomain.it'. >>> >>> All other libraries are yum-installed without problems. >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >

1 0

Re: [ovirt-users] PXE boot of oVirt Node 4.1
by Kamarasu Alagarsamy 01 Aug '17

01 Aug '17

Hi Pavol I have similar requirement for Ovirt 4.1 PXE boot on UEFI enabled systems, however not able to do successful kickstart installation. Facing two issues 1) nodectl init or imgbase layout —init not working because of the reason commands not found 2) System keeps on network install cycle due to boot loader not been set or not installed - I don’t know sure exactly why? Could you please help with these issues? kickstart file contents —————————- liveimg —url=http:/../../squasfs.img <— path shortened ignoredisk —all —initlabel zerombr clearpart —all —initlabel autopart —type=thinp bootloader —location=mbr text reboot %post —erroronfail nodectl init %end Regards Kamarasu

1 0

fence issue adding host
by Bill James 31 Jul '17

31 Jul '17

--------------DDA22B530AEEAC5C11E37F1E Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit I'm adding 3 hardware nodes to our cluster. All 3 same type of server and software, HP DL360 G8, centos 7. One fails the fence agent test. The one I'm having problems with has a newer version of ilo firmware, not sure if related. Troublemaker: 2.54 Others: 2.53 ovirt-engine-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64 2017-07-26 15:14:30,215-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,216-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt1.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='23d2c0ab-5dd1-43af-9db3-2a426a539faf', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 1498b3c4 *2017-07-26 15:14:30,414-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 1498b3c4* 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.bll.pm.FenceAgentExecutor] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] Fence action failed using proxy host '10.144.110.99', trying another proxy 2017-07-26 15:14:30,740-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,741-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt2.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='91d8fa70-fd24-4530-90f7-982ff068230b', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 67d837da 2017-07-26 15:14:30,898-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 67d837da 2017-07-26 15:14:30,903-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. I'm not sure the right syntax for fence_ipmilan since even a "good" host fails: [root@ovirt4 prod vdsm]# fence_ipmilan -a 10.144.254.87 -P -l Administrator -p *** -o status -v chassis power status Executing: /usr/bin/ipmitool -I lanplus -H 10.144.254.87 -U Administrator -P [set] -p 623 -L ADMINISTRATOR chassis power status 1 Error: Unable to establish IPMI v2 / RMCP+ session Failed: Unable to obtain correct plug status or plug is not available Any ideas on what the issue is? --------------DDA22B530AEEAC5C11E37F1E Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> I'm adding 3 hardware nodes to our cluster. All 3 same type of server and software, HP DL360 G8, centos 7. One fails the fence agent test. The one I'm having problems with has a newer version of ilo firmware, not sure if related. Troublemaker: 2.54 Others: 2.53 ovirt-engine-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64 2017-07-26 15:14:30,215-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,216-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt1.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='23d2c0ab-5dd1-43af-9db3-2a426a539faf', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 1498b3c4 2017-07-26 15:14:30,414-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 1498b3c4 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.bll.pm.FenceAgentExecutor] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] Fence action failed using proxy host '10.144.110.99', trying another proxy 2017-07-26 15:14:30,740-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,741-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt2.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='91d8fa70-fd24-4530-90f7-982ff068230b', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 67d837da 2017-07-26 15:14:30,898-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 67d837da 2017-07-26 15:14:30,903-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. I'm not sure the right syntax for fence_ipmilan since even a "good" host fails: [root@ovirt4 prod vdsm]# fence_ipmilan -a 10.144.254.87 -P -l Administrator -p *** -o status -v chassis power status Executing: /usr/bin/ipmitool -I lanplus -H 10.144.254.87 -U Administrator -P [set] -p 623 -L ADMINISTRATOR chassis power status 1 Error: Unable to establish IPMI v2 / RMCP+ session Failed: Unable to obtain correct plug status or plug is not available Any ideas on what the issue is? </body> </html> --------------DDA22B530AEEAC5C11E37F1E--

3 4

[ANN] oVirt 4.1.4 GA is now available
by Lev Veyde 31 Jul '17

31 Jul '17

The oVirt Project is pleased to announce the general availability of the oVirt 4.1.4, as of July 31th, 2017 This update is the GA release to the 4.1 series. 4.1.4 brings more than 20 enhancements and more than 90 bugfixes, including more than 70 high or urgent severity fixes, on top of oVirt 4.1 series This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * oVirt Node 4.1 * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available[4] - oVirt Node is already available[4] Additional Resources: * Read more about the oVirt 4.1.4 release highlights: http://www.ovirt.org/release/4.1.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.4/ [4] resources.ovirt.org/pub/ovirt-4.1/iso/ -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 2

official status of Windows support in oVirt/RHEV ?
by Matthias Leopold 31 Jul '17

31 Jul '17

Hi, can someone please point me to resources about official status of Windows support in oVirt and RHEV? are there differences between oVirt and RHEV? i'm not talking about technical details, i know that eg. Windows 2008 or 2016 runs in oVirt, it's about support contracts. i looked at https://www.redhat.com/cms/managed-files/rh-red-hat-virtualization-datashee…, there you have the terms "Full support", "Support" and "Vendor Support". What's the difference? thx matthias

2 2