- Users - oVirt List Archives

Home ovirt setup (new to ovirt)
by ryancoeit＠gmail.com 09 Oct '18

09 Oct '18

Hello My names ryan and im studying for my rhcsa and rhce also a linux enthusiast, im setting up my first ovirt server and have my ovirt engine setup aswell as my data center and host, ive come to the point where i need to configure storage. Ovirt is installed on a 256GB nvme ssd with my iso and master data domain pointed to the drive. I have 2 WD 2TB hard drives available that havent been allocated yet, id like them to be combined with lvm and have a single share exported via nfs that all vm's (3 vm's) in total can access for data storage Is this possible ? Kind Regards Ryan

5 4

removing FC storage
by David David 09 Oct '18

09 Oct '18

How to remove FC storage domain correctly? I turned off the FC storage domain in the cluster (maintenance -> detach -> remove), but the volume group still remained on the hosts and I would have to remove them manually and need to clear a multipath links too, before I turn off the LUN on the FC storage. How will the cluster behave if there are differences in the volume groups on the hosts? Because I can’t simultaneously delete partitions and multipath links on all hosts, and this process will occur sequentially on each host.

2 1

Cannot delete a stuck task
by Markus Schaufler 09 Oct '18

09 Oct '18

Hi, The task "Adding disk" is stuck at "creating volume". I tried to delete the task with "taskcleaner.sh", at CLI with list / remove jobs, deleted lastly the VM and restartet the engine-vm. But its still in the task list. Any idea to remove this job?

2 5

Gluster JSON-RPC errors
by Maton, Brett 09 Oct '18

09 Oct '18

I'm seeing the following errors appear in the event log every 10 minutes for each participating host in the gluster cluster GetGlusterVolumeHealInfoVDS failed: Internal JSON-RPC error: {'reason': "'bool' object has no attribute 'getiterator'"} Gluster brick health is good Any ideas ? oVirt 4.2.7.2-1.el7 CentOS 7

4 7

New oVirt deployment suggestions
by Stefano Danzi 08 Oct '18

08 Oct '18

Hello! I'm almost ready to start with a new oVirt deplyment. I will use CentOS 7, self hosting engine and glusert storage. I have 3 phisical host. Each host has four NIC. My first idea is: - configure bond betwheen NICs - configure a VLAN interface for management network (and local lan) - configure a VLAN interface for gluster network - configure gluster for the hosted engine - start "hosted-engine --deploy" process is this enough? do I need a phisical dedicated NIC for management network? Bye

5 12

VM Portal noVNC Console invocation
by briwils2＠cisco.com 08 Oct '18

08 Oct '18

When I use the VM Portal and invoke a console I'm not sure how i can leverage the html5 noVNC version of this. I can only get the .vv file and would like to use a web based console, or rather provide them to users of an engine. TIA Brian

2 1

cockpit-networkmanager
by Jonathan Baecker 06 Oct '18

06 Oct '18

Hello Everybody, I only wanted to ask you, if the ovirt hosts does need the cockpit-networkmanager? I ask because I can not updates my CentOS hosts, I get always the message: Transaction check error: file /usr/share/cockpit/networkmanager/manifest.json from install of cockpit-system-176-2.el7.centos.noarch conflicts with file from package cockpit-networkmanager-172-1.el7.noarch file /usr/share/cockpit/networkmanager/po.ca.js.gz from install of cockpit-system-176-2.el7.centos.noarch conflicts with file from package cockpit-networkmanager-172-1.el7.noarch file /usr/share/cockpit/networkmanager/po.cs.js.gz from install of cockpit-system-176-2.el7.centos.noarch conflicts with file from package cockpit-networkmanager-172-1.el7.noarch ... When I remove the cockpit-networkmanager the error is gone, but after making a yum update I'm not able to reinstall the cockpit-networkmanager because it is still want to use the old version. Jonathan

1 0

master domain wont activate
by Vincent Royer 06 Oct '18

06 Oct '18

