July 2017 - Users - oVirt List Archives

imageio: Error setting ImageProxyAddress's value. No such entry with version general.
by Richard Chan 28 Aug '17

28 Aug '17

oVirt 4.1.4 - engine-setup of imageio proxy on a host, at the end it requires: engine-config -s ImageProxyAddress=xxxxxxxx:54323 But on engine: Error setting ImageProxyAddress's value. No such entry with version general. Any ideas thanks! -- Richard Chan

2 1

oVIRT Node / Network Manager / oVirt 4.1
by Devin Acosta 13 Aug '17

13 Aug '17

I noticed that for some reason when I am running oVirt node on my hosts and disabled NetworkManager it appears that it kept turning itself back on, and my understanding is that Network Manager should be disabled. I had to force remove Network Manager in order to get it to stay disabled. I have been seeing strangeness with my VM's where they disconnect, and where hosted-engine keeps trying to non-stop migrate to another host. Just wanted to first confirm about Network Manager and oVirt Node image. -- Devin Acosta Red Hat Certified Architect

2 1

Problemas with ovirtmgmt network used to connect VMs
by FERNANDO FREDIANI 07 Aug '17

07 Aug '17

Has anyone had problem when using the ovirtmgmt bridge to connect VMs ? I am still facing a bizarre problem where some VMs connected to this bridge stop passing traffic. Checking the problem further I see its mac address stops being learned by the bridge and the problem is resolved only with a VM reboot. When I last saw the problem I run brctl showmacs ovirtmgmt and it shows me the VM's mac adress with agening timer 200.19. After the VM reboot I see the same mac with agening timer 0.00. I don't see it in another environment where the ovirtmgmt is not used for VMs. Does anyone have any clue about this type of behavior ? Fernando

2 7

supervdsmd IOError to /dev/stdout
by Richard Chan 03 Aug '17

03 Aug '17

After an upgrade to 4.0 I have a single host that cannot start supervdsmd because of IOError on /dev/stdout. All other hosts upgraded correctly. In the systemd unit I have to hack StandardOutput=null. Any thing I have overlooked? The hosts are all identical and it is just this one that has this weird behaviour. -- Richard Chan

4 7

After upgrading to 4.1.4 unable to start VM or migrate them
by Arman Khalatyan 02 Aug '17

02 Aug '17

Hi, I am running in to trouble with 4.1.4 after engine upgrade I am not able to start or migrate virtual machines: getting following error: General command validation failure Are there any workarounds?

5 11

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

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

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