- Users - oVirt List Archives

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

clean up a fc lun to reuse it
by Nathanaël Blanchet 03 Oct '18

03 Oct '18

Hi all, I tried to install the Hosted-Engine on a FC lun, and the first time, it failed at the end because of a sanlock issue. So I fixed it and the re-deoployed from scratch until this new issue [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Physical device initialization failed. Please check that the device is empty and accessible by the host.]". HTTP response code is 400. Before, I found that the lun [2] was used: [ INFO ] ok: [localhost] The following luns have been found on the requested target: [1] 36006016039a142001792ac5b1b9e513a 1024GiB DGC VRAID status: free, paths: 8 active [2] 36006016039a142006755b25b7505d26b 100GiB DGC VRAID status: used, paths: 8 active So it was the good explanation for the failure. Following the admin guide, I cleaned up the lun using |# dd if=/dev/zero of=/dev/mapper/||36006016039a142006755b25b7505d26b bs=1M count=200 oflag=direct| And re-deployed it until it complains the device was not empty despite of before. The script still reported that the status of the lun was "used" Finally, I rebooted the host, and that time the script considered the lun status as free. So there is somewhere a bit of code into the ansible script that keeps the old status of the lun before dd, until rebooting. Is there an other way to refresh the lun status after dd ? 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

Adding hosts to oVirt-Engine
by manish.shukla＠locuz.com 03 Oct '18

03 Oct '18

Below error i am getting while adding same host in to Engine. Error log on Engine. Kindlly Suggest 2018-10-03 12:02:32,271+05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = 192.168.0.28, VdsIdAndVdsVDSCommandParametersBase:{hostId='0fb0f4ac-162e-4cfd-ab15-641c04861d2f', vds='Host[192.168.0.28,0fb0f4ac-162e-4cfd-ab15-641c04861d2f]'})' execution failed: java.net.ConnectException: Connection refused 2018-10-03 12:02:33,342+05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /192.168.0.28 2018-10-03 12:02:33,345+05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Command 'GetAllVmStatsVDSCommand(HostName = 192.168.0.28, VdsIdVDSCommandParametersBase:{hostId='0fb0f4ac-162e-4cfd-ab15-641c04861d2f'})' execution failed: java.net.ConnectException: Connection refused 2018-10-03 12:02:33,345+05 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Failed to fetch vms info for host '192.168.0.28' - skipping VMs monitoring. 2018-10-03 12:02:35,283+05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /192.168.0.28 2018-10-03 12:02:35,285+05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [] Unable to RefreshCapabilities: ConnectException: Connection refused 2018-10-03 12:02:35,288+05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-32) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = 192.168.0.28, VdsIdAndVdsVDSCommandParametersBase:{hostId='0fb0f4ac-162e-4cfd-ab15-641c04861d2f', vds='Host[192.168.0.28,0fb0f4ac-162e-4cfd-ab15-641c04861d2f]'})' execution failed: java.net.ConnectException: Connection refused

3 4

Need to register with oVirt community
by Manish Shukla 03 Oct '18

03 Oct '18

Dear Team, Please suggest me how to joined community. I would like to be an implementation of the oVirt infrastructure. Thanks & Regards, Manish SHUKLA

1 0

P2V Tools for oVirt
by Vinícius Ferrão 03 Oct '18

03 Oct '18

Hello, I’m looking for a P2V tool to migrate some physical machine to oVirt. I’m specifically worried about database servers that must be made virtual. What are the recommendations and tested tools? Thanks in advance,

1 0

[OT] transferring kvm raw mage from filesystem to lvm based
by Gianluca Cecchi 02 Oct '18

02 Oct '18

Hello, I have a windows 7 VM that is composed by a raw disk on filesystem on Fedora 28. I would like to transfer this VM to another environment, always based on same version of Fedora 28, but where the storage is configured in virt-manager as lvm based, so similar to what happens in oVirt block based storage domains. I'm trying to figure how to transfer the image. I presume I can create a new LV and then leave some bytes for the LVM header into the created LV and then make a sort of dd with offset? Anyone has any hint? Thanks in advance, Gianluca

3 3

iSCSI multipath with Dell Compellent
by Bernhard Dick 02 Oct '18

02 Oct '18

Hi, I'm trying to achieve iSCSI multipathing with an Dell Compellent SC4020 array. As the Dell Array does not work as an ALUA system it displays available LUNs only on the currently active system (here is a good description that I found: https://niktips.wordpress.com/2016/05/16/dell-compellent-is-not-an-alua-sto… ). As a result I cannot add the currently non-active controller to an iSCSI-Bond (as it does not present the LUNs to oVirt) and so the path to the second controller will not be up. Is there any way to solve this? Regards Bernhard

2 4

Change network interface for hosted engine iSCSI connection
by Bernhard Dick 02 Oct '18

02 Oct '18