I was attempting to migrate from nfs to iscsi storage domains. I have reached a state where I can no longer activate the old master storage domain, and thus no others will activate either. I'm ready to give up on the installation and just move to an HCI deployment instead. Wipe all the hosts clean and start again. My plan was to create and use an export domain, then wipe the nodes and set them up HCI where I could re-import. But without being able to activate a master domain, I can't create the export domain. I'm not sure why it can't find the master anymore, as nothing has happened to the NFS storage, but the error in vdsm says it just can't find it: StoragePoolMasterNotFound: Cannot find master domain: u'spUUID=5a77bed1-0238-030c-0122-0000000003b3, msdUUID=d3165759-07c2-46ae-b7b8-b6226a929d68' 2018-10-03 22:40:33,751-0700 INFO (jsonrpc/3) [storage.TaskManager.Task] (Task='83f33db5-90f3-4064-87df-0512ab9b6378') aborting: Task is aborted: "Cannot find master domain: u'spUUID=5a77bed1-0238-030c-0122-0000000003b3, msdUUID=d3165759-07c2-46ae-b7b8-b6226a929d68'" - code 304 (task:1181) 2018-10-03 22:40:33,751-0700 ERROR (jsonrpc/3) [storage.Dispatcher] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=5a77bed1-0238-030c-0122-0000000003b3, msdUUID=d3165759-07c2-46ae-b7b8-b6226a929d68' (dispatcher:82) 2018-10-03 22:40:33,751-0700 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call StoragePool.connect failed (error 304) in 0.17 seconds (__init__:573) 2018-10-03 22:40:34,200-0700 INFO (jsonrpc/1) [api.host] START getStats() from=::ffff:172.16.100.13,39028 (api:46) When I look in cockpit on the hosts, the storage domain is mounted and seems fine.

3 12

Re: Error when running hosted-engine deploy on system with bond of bonds
by Karli Sjöberg 05 Oct '18

05 Oct '18

2 1

Re: Error when running hosted-engine deploy on system with bond of bonds
by Karli Sjöberg 05 Oct '18

05 Oct '18

2 1

Bad libvirt-spice certificate - regenerate?
by Chris Adams 05 Oct '18

05 Oct '18

I have an oVirt 4.1 cluster that was initially installed with 3.5 in 2014. The SSL certificates on the physical hosts in /etc/pki/vdsm/libvirt-spice have a problem - the "not before" date is invalid (it doesn't include a time zone), and so I can't connect to VM consoles from a client with OpenSSL 1.1.0i (up to date Fedora 27). How can I regenerate these certificates? Also, I noticed they expire next year - is that expiration handled automatically? -- Chris Adams <cma(a)cmadams.net>

3 3

Error when running hosted-engine deploy on system with bond of bonds
by Ben Webber 05 Oct '18

05 Oct '18

Hi, I'm trying to set up ovirt using the hosted-engine --deploy command on CentOS7, but am encountering an error. I am running a slightly unusual network configuration. I have two fairly basic non stacked gigabit switches with port channels connecting the two switches together. I have a lacp bond from the host consisting of 4 ports to each switch (bond1 and bond2). I have then created an active-backup bond (bond0) using the two lacp bonds as slaves in the hope to create ha at the switch layer using my basic switches. There is then a VLAN (101) on bond0. This network configuration runs fine on the host, however, when run, after a short while, the hosted-engine --deploy command outputs the following error: ... [ INFO ] TASK [Force host-deploy in offline mode] [ INFO ] ok: [localhost] [ INFO ] TASK [Add host] [ INFO ] changed: [localhost] [ INFO ] TASK [Wait for the host to be up] [ INFO ] ok: [localhost] [ INFO ] TASK [Check host status] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host has been set in non_operational status, please check engine logs, fix accordingly and re-deploy.\n"} ... Looking in /var/log/ovirt-engine/engine.log on the machine created, I can see the following errors logged: ... 2018-10-04 21:51:30,116+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] START, HostSetupNetworksVDSCommand(HostName = ov1.test.local, HostSetupNetworksVdsCommandParameters:{hostId='7440c9b9-e530-4341-a317-d3a9041dc777', vds='Host[ov1.test.local,7440c9b9-e530-4341-a317-d3a9041dc777]', rollbackOnFailure='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='true', networkName='ovirtmgmt', vdsmName='ovirtmgmt', nicName='bond0', vlan='101', vmNetwork='true', stp='false', properties='null', ipv4BootProtocol='STATIC_IP', ipv4Address='192.168.1.11', ipv4Netmask='255.255.255.0', ipv4Gateway='192.168.1.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='null'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSwitchType='LEGACY'}), log id: 4f0c7eaa 2018-10-04 21:51:30,121+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] FINISH, HostSetupNetworksVDSCommand, log id: 4f0c7eaa 2018-10-04 21:51:30,645+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] Failed in 'HostSetupNetworksVDS' method 2018-10-04 21:51:30,687+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ov1.test.local command HostSetupNetworksVDS failed: Unknown nics in: ['bond1', 'bond2'] 2018-10-04 21:51:30,688+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Unknown nics in: ['bond1', 'bond2'], code = 23 ... It looks like when HostSetupNetworksVDS is run, it is checking that the slave interfaces to the bonds are physical network devices and being as the slaves of bond0 are bond1 and bond2, rather than physical devices, it then throws the error Unknown nics in: ['bond1', 'bond2']. Is there anything I can do or any configuration that I can put anywhere to make it work with this "stacked bond" configuration or does ovirt just not work when bonds are set up like this? Thanks in advance, Ben

3 9

[ANN] oVirt Node 4.2.6 async update is now available
by Sandro Bonazzola 05 Oct '18

05 Oct '18

The oVirt Team has just released a new version of oVirt Node image including latest CentOS updates, fixing a regression introduced in kernel package [1] breaking IP over infiniband. We recommend to users to upgrade to this new release. Errata included: CEEA-2018:2397 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023021.ht…> CESA-2018:2748 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023027.ht…> CEBA-2018:2760 CentOS 7 ipa BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023029.ht…> CESA-2018:2768 Moderate CentOS 7 nss Security Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023030.ht…> CEBA-2018:2753 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023033.ht…> CEBA-2018:2756 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023034.ht…> CEBA-2018:2769 CentOS 7 libvirt BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023038.ht…> CEBA-2018:2761 CentOS 7 kexec-tools BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023041.ht…> CEBA-2018:2758 CentOS 7 firewalld BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023045.ht…> CEBA-2018:2764 CentOS 7 initscripts BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023046.ht…> CESA-2018:2731 Important CentOS 7 spice Security Update <https://lists.centos.org/pipermail/centos-announce/2018-September/023047.ht…> Ansible 2.6.5: https://github.com/ansible/ansible/blob/v2.6.5/changelogs/CHANGELOG-v2.6.rst Cockpit 176: https://cockpit-project.org/blog/cockpit-176.html Updates included: +ansible-2.6.5-1.el7.noarch +cockpit-176-2.el7.centos.x86_64 +cockpit-bridge-176-2.el7.centos.x86_64 +cockpit-dashboard-176-2.el7.centos.x86_64 +cockpit-machines-ovirt-176-2.el7.centos.noarch +cockpit-storaged-176-2.el7.centos.noarch +cockpit-system-176-2.el7.centos.noarch +cockpit-ws-176-2.el7.centos.x86_64 +firewalld-0.4.4.4-15.el7_5.noarch +firewalld-filesystem-0.4.4.4-15.el7_5.noarch +initscripts-9.49.41-1.el7_5.2.x86_64 +ipa-client-4.5.4-10.el7.centos.4.4.x86_64 +ipa-client-common-4.5.4-10.el7.centos.4.4.noarch +ipa-common-4.5.4-10.el7.centos.4.4.noarch +kernel-3.10.0-862.14.4.el7.x86_64 +kernel-tools-3.10.0-862.14.4.el7.x86_64 +kernel-tools-libs-3.10.0-862.14.4.el7.x86_64 +kexec-tools-2.0.15-13.el7_5.2.x86_64 +libgudev1-219-57.el7_5.3.x86_64 +libipa_hbac-1.16.0-19.el7_5.8.x86_64 +libsss_autofs-1.16.0-19.el7_5.8.x86_64 +libsss_certmap-1.16.0-19.el7_5.8.x86_64 +libsss_idmap-1.16.0-19.el7_5.8.x86_64 +libsss_nss_idmap-1.16.0-19.el7_5.8.x86_64 +libsss_sudo-1.16.0-19.el7_5.8.x86_64 +libvirt-3.9.0-14.el7_5.8.x86_64 +libvirt-client-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-config-network-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-config-nwfilter-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-interface-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-lxc-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-network-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-nodedev-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-nwfilter-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-qemu-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-secret-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-core-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-disk-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-iscsi-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-logical-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-mpath-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-rbd-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-driver-storage-scsi-3.9.0-14.el7_5.8.x86_64 +libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64 +libvirt-libs-3.9.0-14.el7_5.8.x86_64 +libvirt-lock-sanlock-3.9.0-14.el7_5.8.x86_64 +microcode_ctl-2.1-29.16.el7_5.x86_64 +mokutil-12-2.el7.x86_64 +nss-3.36.0-7.el7_5.x86_64 +nss-sysinit-3.36.0-7.el7_5.x86_64 +nss-tools-3.36.0-7.el7_5.x86_64 +ovirt-node-ng-image-update-placeholder-4.2.6.2-1.el7.noarch +ovirt-node-ng-nodectl-4.2.0-0.20181003.0.el7.noarch +ovirt-release-host-node-4.2.6.2-1.el7.noarch +ovirt-release42-4.2.6.2-1.el7.noarch +python-firewall-0.4.4.4-15.el7_5.noarch +python-libipa_hbac-1.16.0-19.el7_5.8.x86_64 +python-perf-3.10.0-862.14.4.el7.x86_64 +python-sss-murmur-1.16.0-19.el7_5.8.x86_64 +python-sssdconfig-1.16.0-19.el7_5.8.noarch +python2-ipaclient-4.5.4-10.el7.centos.4.4.noarch +python2-ipalib-4.5.4-10.el7.centos.4.4.noarch +shim-x64-12-2.el7.x86_64 +spice-server-0.14.0-2.el7_5.5.x86_64 +sssd-1.16.0-19.el7_5.8.x86_64 +sssd-ad-1.16.0-19.el7_5.8.x86_64 +sssd-client-1.16.0-19.el7_5.8.x86_64 +sssd-common-1.16.0-19.el7_5.8.x86_64 +sssd-common-pac-1.16.0-19.el7_5.8.x86_64 +sssd-ipa-1.16.0-19.el7_5.8.x86_64 +sssd-krb5-1.16.0-19.el7_5.8.x86_64 +sssd-krb5-common-1.16.0-19.el7_5.8.x86_64 +sssd-ldap-1.16.0-19.el7_5.8.x86_64 +sssd-proxy-1.16.0-19.el7_5.8.x86_64 +systemd-219-57.el7_5.3.x86_64 +systemd-libs-219-57.el7_5.3.x86_64 +systemd-python-219-57.el7_5.3.x86_64 +systemd-sysv-219-57.el7_5.3.x86_64 Thanks, [1] https://bugs.centos.org/view.php?id=15193 -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

5 7

Failed to lock byte 100 - when booting VM with attached CD
by Simon Vincent 05 Oct '18

05 Oct '18

I have found recently I can't boot any VMs which have a CD attached to it. I get the following error. VM Test is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2018-10-04T11:53:07.031875Z qemu-kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2: Failed to lock byte 100 2018-10-04T11:53:07.032264Z qemu-kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2: Failed to lock byte 100 2018-10-04T11:53:07.032285Z qemu-kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2: Failed to lock byte 100 Unexpected error in raw_apply_lock_bytes() at block/file-posix.c:642: 2018-10-04T11:53:07.032665Z qemu-kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2: Failed to lock byte 100. I have tried relaxing the permissions on the iSO NFS share and even removed the iSO domain and added a new one, but I still get the problem. Regards Simon

2 1

iso domain don't list available images
by Nathanaël Blanchet 04 Oct '18

04 Oct '18

Hello, I detached an existing iso domain from an other ovirt instance and attached it to on a fresh 4.2 install, but no images are available. Is it a known bug? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 2

Unable to mount CephFS as POSIX Compliant FS
by ryan.terpstra＠gmail.com 04 Oct '18

04 Oct '18

I have a ceph filesystem that I can manually mount on my ovirt host. [root@ovirt121 ~]# mount -t ceph ceph01:/ /mnt -o name=admin,secret=<secret removed for security> [root@ovirt121 ~]# touch /mnt/test works great! Then I umount that filesystem and attempt to add storage domain in ovirt engine. Settings: Storage type: POSIX compliant FS Host to use: ovirt121 name: cephdata Path: ceph01:/ vfs type: ceph mount options: name=admin,secret=<secret removed for security> In the oVirt web UI I get a "General Exception" error. On the host I see this in vdsm.log: 2018-10-03 23:47:58,165+0000 INFO (jsonrpc/6) [vdsm.api] START connectStorageServer(domType=6, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'mnt_options': u'name=admin,secret=AQDJI7RbS4Z2GhAAhlyWUvX7wtPNzO6n5vqjsQ==', u'id': u'00000000-0000-0000-0000-000000000000', u'connection': u'ceph01:/', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'vfs_type': u'ceph', u'password': '********', u'port': u''}], options=None) from=::ffff:10.78.7.221,54910, flow_id=ba106a2d-e204-4da7-acc7-29b70c3ff759, task_id=b5e0c87c-8838-4b49-8590-11382a02d67f (api:46) 2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.StorageServer.MountConnection] Creating directory u'/rhev/data-center/mnt/ceph01:_' (storageServer:167) 2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.fileUtils] Creating directory: /rhev/data-center/mnt/ceph01:_ mode: None (fileUtils:197) 2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.Mount] mounting ceph01:/ at /rhev/data-center/mnt/ceph01:_ (mount:204) 2018-10-03 23:47:58,218+0000 ERROR (jsonrpc/6) [storage.HSM] Could not connect to storageServer (hsm:2415) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2412, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 183, in connect self.getMountObj().getRecord().fs_file) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 253, in getRecord (self.fs_spec, self.fs_file)) OSError: [Errno 2] Mount of `ceph01:/` at `/rhev/data-center/mnt/ceph01:_` does not exist 2018-10-03 23:47:58,218+0000 INFO (jsonrpc/6) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'status': 100, 'id': u'00000000-0000-0000-0000-000000000000'}]} from=::ffff:10.78.7.221,54910, flow_id=ba106a2d-e204-4da7-acc7-29b70c3ff759, task_id=b5e0c87c-8838-4b49-8590-11382a02d67f (api:52) However, if i run "monut" or "cat /proc/mounts" I can see the cephfs was properly mounted, I can even touch files. [root@ovirt121 ~]# touch /rhev/data-center/mnt/ceph01\:_/ceph_ovirt_test [root@ovirt121 ~]# [root@ovirt121 ~]# cat /proc/mounts <...bunch of mounts...> 10.78.71.1:/ /rhev/data-center/mnt/ceph01:_ ceph rw,relatime,name=admin,secret=<hidden>,acl,wsize=16777216 0 0 [root@ovirt121 ~]# Any thoughts? oVirt version is 4.2.6.4-1.el7, running on CentOS 7 18.05.

3 3

no space left to upgrade hosted-engine
by Nathanaël Blanchet 04 Oct '18

04 Oct '18

I've deployed and hosted-engine with the hosted-engine provided appliance. When runing hosted-engine --upgrade-appliance on one host, it tells me "If your engine VM is already based on el7 you can also simply upgrade the engine there." So I launched a yum update on the hosted-engine, but it complains there is no space left on / [root@infra ~]# df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/vda3 6,2G 6,2G 20K 100% / devtmpfs 7,8G 0 7,8G 0% /dev tmpfs 7,8G 4,0K 7,8G 1% /dev/shm tmpfs 7,8G 9,0M 7,8G 1% /run tmpfs 7,8G 0 7,8G 0% /sys/fs/cgroup /dev/mapper/ovirt-home 1014M 33M 982M 4% /home /dev/mapper/ovirt-tmp 2,0G 33M 2,0G 2% /tmp /dev/vda1 1014M 162M 853M 16% /boot /dev/mapper/ovirt-var 20G 631M 20G 4% /var /dev/mapper/ovirt-log 10G 58M 10G 1% /var/log /dev/mapper/ovirt-audit 1014M 59M 956M 6% /var/log/audit tmpfs 1,6G 0 1,6G 0% /run/user/0 Is the only way is to deploy the new appliance? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 2

ODL and Openstack issue
by Soujanya Bargavi 04 Oct '18

04 Oct '18

I am running one controller and one compute node. Controller node is running both ODL and OpenStack. I created tenants, underthem i created networks and launched instances on them. All is see on ODL web GUI is 3 swithces, and I guess those are br-int and br-ex of controller and br-int of compute and the links are missing too. Is there anyway where I can see my whole OpenStack https://goo.gl/6CgufL topology on ODL GUI with the links?

1 0

Reg: Enabling Nested virtualization.
by syedquadeer＠ctel.in 04 Oct '18

04 Oct '18

Dear Team, Need help to enable nested virtualization in Ovirt VM's. As when I checked my cpu info and kvm acceleration info, it is giving below output. # kvm-ok INFO: Your CPU does not support KVM extensions KVM acceleration can NOT be used # cat /sys/module/kvm/parameters/nested cat: /sys/module/kvm/parameters/nested: No such file or directory # virsh -r list Id Name State ---------------------------------------------------- Thanks & Regards, Syed Abdul Qadeer. 7660022818.

2 1

Re: Need to register with oVirt community
by Evgheni Dereveanchin 04 Oct '18

04 Oct '18

Hi Manish, If you want to deploy oVirt and use it, please follow our installation guide: https://www.ovirt.org/documentation/install-guide/Installation_Guide/ If you'd like to contribute to the project there's several ways like submitting patches to the code or helping with documentation or infra: https://www.ovirt.org/community/ Please let me know if you have any further questions. On Wed, Oct 3, 2018 at 10:12 AM Manish Shukla <Manish.Shukla(a)locuz.com> wrote: > Dear Team, > > > > Please suggest me how to joined community. I would like to be an > implementation of the oVirt infrastructure. > > > > > > > > > > Thanks & Regards, > > > > Manish SHUKLA > > > _______________________________________________ > 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/2NMDN6K643COC… > -- Regards, Evgheni Dereveanchin

1 0

[ANN] oVirt 4.2.7 Second Release Candidate is now available
by Sandro Bonazzola 04 Oct '18

04 Oct '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.7 Second Release Candidate, as of October 4th, 2018. This update is a release candidate of the seventh in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later * CentOS Linux (or similar) 7.5 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] Additional Resources: * Read more about the oVirt 4.2.7 release highlights: http://www.ovirt.org/release/4.2.7/ * 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] http://www.ovirt.org/release/4.2.7/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0

lost connection to hosted engine
by Artem Tambovskiy 04 Oct '18

04 Oct '18

Hi, Just run into the issue during cluster upgrade from 4.24 to 4.2.6.1. I'm running small cluster with 2 hosts and gluster storage. Once I upgraded one of the hosts to 4.2.6.1 something went wrong (looks like it tried to start HE instance) and I can't connect to hosted-engine any longer. As I can see HostedEngine is still running on the second host (and another yet 7 VM's) , but I can't stop it. ovirt-ha-agent and ovirt-ha-broker are failing to start. hosted-engine --vm-status gives nothing but error message "The hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable." ps -ef shows plenty of vdsm processes in defunc state thats probably the reason why agent and brocker can't start. Just wondering that is the good way to start problem resolution here to minimize downtime for running VM's? Restart vdsm and try again restarting agent and broker or just reboot the whole host? Regards, Artem

2 1

hosted-engine --deploy erorr
by mustafa.taha.mu95＠gmail.com 04 Oct '18

04 Oct '18

i configuer ovirt-self host and then i clear it by this command : /usr/sbin/ovirt-hosted-engine-cleanup then i want to re-deploy the selfhost by this error appear : [root@ovirtnode44 ~]# hosted-engine --deploy [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and create a local VM with a running engine. The locally running engine will be used to configure a storage domain and create a VM there. At the end the disk of the local VM will be moved to the shared storage. Are you sure you want to continue? (Yes, No)[Yes]: It has been detected that this program is executed through an SSH connection without using screen. Continuing with the installation may lead to broken installation if the network connection fails. It is highly recommended to abort the installation and run it inside a screen session using command "screen". Do you want to continue anyway? (Yes, No)[No]: yes Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20181004025609-bzthh6.log Version: otopi-1.7.8 (otopi-1.7.8-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- --== HOST NETWORK CONFIGURATION ==-- [ INFO ] Bridge ovirtmgmt already created Please indicate a pingable gateway IP address [192.168.3.2]: [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [Detecting interface on existing management bridge] [ INFO ] ok: [localhost] [ INFO ] TASK [Get all active network interfaces] [ INFO ] TASK [Filter bonds with bad naming] [ INFO ] TASK [Generate output list] [ INFO ] ok: [localhost] Please indicate a nic to set ovirtmgmt bridge on: (enp24s0f0) [enp24s0f0]: --== VM CONFIGURATION ==-- If you want to deploy with a custom engine appliance image, please specify the path to the OVA archive you would like to use (leave it empty to skip, the setup will use ovirt-engine-appliance rpm installing it if missing): [ INFO ] Detecting host timezone. Please provide the FQDN you would like to use for the engine appliance. Note: This will be the FQDN of the engine VM you are now going to launch, it should not point to the base host or to any other existing machine. Engine VM FQDN: []: ovirtengine.exalt.ps Please provide the domain name you would like to use for the engine appliance. Engine VM domain: [exalt.ps] Enter root password that will be used for the engine appliance: Confirm appliance root password: Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip): [WARNING] Skipping appliance root ssh public key Do you want to enable ssh access for the root user (yes, no, without-password) [yes]: Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]: Please specify the memory size of the VM in MB (Defaults to appliance OVF value): [16384]: You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:03:a8:09]: How should the engine VM network be configured (DHCP, Static)[DHCP]? Static Please enter the IP address to be used for the engine VM [192.168.0.1]: 192.168.200.45 [ INFO ] The engine VM will be configured to use 192.168.200.45/16 Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM Engine VM DNS (leave it empty to skip) [192.168.200.6]: Add lines for the appliance itself and for this host to /etc/hosts on the engine VM? Note: ensuring that this host could resolve the engine VM hostname is still up to you (Yes, No)[No] --== HOSTED ENGINE CONFIGURATION ==-- Please provide the name of the SMTP server through which we will send notifications [localhost]: Please provide the TCP port number of the SMTP server [25]: Please provide the email address from which notifications will be sent [root@localhost]: Please provide a comma-separated list of email addresses which will get notifications [root@localhost]: Enter engine admin password: Confirm engine admin password: [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Cleaning previous attempts [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [Stop libvirt service] [ INFO ] ok: [localhost] [ INFO ] TASK [Drop vdsm config statements] [ INFO ] TASK [Restore initial abrt config files] [ INFO ] TASK [Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [Stop and disable services] [ INFO ] TASK [Start libvirt] [ INFO ] changed: [localhost] [ INFO ] TASK [Check for leftover local Hosted Engine VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Destroy leftover local Hosted Engine VM] [ INFO ] skipping: [localhost] [ INFO ] TASK [Check for leftover defined local Hosted Engine VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Undefine leftover local engine VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Check for leftover defined Hosted Engine VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Undefine leftover engine VM] [ INFO ] skipping: [localhost] [ INFO ] TASK [Remove eventually entries for the local VM from known_hosts file] [ INFO ] changed: [localhost] [ INFO ] Starting local VM [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [Start libvirt] [ INFO ] ok: [localhost] [ INFO ] TASK [Activate default libvirt network] [ INFO ] ok: [localhost] [ INFO ] TASK [Get libvirt interfaces] [ INFO ] ok: [localhost] [ INFO ] TASK [Get routing rules] [ INFO ] changed: [localhost] [ INFO ] TASK [Save bridge name] [ INFO ] ok: [localhost] [ INFO ] TASK [Wait for the bridge to appear on the host] [ INFO ] changed: [localhost] [ INFO ] TASK [Refresh network facts] [ INFO ] skipping: [localhost] [ INFO ] TASK [Prepare CIDR for virbr0] [ INFO ] ok: [localhost] [ INFO ] TASK [Add outbound route rules] [ INFO ] skipping: [localhost] [ INFO ] TASK [Add inbound route rules] [ INFO ] skipping: [localhost] [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Avoid localhost] [ INFO ] skipping: [localhost] [ INFO ] TASK [Get host address resolution] [ INFO ] changed: [localhost] [ INFO ] TASK [Check address resolution] [ INFO ] skipping: [localhost] [ INFO ] TASK [Parse host address resolution] [ INFO ] ok: [localhost] [ INFO ] TASK [Ensure host address resolves locally] [ INFO ] skipping: [localhost] [ INFO ] TASK [Get target address from selected interface] [ INFO ] ok: [localhost] [ INFO ] TASK [Check the resolved address resolves on the selected interface] [ INFO ] skipping: [localhost] [ INFO ] TASK [Check for alias] [ INFO ] changed: [localhost] [ INFO ] TASK [Ensure the resolved address resolves only on the selected interface] [ INFO ] skipping: [localhost] [ INFO ] TASK [Avoid localhost] [ INFO ] skipping: [localhost] [ INFO ] TASK [Get engine FQDN resolution] [ INFO ] changed: [localhost] [ INFO ] TASK [Check engine FQDN resolution] [ INFO ] skipping: [localhost] [ INFO ] TASK [Parse engine FQDN resolution] [ INFO ] ok: [localhost] [ INFO ] TASK [Ensure engine FQDN doesn't resolve locally] [ INFO ] skipping: [localhost] [ INFO ] TASK [Check http/https proxy] [ INFO ] TASK [Register the engine FQDN as a host] [ INFO ] changed: [localhost] [ INFO ] TASK [Create directory for local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Set local vm dir path] [ INFO ] ok: [localhost] [ INFO ] TASK [Fix local VM directory permission] [ INFO ] changed: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Install ovirt-engine-appliance rpm] [ INFO ] ok: [localhost] [ INFO ] TASK [Parse appliance configuration for path] [ INFO ] changed: [localhost] [ INFO ] TASK [Parse appliance configuration for sha1sum] [ INFO ] changed: [localhost] [ INFO ] TASK [Get OVA path] [ INFO ] ok: [localhost] [ INFO ] TASK [Compute sha1sum] [ INFO ] ok: [localhost] [ INFO ] TASK [Compare sha1sum] [ INFO ] skipping: [localhost] [ INFO ] TASK [Register appliance PATH] [ INFO ] skipping: [localhost] [ INFO ] TASK [Extract appliance to local VM directory] [ INFO ] changed: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [Get appliance disk size] [ INFO ] changed: [localhost] [ INFO ] TASK [Parse qemu-img output] [ INFO ] ok: [localhost] [ INFO ] TASK [Create cloud init user-data and meta-data files] [ INFO ] TASK [Create ISO disk] [ INFO ] changed: [localhost] [ INFO ] TASK [Create local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Get local VM IP] [ INFO ] changed: [localhost] [ INFO ] TASK [Remove eventually entries for the local VM from /etc/hosts] [ INFO ] changed: [localhost] [ INFO ] TASK [Create an entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [Wait for SSH to restart on the local VM] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [ovirtengine.exalt.ps] [ INFO ] TASK [Wait for the local VM] [ INFO ] ok: [ovirtengine.exalt.ps] [ INFO ] TASK [Add an entry for this host on /etc/hosts on the local VM] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Set FQDN] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Force the local VM FQDN to temporary resolve on the natted network address] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Restore sshd reverse DNS lookups] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Generate an answer file for engine-setup] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Include before engine-setup custom tasks files for the engine VM] [ INFO ] TASK [Execute engine-setup] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Include after engine-setup custom tasks files for the engine VM] [ INFO ] TASK [Configure LibgfApi support] [ INFO ] skipping: [ovirtengine.exalt.ps] [ INFO ] TASK [Restart ovirt-engine service for LibgfApi support] [ INFO ] skipping: [ovirtengine.exalt.ps] [ INFO ] TASK [Mask cloud-init services to speed up future boot] [ INFO ] TASK [Clean up bootstrap answer file] [ INFO ] changed: [ovirtengine.exalt.ps] [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [Wait for ovirt-engine service to start] [ INFO ] ok: [localhost] [ INFO ] TASK [Detect VLAN ID] [ INFO ] changed: [localhost] [ INFO ] TASK [Set Engine public key as authorized key without validating the TLS/SSL certificates] [ INFO ] changed: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [Enable GlusterFS at cluster level] [ INFO ] skipping: [localhost] [ INFO ] TASK [Set VLAN ID at datacenter level] [ INFO ] skipping: [localhost] [ INFO ] TASK [Force host-deploy in offline mode] [ INFO ] ok: [localhost] [ INFO ] TASK [Add host] [ INFO ] changed: [localhost] [ INFO ] TASK [Wait for the host to be up] [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [Give the vm time to flush dirty buffers] [ INFO ] TASK [Copy engine logs] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [Set local_vm_disk_path] [ INFO ] skipping: [localhost] [ INFO ] TASK [Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [Copy engine logs] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20181004031555.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20181004025609-bzthh6.log

3 2

ISCSI domain won't attach
by Vincent Royer 03 Oct '18

03 Oct '18

I setup an iscsi domain in hopes of moving away from NFS. I created a new logical network for this on a storage vlan. both hosts and storage server grabbed a good IP on this vlan. ISCSI Domain connected ok and I started moving disks over from the NFS domain. Transfers were completing so I let it do its thing. This morning, after the transfers completed, three things occurred in quick succession: 1. Affinity Rules Enforcement Manager started. 2. Invalid status on Data Center. Setting status to Non Responsive. 3. Storage Pool Manager runs on Host brian.xxx.net (Address: brian.xxx.net) Data Center. 4. Storage Domain domiscsi was deactivated by system because it's not visible by any of the hosts. Try to attach it again and it fails. Have another coffee and try to attach again to get logs, and this time it attaches just fine. domain disconnected vdsm log: https://pastebin.com/pfGerEE5 Successful attach operation vdsm log: https://pastebin.com/c0U07QXg host Brian can't seem to keep the storage domain https://pastebin.com/ySAqiqA3 both hosts seem to have connected sessions when looking from the storage server: [image: image.png] Seems like it might be one problematic host, because engine keeps trying to reboot it to get it to reconnect to the storage domain. Maybe after a few tries it just deems the domain is bad. Not sure! Any help is appreciated!

2 2

ovirt-ha-agent failed to start
by mustafa.taha.mu95＠gmail.com 03 Oct '18

03 Oct '18

hi i try to start ovirt-ha-agent in my self-host machine but it does not work if i run journalctl -xe it shows : Oct 03 04:33:24 ovirtnode44.exalt.ps ovirt-ha-agent[81909]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary mo Oct 03 04:33:24 ovirtnode44.exalt.ps ovirt-ha-agent[81909]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent return action(he) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_prope return he.start_monitoring() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 413, in sta self._initialize_broker() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 535, in _in m.get('options', {})) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 83, in start_mon .format(type, options, e)) RequestError: Failed to start monitor ping, options {'addr': '192.168.3.2'}: [Errno 2] No such file or di Oct 03 04:33:24 ovirtnode44.exalt.ps ovirt-ha-agent[81909]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent anybody have idea ?

2 1