Hi, after I changed the network configuration of one of my hosted engine hosts in oVirt I am no longer able to run the ha-daemon on the host. When I run hosted-engine --connect-storage on this host I get the following error: vdsm.client.TimeoutError: Request StoragePool.connectStorageServer with args {'connectionParams': [{'netIfaceName': 'ens1f1', 'port': '3260', 'connection': '192.168.1.1', 'iqn': 'iqn.2002-03.com.compellent:5000 d...', 'user': '', 'tpgt': '0', 'ifaceName': 'ens1f1', 'password': '', 'id': 'cd5fa13f-fbb7-4cc6-a094-4b280dc7b514'}], 'storagepoolID': '00000000-0000-0000-0000-000000000000', 'domainType': 3} timed out after 60 seconds ens1f1 is the network card that has been used earlier for iSCSI, now it should connect via ens1f0. Is there a way to update this configuration for the host? Regards Bernhard

2 2

oVirt Metrics Store installation
by Markus Schaufler 02 Oct '18

02 Oct '18

Hi! I'm having trouble installing the oVirt Metrics Store following this https://www.ovirt.org/develop/release-management/features/metrics/metrics-s… respectively this guide https://www.ovirt.org/develop/release-management/features/metrics/setting-u… When executing the test script ANSIBLE_LOG_PATH=/tmp/ansible-prereq.log ansible-playbook -vvv -e @/root/vars.yaml -i /root/ansible-inventory-origin-39-aio playbooks/prerequisites.yml following error occurs: Using module file /usr/lib/python2.7/site-packages/ansible/modules/packaging/os/yum.py <localhost> EXEC /bin/sh -c '/usr/bin/python && sleep 0' fatal: [localhost]: FAILED! => { "attempts": 3, "changed": false, "invocation": { "module_args": { "allow_downgrade": false, "bugfix": false, "conf_file": null, "disable_gpg_check": false, "disable_plugin": [], "disablerepo": null, "enable_plugin": [], "enablerepo": null, "exclude": null, "install_repoquery": true, "installroot": "/", "list": null, "name": [ "docker", "atomic", "skopeo" ], "security": false, "skip_broken": false, "state": "present", "update_cache": false, "update_only": false, "validate_certs": true } }, "msg": "Error: Package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64 (centosplus)\n Requires: python-docker-py >= 1.7.2-1\n Available: docker-python-1.4.0-115.el7.x86_64 (centosplus)\n python-docker-py = 1.4.0-115.el7\n Available: python-docker-py-1.10.6-3.el7.noarch (centosplus)\n python-docker-py = 1.10.6-3.el7\n Available: python-docker-py-1.10.6-4.el7.noarch (centosplus)\n python-docker-py = 1.10.6-4.el7\n Available: python2-docker-2.4.2-1.2.el7.noarch (centos-openshift-origin-testing-cbs)\n python-docker-py = 2.4.2-1.2.el7\n Installed: python2-docker-3.3.0-1.el7.noarch (@centos-openshift-origin-testing)\n Not found\n", "rc": 1, "results": [ "2:docker-1.13.1-74.git6e3bb8e.el7.centos.x86_64 providing docker is already installed", "Loaded plugins: fastestmirror\nLoading mirror speeds from cached hostfile\nResolving Dependencies\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n--> Processing Dependency: runc for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: python-dateutil for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: ostree for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: gomtree for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n---> Package skopeo.x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos will be installed\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n-- > Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n---> Package gomtree.x86_64 0:0.5.0-0.2.git16da0f8.el7 will be installed\n---> Package ostree.x86_64 0:2018.5-1.el7 will be installed\n--> Processing Dependency: libarchive.so.13()(64bit) for package: ostree-2018.5-1.el7.x86_64\n---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed\n---> Package runc.x86_64 0:1.0.0-37.rc5.dev.gitad0f525.el7 will be installed\n--> Processing Dependency: criu for package: runc-1.0.0-37.rc5.dev.gitad0f525.el7.x86_64\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7. noarch which is already installed\n---> Package criu.x86_64 0:3.5-4.el7 will be installed\n--> Processing Dependency: libprotobuf-c.so.1(LIBPROTOBUF_C_1.0.0)(64bit) for package: criu-3.5-4.el7.x86_64\n--> Processing Dependency: libprotobuf-c.so.1()(64bit) for package: criu-3.5-4.el7.x86_64\n--> Processing Dependency: libnet.so.1()(64bit) for package: criu-3.5-4.el7.x86_64\n---> Package libarchive.x86_64 0:3.1.2-10.el7_2 will be installed\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n---> Package libnet.x86_64 0:1.1.6-7.el7 will be installed\n---> Package protobuf-c.x86_64 0:1.0.2-3.el7 will be installed\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the pro blem\n You could try running: rpm -Va --nofiles --nodigest\n" ] } PLAY RECAP ************************************************************************************************************************************************************ localhost : ok=75 changed=6 unreachable=0 failed=1 I already already found out that there might be a bug in some older versions of openshift/ansible but the recent versions should be fine. Thanks for any suggestions on this!

2 1