- Users - oVirt List Archives

Re: Ovirt OVN help needed
by Strahil 10 Jan '20

10 Jan '20

Hi Dominik, Thanks for your reply. On ovirt1 I got the following: [root@ovirt1 openvswitch]# less ovn-controller.log-20191216.gz 2019-12-15T01:49:02.988Z|00032|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2019-12-16T01:18:02.114Z|00033|vlog|INFO|closing log file ovn-controller.log-20191216.gz (END) Same is on the other node: [root@ovirt2 openvswitch]# less ovn-controller.log-20191216.gz 2019-12-15T01:26:03.477Z|00028|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2019-12-16T01:30:01.718Z|00029|vlog|INFO|closing log file ovn-controller.log-20191216.gz (END) The strange thing is that the geneve tunnels are there: [root@ovirt1 ~]# ovs-vsctl show c0e938f1-b5b5-4d5a-9cda-29dae2986f29 Bridge br-int fail_mode: secure Port "ovn-25cc77-0" Interface "ovn-25cc77-0" type: geneve options: {csum="true", key=flow, remote_ip="192.168.1.64"} Port "ovn-566849-0" Interface "ovn-566849-0" type: geneve options: {csum="true", key=flow, remote_ip="192.168.1.41"} Port br-int Interface br-int type: internal Port "vnet2" Interface "vnet2" ovs_version: "2.11.0" [root@ovirt1 ~]# ovs-vsctl list ports ovs-vsctl: unknown table "ports" [root@ovirt1 ~]# ovs-vsctl list port _uuid : fbf40569-925e-4430-a7c5-c78d58979bbc bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {} fake_bridge : false interfaces : [3207c0cb-3000-40f2-a850-83548f76f090]lacp : [] mac : [] name : "vnet2" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : 8947f82d-a089-429b-8843-71371314cb52 bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {} fake_bridge : false interfaces : [ec6a6688-e5d6-4346-ac47-ece1b8379440]lacp : [] mac : [] name : br-int other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : 72d612be-853e-43e9-8f5c-ce66cef0bebe bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3(a)192.168.1.41"} fake_bridge : false interfaces : [a31574fe-515b-420b-859d-7f2ac729638f]lacp : [] mac : [] name : "ovn-566849-0" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : 2043a15f-ec39-4cc3-b875-7be00423dd7a bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {ovn-chassis-id="25cc77b3-046f-45c5-af0c-ffb2f77d73f1(a)192.168.1.64"} fake_bridge : false interfaces : [f9a9e3ff-070e-4044-b601-7f7394dc295f]lacp : [] mac : [] name : "ovn-25cc77-0" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] [root@ovirt1 ~]# [root@ovirt2 ~]# ovs-vsctl show 3dbab138-6b90-44c5-af05-b8a944c9bf20 Bridge br-int fail_mode: secure Port "ovn-baa019-0" Interface "ovn-baa019-0" type: geneve options: {csum="true", key=flow, remote_ip="192.168.1.90"} Port br-int Interface br-int type: internal Port "vnet5" Interface "vnet5" Port "ovn-566849-0" Interface "ovn-566849-0" type: geneve options: {csum="true", key=flow, remote_ip="192.168.1.41"} ovs_version: "2.11.0" [root@ovirt2 ~]# ovs-vsctl list port _uuid : 151e1188-f07a-4750-a620-392a08e7e7fe bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {ovn-chassis-id="baa0199e-d1a4-484c-af13-a41bcad19dbc(a)192.168.1.90"} fake_bridge : false interfaces : [4d4bc12a-609a-4917-b839-d4f652acdc33]lacp : [] mac : [] name : "ovn-baa019-0" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : 3a862f96-b3ec-46a9-bcf6-f385e5def410 bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {} fake_bridge : false interfaces : [777f2819-ca27-4890-8d2f-11349ca0d398]lacp : [] mac : [] name : br-int other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : a65109fa-f8b4-4670-8ae8-a2bd0bf6aba3 bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {ovn-chassis-id="5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3(a)192.168.1.41"} fake_bridge : false interfaces : [ed442077-f897-4e0b-97a1-a8051e9c3d56]lacp : [] mac : [] name : "ovn-566849-0" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] _uuid : a1622e6f-fcd0-4a8a-b259-ca4d0ccf1cd2 bond_active_slave : [] bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 cvlans : [] external_ids : {} fake_bridge : false interfaces : [ca368654-54f3-49d0-a71c-8894426df6bf]lacp : [] mac : [] name : "vnet5" other_config : {} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] [root@ovirt2 ~]# Best Regards, Strahil Nikolov On Dec 16, 2019 23:28, Dominik Holler <dholler(a)redhat.com> wrote: > > > > On Sat, Dec 14, 2019 at 11:36 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Dominik, >> >> yes I was looking for those settings. >> >> I have added again the external provider , but I guess the mess is even bigger as I made some stupid decisions (like removing 2 port groups :) without knowing what I'm doing) . >> Sadly I can't remove all packages on the engine and hosts and reinstall them from scratch. >> >> Pip fails to install the openstacksdk (centOS7 is not great for such tasks) on the engine and my lack of knowledge in OVN makes it even more difficult. >> >> So the symptoms are that 2 machines can communicate with each other only if they are on the same host ,while on separate - no communications is happening. >> > > This indicates that the tunnels between the hosts are not created. > Can you please check the /var/log/openvswitch/ovn-controller.log on both hosts for errors and warnings, or share parts of the files here? > If this does not point us to a problem, ovn has to be reconfigured. If possible, most easy way to do this would be to ensure that > ovirt-provider-ovn is the default network provider of the cluster of the hosts, put one host after another in maintance mode and reinstall. > > >> >> How I created the network via UI: >> >> 1. Networks - new >> 2. Fill in the name >> 3. Create on external provider >> 4. Network Port security -> disabled (even undefined does not work) >> 5.Connect to physical network -> ovirtmgmt >> >> >> I would be happy to learn more about OVN and thus I would like to make it work. >> >> Here is some info from the engine: >> >> [root@engine ~]# ovn-nbctl show >> switch 1288ed26-471c-4bc2-8a7d-4531f306f44c (ovirt-pxelan-2a88b2e0-d04b-4196-ad50-074501e4ed08) >> port c1eba112-5eed-4c04-b25c-d3dcfb934546 >> addresses: ["56:6f:5a:65:00:06"] >> port 8b52ab60-f474-4d51-b258-cb2e0a53c34a >> type: localnet >> addresses: ["unknown"] >> port b2753040-881b-487a-92a1-9721da749be4 >> addresses: ["56:6f:5a:65:00:09"] >> [root@engine ~]# ovn-sbctl show >> Chassis "5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3" >> hostname: "ovirt3.localdomain" >> Encap geneve >> ip: "192.168.1.41" >> options: {csum="true"} >> Chassis "baa0199e-d1a4-484c-af13-a41bcad19dbc" >> hostname: "ovirt1.localdomain" >> Encap geneve >> ip: "192.168.1.90" >> options: {csum="true"} >> Chassis "25cc77b3-046f-45c5-af0c-ffb2f77d73f1" >> hostname: "ovirt2.localdomain" >> Encap geneve >> ip: "192.168.1.64" >> options: {csum="true"} >> Port_Binding "b2753040-881b-487a-92a1-9721da749be4" >> Port_Binding &quo

4 8

is there any feature of load balancing for engine??
by yam yam 10 Jan '20

10 Jan '20

Hello, given massive oVirt environment, I think single engine looks too small to deal with all workloads. so, I want to make active-active engine cluster for distributing workloads. is it possible for an oVirt environment to be made up of multiple engines & DBs for load balancing?

3 4

Re: is there any feature of load balancing for engine??
by Strahil 10 Jan '20

10 Jan '20

It is not a good idea. If you think that the engine can't cope with the load, add a separate engine for the specific cluster(s). What is the count of Datacenters, Clusters, Hosts, VMs & Storage domains ? Best Regards, Strahil NikolovOn Jan 8, 2020 03:51, yam yam <hyunooudy(a)gmail.com> wrote: > > Hello, > > given massive oVirt environment, I think single engine looks too small to deal with all workloads. > so, I want to make active-active engine cluster for distributing workloads. > is it possible for an oVirt environment to be made up of multiple engines & DBs for load balancing? > _______________________________________________ > 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/XCO5DJS63YKC6…

2 1

Re: Setting up cockpit?
by Strahil 10 Jan '20

10 Jan '20

On Jan 9, 2020 18:58, m.skrzetuski(a)gmail.com wrote: > > Hello everyone, > > I'd like to get cockpit to work because currently when I click "Host Console" on a host I just get "connection refused". I checked and after the engine installation the cockpit service was not running. When I start it, it runs and answers on port 9090, however the SSL certificate is broken. > > - How do I auto enable cockpit on installation? systemctl enable --now cockpit.socket -H < destination server> > - How do I supply my own SSL certification to cockpit? Put them in /etc/cockpit/ws-certs.d/ Source:https://www.redhat.com/en/blog/linux-system-administration-managemen… > > Kind regards > Skrzetuski Best Regards, Strahil Nikolov

1 0

Re: After NAS crash, one VM will not start up, Cannot prepare illegal volume
by David Johnson 09 Jan '20

09 Jan '20

Thank you again. After updating legality to LEGAL, [root@mx-ovirt-host2 ~]# vdsm-client Volume getInfo storagepoolID=25cd9bfc-bab6-11e8-90f3-78acc0b47b4d storagedomainID=6e627364-5e0c-4250-ac95-7cd914d0175f imageID=4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6 volumeID=f8066c56-6db1-4605-8d7c-0739335d30b8 { "status": "OK", "lease": { "path": "/rhev/data-center/mnt/192.168.2.220: _mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease", "owners": [], "version": null, "offset": 0 }, "domain": "6e627364-5e0c-4250-ac95-7cd914d0175f", "capacity": "1503238553600", "voltype": "LEAF", "description": "", "parent": "a912e388-d80d-4f56-805b-ea5e2f35d741", "format": "COW", "generation": 0, "image": "4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6", "uuid": "f8066c56-6db1-4605-8d7c-0739335d30b8", "disktype": "DATA", "legality": "LEGAL", "mtime": "0", "apparentsize": "36440899584", "truesize": "16916186624", "type": "SPARSE", "children": [], "pool": "", "ctime": "1571669201" } Attempt to start the VM result are: Log excerpt: 2020-01-09 06:47:46,575-0600 INFO (vm/c5d0a42f) [storage.StorageDomain] Creating symlink from /rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6 to /var/run/vdsm/storage/6e627364-5e0c-4250-ac95-7cd914d0175f/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6 (fileSD:580) 2020-01-09 06:47:46,581-0600 INFO (vm/c5d0a42f) [vdsm.api] FINISH prepareImage return={'info': {'path': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', 'type': 'file'}, 'path': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', 'imgVolumesInfo': [{'domainID': '6e627364-5e0c-4250-ac95-7cd914d0175f', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/a912e388-d80d-4f56-805b-ea5e2f35d741', 'volumeID': u'a912e388-d80d-4f56-805b-ea5e2f35d741', 'leasePath': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/a912e388-d80d-4f56-805b-ea5e2f35d741.lease', 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6'}, {'domainID': '6e627364-5e0c-4250-ac95-7cd914d0175f', 'leaseOffset': 0, 'path': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', 'volumeID': u'f8066c56-6db1-4605-8d7c-0739335d30b8', 'leasePath': u'/rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6'}]} from=internal, task_id=865d2ff4-4e63-44dc-b8f8-9d93cad9892f (api:52) 2020-01-09 06:47:46,582-0600 INFO (vm/c5d0a42f) [vds] prepared volume path: /rhev/data-center/mnt/192.168.2.220:_mnt_ovirt-freenas/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8 (clientIF:497) 2020-01-09 06:47:46,583-0600 INFO (vm/c5d0a42f) [vdsm.api] START prepareImage(sdUUID='ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', spUUID='25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', imgUUID='60077050-6f99-41db-b280-446f018b104b', leafUUID='a67eb40c-e0a1-49cc-9179-bebb263d6e9c', allowIllegal=False) from=internal, task_id=08830292-0f75-4c5b-a411-695894c66475 (api:46) 2020-01-09 06:47:46,632-0600 INFO (vm/c5d0a42f) [vdsm.api] FINISH prepareImage error=Cannot prepare illegal volume: (u'a67eb40c-e0a1-49cc-9179-bebb263d6e9c',) from=internal, task_id=08830292-0f75-4c5b-a411-695894c66475 (api:50) 2020-01-09 06:47:46,632-0600 ERROR (vm/c5d0a42f) [storage.TaskManager.Task] (Task='08830292-0f75-4c5b-a411-695894c66475') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in prepareImage File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3187, in prepareImage raise se.prepareIllegalVolumeError(volUUID) prepareIllegalVolumeError: Cannot prepare illegal volume: (u'a67eb40c-e0a1-49cc-9179-bebb263d6e9c',) 2020-01-09 06:47:46,633-0600 INFO (vm/c5d0a42f) [storage.TaskManager.Task] (Task='08830292-0f75-4c5b-a411-695894c66475') aborting: Task is aborted: "Cannot prepare illegal volume: (u'a67eb40c-e0a1-49cc-9179-bebb263d6e9c',)" - code 227 (task:1181) 2020-01-09 06:47:46,634-0600 ERROR (vm/c5d0a42f) [storage.Dispatcher] FINISH prepareImage error=Cannot prepare illegal volume: (u'a67eb40c-e0a1-49cc-9179-bebb263d6e9c',) (dispatcher:82) 2020-01-09 06:47:46,634-0600 ERROR (vm/c5d0a42f) [virt.vm] (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') The vm start process failed (vm:949) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 878, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2798, in _run self._devices = self._make_devices() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2639, in _make_devices disk_objs = self._perform_host_local_adjustment() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2712, in _perform_host_local_adjustment self._preparePathsForDrives(disk_params) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 1023, in _preparePathsForDrives drive['path'] = self.cif.prepareVolumePath(drive, self.id) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 417, in prepareVolumePath raise vm.VolumeError(drive) VolumeError: Bad volume specification {'address': {'bus': '0', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '3'}, 'serial': '60077050-6f99-41db-b280-446f018b104b', 'index': 1, 'iface': 'scsi', 'apparentsize': '16842752', 'specParams': {}, 'cache': 'writeback', 'imageID': '60077050-6f99-41db-b280-446f018b104b', 'truesize': '2840576', 'type': 'disk', 'domainID': 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', 'reqsize': '0', 'format': 'cow', 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/60077050-6f99-41db-b280-446f018b104b/a67eb40c-e0a1-49cc-9179-bebb263d6e9c', 'propagateErrors': 'off', 'name': 'sdb', 'volumeID': 'a67eb40c-e0a1-49cc-9179-bebb263d6e9c', 'diskType': 'file', 'alias': 'ua-60077050-6f99-41db-b280-446f018b104b', 'discard': False} 2020-01-09 06:47:46,634-0600 INFO (vm/c5d0a42f) [virt.vm] (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') Changed state to Down: Bad volume specification {'address': {'bus': '0', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '3'}, 'serial': '60077050-6f99-41db-b280-446f018b104b', 'index': 1, 'iface': 'scsi', 'apparentsize': '16842752', 'specParams': {}, 'cache': 'writeback', 'imageID': '60077050-6f99-41db-b280-446f018b104b', 'truesize': '2840576', 'type': 'disk', 'domainID': 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', 'reqsize': '0', 'format': 'cow', 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/60077050-6f99-41db-b280-446f018b104b/a67eb40c-e0a1-49cc-9179-bebb263d6e9c', 'propagateErrors': 'off', 'name': 'sdb', 'volumeID': 'a67eb40c-e0a1-49cc-9179-bebb263d6e9c', 'diskType': 'file', 'alias': 'ua-60077050-6f99-41db-b280-446f018b104b', 'discard': False} (code=1) (vm:1689) 2 Regards, David Johnson Director of Development, Maxis Technology 844.696.2947 ext 702 (o) | 479.531.3590 (c) djohnson(a)maxistechnology.com [image: Maxis Techncology] <http://www.maxistechnology.com> www.maxistechnology.com *stay connected <http://www.linkedin.com/in/pojoguy>* On Thu, Jan 9, 2020 at 6:39 AM Benny Zlotnik <bzlotnik(a)redhat.com> wrote: > this `/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.meta` > > > You can see here[1] an example for updating volume metadata using > vdsm-client > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1409380#c3 > > On Thu, Jan 9, 2020 at 2:26 PM David Johnson <djohnson(a)maxistechnology.com> > wrote: > >> Thank you for the quick response. >> >> Where do I find that? >> >> Regards, >> David Johnson >> Director of Development, Maxis Technology >> 844.696.2947 ext 702 (o) | 479.531.3590 (c) >> djohnson(a)maxistechnology.com >> >> >> [image: Maxis Techncology] <http://www.maxistechnology.com> >> www.maxistechnology.com >> >> >> *stay connected <http://www.linkedin.com/in/pojoguy>* >> >> >> On Thu, Jan 9, 2020 at 6:24 AM Benny Zlotnik <bzlotnik(a)redhat.com> wrote: >> >>> Did you change the volume metadata to LEGAL on the storage as well? >>> >>> >>> On Thu, Jan 9, 2020 at 2:19 PM David Johnson < >>> djohnson(a)maxistechnology.com> wrote: >>> >>>> We had a drive in our NAS fail, but afterwards one of our VM's will not >>>> start. >>>> >>>> The boot drive on the VM is (so near as I can tell) the only drive >>>> affected. >>>> >>>> I confirmed that the disk images (active and snapshot) are both valid >>>> with qemu. >>>> >>>> I followed the instructions at >>>> https://www.canarytek.com/2017/07/02/Recover_oVirt_Illegal_Snapshots.html to >>>> identify the snapshot images that were marked "invalid" and marked them as >>>> valid. >>>> >>>> update images set imagestatus=1 where imagestatus=4; >>>> >>>> >>>> >>>> Log excerpt from attempt to start VM: >>>> 2020-01-09 02:18:44,908-0600 INFO (vm/c5d0a42f) [vdsm.api] START >>>> prepareImage(sdUUID='6e627364-5e0c-4250-ac95-7cd914d0175f', >>>> spUUID='25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', >>>> imgUUID='4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', >>>> leafUUID='f8066c56-6db1-4605-8d7c-0739335d30b8', allowIllegal=False) >>>> from=internal, task_id=26053225-6569-4b73-abdd-7d6c7e15d1e9 (api:46) >>>> 2020-01-09 02:18:44,931-0600 INFO (vm/c5d0a42f) [vdsm.api] FINISH >>>> prepareImage error=Cannot prepare illegal volume: >>>> (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) from=internal, >>>> task_id=26053225-6569-4b73-abdd-7d6c7e15d1e9 (api:50) >>>> 2020-01-09 02:18:44,932-0600 ERROR (vm/c5d0a42f) >>>> [storage.TaskManager.Task] (Task='26053225-6569-4b73-abdd-7d6c7e15d1e9') >>>> Unexpected error (task:875) >>>> Traceback (most recent call last): >>>> File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line >>>> 882, in _run >>>> return fn(*args, **kargs) >>>> File "<string>", line 2, in prepareImage >>>> File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, >>>> in method >>>> ret = func(*args, **kwargs) >>>> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line >>>> 3187, in prepareImage >>>> raise se.prepareIllegalVolumeError(volUUID) >>>> prepareIllegalVolumeError: Cannot prepare illegal volume: >>>> (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) >>>> 2020-01-09 02:18:44,932-0600 INFO (vm/c5d0a42f) >>>> [storage.TaskManager.Task] (Task='26053225-6569-4b73-abdd-7d6c7e15d1e9') >>>> aborting: Task is aborted: "Cannot prepare illegal volume: >>>> (u'f8066c56-6db1-4605-8d7c-0739335d30b8',)" - code 227 (task:1181) >>>> 2020-01-09 02:18:44,933-0600 ERROR (vm/c5d0a42f) [storage.Dispatcher] >>>> FINISH prepareImage error=Cannot prepare illegal volume: >>>> (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) (dispatcher:82) >>>> 2020-01-09 02:18:44,933-0600 ERROR (vm/c5d0a42f) [virt.vm] >>>> (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') The vm start process failed >>>> (vm:949) >>>> Traceback (most recent call last): >>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 878, in >>>> _startUnderlyingVm >>>> self._run() >>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2798, >>>> in _run >>>> self._devices = self._make_devices() >>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2639, >>>> in _make_devices >>>> disk_objs = self._perform_host_local_adjustment() >>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2712, >>>> in _perform_host_local_adjustment >>>> self._preparePathsForDrives(disk_params) >>>> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 1023, >>>> in _preparePathsForDrives >>>> drive['path'] = self.cif.prepareVolumePath(drive, self.id) >>>> File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 417, >>>> in prepareVolumePath >>>> raise vm.VolumeError(drive) >>>> VolumeError: Bad volume specification {'address': {'bus': '0', >>>> 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '0'}, 'serial': >>>> '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'index': 0, 'iface': 'scsi', >>>> 'apparentsize': '36440899584', 'specParams': {}, 'cache': 'writeback', >>>> 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'truesize': >>>> '16916186624', 'type': 'disk', 'domainID': >>>> '6e627364-5e0c-4250-ac95-7cd914d0175f', 'reqsize': '0', 'format': 'cow', >>>> 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': >>>> '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> 'propagateErrors': 'off', 'name': 'sda', 'bootOrder': '1', 'volumeID': >>>> 'f8066c56-6db1-4605-8d7c-0739335d30b8', 'diskType': 'file', 'alias': >>>> 'ua-4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'discard': False} >>>> 2020-01-09 02:18:44,934-0600 INFO (vm/c5d0a42f) [virt.vm] >>>> (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') Changed state to Down: Bad >>>> volume specification {'address': {'bus': '0', 'controller': '0', 'type': >>>> 'drive', 'target': '0', 'unit': '0'}, 'serial': >>>> '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'index': 0, 'iface': 'scsi', >>>> 'apparentsize': '36440899584', 'specParams': {}, 'cache': 'writeback', >>>> 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'truesize': >>>> '16916186624', 'type': 'disk', 'domainID': >>>> '6e627364-5e0c-4250-ac95-7cd914d0175f', 'reqsize': '0', 'format': 'cow', >>>> 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': >>>> '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> 'propagateErrors': 'off', 'name': 'sda', 'bootOrder': '1', 'volumeID': >>>> 'f8066c56-6db1-4605-8d7c-0739335d30b8', 'diskType': 'file', 'alias': >>>> 'ua-4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'discard': False} (code=1) >>>> (vm:1689) >>>> 2020-01-09 02:18:44,963-0600 INFO (vm/c5d0a42f) [virt.vm] >>>> (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') Stopping connection >>>> (guestagent:442) >>>> 2020-01-09 02:18:44,978-0600 INFO (jsonrpc/4) [api.virt] START >>>> destroy(gracefulAttempts=1) from=::ffff:192.168.2.15,57858, >>>> flow_id=4b57f1a6, vmId=c5d0a42f-3b1e-43ee-a567-7844654011f5 (api:46) >>>> 2 >>>> >>>> >>>> Log excerpt from attempt to migrate the affected drive to another >>>> storage device: >>>> 2020-01-09 05:27:14,362-0600 INFO (jsonrpc/2) [storage.VolumeManifest] >>>> ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8 >>>> info is {'status': 'OK', 'domain': 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', >>>> 'voltype': 'LEAF', 'description': 'None', 'parent': >>>> 'a912e388-d80d-4f56-805b-ea5e2f35d741', 'format': 'COW', 'generation': 0, >>>> 'image': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'ctime': '1578559013', >>>> 'disktype': 'DATA', 'legality': 'LEGAL', 'mtime': '0', 'apparentsize': >>>> '219008', 'children': [], 'pool': '', 'capacity': '1503238553600', 'uuid': >>>> u'f8066c56-6db1-4605-8d7c-0739335d30b8', 'truesize': '26624', 'type': >>>> 'SPARSE', 'lease': {'path': u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> 'owners': [], 'version': None, 'offset': 0}} (volume:282) >>>> 2020-01-09 05:27:14,362-0600 INFO (jsonrpc/2) [vdsm.api] FINISH >>>> getVolumeInfo return={'info': {'status': 'OK', 'domain': >>>> 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', 'voltype': 'LEAF', 'description': >>>> 'None', 'parent': 'a912e388-d80d-4f56-805b-ea5e2f35d741', 'format': 'COW', >>>> 'generation': 0, 'image': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'ctime': >>>> '1578559013', 'disktype': 'DATA', 'legality': 'LEGAL', 'mtime': '0', >>>> 'apparentsize': '219008', 'children': [], 'pool': '', 'capacity': >>>> '1503238553600', 'uuid': u'f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> 'truesize': '26624', 'type': 'SPARSE', 'lease': {'path': >>>> u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> 'owners': [], 'version': None, 'offset': 0}}} >>>> from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, >>>> task_id=28e885f7-df18-4ea5-bb6e-eaee7385b519 (api:52) >>>> 2020-01-09 05:27:14,363-0600 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] >>>> RPC call Volume.getInfo succeeded in 0.04 seconds (__init__:573) >>>> 2020-01-09 05:27:14,394-0600 INFO (jsonrpc/6) [vdsm.api] START >>>> sdm_copy_data(job_id=u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', >>>> source={u'img_id': u'4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', u'sd_id': >>>> u'6e627364-5e0c-4250-ac95-7cd914d0175f', u'endpoint_type': u'div', >>>> u'vol_id': u'f8066c56-6db1-4605-8d7c-0739335d30b8'}, >>>> destination={u'generation': 0, u'img_id': >>>> u'4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', u'sd_id': >>>> u'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', u'endpoint_type': u'div', >>>> u'vol_id': u'f8066c56-6db1-4605-8d7c-0739335d30b8'}) >>>> from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, >>>> task_id=f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (api:46) >>>> 2020-01-09 05:27:14,395-0600 INFO (jsonrpc/6) [vdsm.api] FINISH >>>> sdm_copy_data return=None from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, >>>> task_id=f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (api:52) >>>> 2020-01-09 05:27:14,395-0600 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] >>>> RPC call SDM.copy_data succeeded in 0.00 seconds (__init__:573) >>>> 2020-01-09 05:27:14,396-0600 INFO (tasks/4) >>>> [storage.ThreadPool.WorkerThread] START task >>>> f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (cmd=<bound method Task.commit of >>>> <vdsm.storage.task.Task instance at 0x7ff3a42613b0>>, args=None) >>>> (threadPool:208) >>>> 2020-01-09 05:27:14,396-0600 INFO (tasks/4) [root] Running job >>>> u'9a47a14f-d398-4fe8-81fa-59cba7122aa0'... (jobs:183) >>>> 2020-01-09 05:27:14,429-0600 INFO (jsonrpc/1) [api.host] START >>>> getJobs(job_type=u'storage', >>>> job_ids=[u'9a47a14f-d398-4fe8-81fa-59cba7122aa0']) >>>> from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:46) >>>> 2020-01-09 05:27:14,430-0600 INFO (jsonrpc/1) [api.host] FINISH >>>> getJobs return={'status': {'message': 'Done', 'code': 0}, 'jobs': >>>> {u'9a47a14f-d398-4fe8-81fa-59cba7122aa0': {'status': 'running', 'job_type': >>>> 'storage', 'id': u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', 'description': >>>> 'copy_data'}}} from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:52) >>>> 2020-01-09 05:27:14,430-0600 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] >>>> RPC call Host.getJobs succeeded in 0.00 seconds (__init__:573) >>>> 2020-01-09 05:27:14,459-0600 INFO (tasks/4) [storage.SANLock] >>>> Acquiring Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> offset=0) for host id 2 (clusterlock:386) >>>> 2020-01-09 05:27:14,496-0600 INFO (tasks/4) [storage.SANLock] >>>> Successfully acquired Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> offset=0) for host id 2 (clusterlock:424) >>>> 2020-01-09 05:27:14,498-0600 INFO (tasks/4) [storage.VolumeManifest] >>>> Volume: preparing volume >>>> 6e627364-5e0c-4250-ac95-7cd914d0175f/f8066c56-6db1-4605-8d7c-0739335d30b8 >>>> (volume:569) >>>> 2020-01-09 05:27:14,502-0600 INFO (tasks/4) [storage.SANLock] >>>> Releasing Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> offset=0) (clusterlock:487) >>>> 2020-01-09 05:27:14,504-0600 INFO (tasks/4) [storage.SANLock] >>>> Successfully released Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', >>>> path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', >>>> offset=0) (clusterlock:496) >>>> 2020-01-09 05:27:14,504-0600 ERROR (tasks/4) [root] Job >>>> u'9a47a14f-d398-4fe8-81fa-59cba7122aa0' failed (jobs:221) >>>> Traceback (most recent call last): >>>> File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 157, in run >>>> self._run() >>>> File >>>> "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/copy_data.py", line >>>> 61, in _run >>>> with self._source.prepare(), self._dest.prepare(): >>>> File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ >>>> return self.gen.next() >>>> File >>>> "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/copy_data.py", line >>>> 172, in prepare >>>> self.volume.prepare(rw=self._writable, justme=False) >>>> File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line >>>> 574, in prepare >>>> raise se.prepareIllegalVolumeError(self.volUUID) >>>> prepareIllegalVolumeError: Cannot prepare illegal volume: >>>> ('f8066c56-6db1-4605-8d7c-0739335d30b8',) >>>> 2020-01-09 05:27:14,505-0600 INFO (tasks/4) [root] Job >>>> u'9a47a14f-d398-4fe8-81fa-59cba7122aa0' will be deleted in 3600 seconds >>>> (jobs:249) >>>> 2020-01-09 05:27:14,506-0600 INFO (tasks/4) >>>> [storage.ThreadPool.WorkerThread] FINISH task >>>> f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (threadPool:210) >>>> 2020-01-09 05:27:16,459-0600 INFO (jsonrpc/4) [api.host] START >>>> getJobs(job_type=u'storage', >>>> job_ids=[u'9a47a14f-d398-4fe8-81fa-59cba7122aa0']) >>>> from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:46) >>>> 2020-01-09 05:27:16,460-0600 INFO (jsonrpc/4) [api.host] FINISH >>>> getJobs return={'status': {'message': 'Done', 'code': 0}, 'jobs': >>>> {u'9a47a14f-d398-4fe8-81fa-59cba7122aa0': {'status': 'failed', 'error': >>>> {'message': "Cannot prepare illegal volume: >>>> ('f8066c56-6db1-4605-8d7c-0739335d30b8',)", 'code': 227}, 'job_type': >>>> 'storage', 'id': u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', 'description': >>>> 'copy_data'}}} from=::ffff:192.168.2.15,57858, >>>> flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:52) >>>> 2 >>>> >>>> Regards, >>>> David Johnson >>>> Director of Development, Maxis Technology >>>> 844.696.2947 ext 702 (o) | 479.531.3590 (c) >>>> djohnson(a)maxistechnology.com >>>> >>>> >>>> [image: Maxis Techncology] <http://www.maxistechnology.com> >>>> www.maxistechnology.com >>>> >>>> >>>> *stay connected <http://www.linkedin.com/in/pojoguy>* >>>> _______________________________________________ >>>> 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/KKLZKSPCESYVJ… >>>> >>>

1 2

AWX and error using ovirt as an inventory source
by Gianluca Cecchi 09 Jan '20

09 Jan '20

Hello, I have awx 9.0.1 and ansible 2.8.5 in container of a CentOS 7.7 server. I'm trying to use oVirt 4.3.6.7-1.el7 as a source of an inventory in awx but I get error when syncing Find at bottom below the error messages. I see that in recent past (around June this year) there were some problems, but they should be solved now, correct? There was also a problem in syncing when some powered off VMs were present in oVirt env, but I think this solved too, correct? Any way to replicate / test from command line of awx container? I try some things but in command line I always get error regarding oVirt inventory script requires ovirt-engine-sdk-python >= 4.0.0 that I think depends on not using correct command line and/or not setting needed env. Thanks in advance, Gianluca 2.536 INFO Updating inventory 4: MYDC_OVIRT 3.011 INFO Reading Ansible inventory source: /var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/plugins/inventory/ovirt4.py 3.013 INFO Using VIRTUAL_ENV: /var/lib/awx/venv/ansible 3.013 INFO Using PATH: /var/lib/awx/venv/ansible/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 3.013 INFO Using PYTHONPATH: /var/lib/awx/venv/ansible/lib/python3.6/site-packages: Traceback (most recent call last): File "/var/lib/awx/venv/awx/bin/awx-manage", line 11, in <module> load_entry_point('awx==9.0.1.0', 'console_scripts', 'awx-manage')() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/__init__.py", line 158, in manage execute_from_command_line(sys.argv) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1153, in handle raise exc File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1043, in handle venv_path=venv_path, verbosity=self.verbosity).load() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 214, in load return self.command_to_json(base_args + ['--list']) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 197, in command_to_json self.method, proc.returncode, stdout, stderr)) RuntimeError: ansible-inventory failed (rc=1) with stdout: stderr: ansible-inventory 2.8.5 config file = /etc/ansible/ansible.cfg configured module search path = ['/var/lib/awx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python3.6/site-packages/ansible executable location = /usr/bin/ansible-inventory python version = 3.6.8 (default, Oct 7 2019, 17:58:22) [GCC 8.2.1 20180905 (Red Hat 8.2.1-3)] Using /etc/ansible/ansible.cfg as config file [WARNING]: * Failed to parse /var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py with script plugin: Inventory script (/var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py) had an execution error: File "/usr/lib/python3.6/site-packages/ansible/inventory/manager.py", line 268, in parse_source plugin.parse(self._inventory, self._loader, source, cache=cache) File "/usr/lib/python3.6/site-packages/ansible/plugins/inventory/script.py", line 161, in parse raise AnsibleParserError(to_native(e)) [WARNING]: Unable to parse /var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py as an inventory source ERROR! No inventory was parsed, please check your configuration and options.

3 23

After NAS crash, one VM will not start up, Cannot prepare illegal volume
by David Johnson 09 Jan '20

09 Jan '20

We had a drive in our NAS fail, but afterwards one of our VM's will not start. The boot drive on the VM is (so near as I can tell) the only drive affected. I confirmed that the disk images (active and snapshot) are both valid with qemu. I followed the instructions at https://www.canarytek.com/2017/07/02/Recover_oVirt_Illegal_Snapshots.html to identify the snapshot images that were marked "invalid" and marked them as valid. update images set imagestatus=1 where imagestatus=4; Log excerpt from attempt to start VM: 2020-01-09 02:18:44,908-0600 INFO (vm/c5d0a42f) [vdsm.api] START prepareImage(sdUUID='6e627364-5e0c-4250-ac95-7cd914d0175f', spUUID='25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', imgUUID='4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', leafUUID='f8066c56-6db1-4605-8d7c-0739335d30b8', allowIllegal=False) from=internal, task_id=26053225-6569-4b73-abdd-7d6c7e15d1e9 (api:46) 2020-01-09 02:18:44,931-0600 INFO (vm/c5d0a42f) [vdsm.api] FINISH prepareImage error=Cannot prepare illegal volume: (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) from=internal, task_id=26053225-6569-4b73-abdd-7d6c7e15d1e9 (api:50) 2020-01-09 02:18:44,932-0600 ERROR (vm/c5d0a42f) [storage.TaskManager.Task] (Task='26053225-6569-4b73-abdd-7d6c7e15d1e9') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in prepareImage File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3187, in prepareImage raise se.prepareIllegalVolumeError(volUUID) prepareIllegalVolumeError: Cannot prepare illegal volume: (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) 2020-01-09 02:18:44,932-0600 INFO (vm/c5d0a42f) [storage.TaskManager.Task] (Task='26053225-6569-4b73-abdd-7d6c7e15d1e9') aborting: Task is aborted: "Cannot prepare illegal volume: (u'f8066c56-6db1-4605-8d7c-0739335d30b8',)" - code 227 (task:1181) 2020-01-09 02:18:44,933-0600 ERROR (vm/c5d0a42f) [storage.Dispatcher] FINISH prepareImage error=Cannot prepare illegal volume: (u'f8066c56-6db1-4605-8d7c-0739335d30b8',) (dispatcher:82) 2020-01-09 02:18:44,933-0600 ERROR (vm/c5d0a42f) [virt.vm] (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') The vm start process failed (vm:949) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 878, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2798, in _run self._devices = self._make_devices() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2639, in _make_devices disk_objs = self._perform_host_local_adjustment() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2712, in _perform_host_local_adjustment self._preparePathsForDrives(disk_params) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 1023, in _preparePathsForDrives drive['path'] = self.cif.prepareVolumePath(drive, self.id) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 417, in prepareVolumePath raise vm.VolumeError(drive) VolumeError: Bad volume specification {'address': {'bus': '0', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '0'}, 'serial': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'index': 0, 'iface': 'scsi', 'apparentsize': '36440899584', 'specParams': {}, 'cache': 'writeback', 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'truesize': '16916186624', 'type': 'disk', 'domainID': '6e627364-5e0c-4250-ac95-7cd914d0175f', 'reqsize': '0', 'format': 'cow', 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', 'propagateErrors': 'off', 'name': 'sda', 'bootOrder': '1', 'volumeID': 'f8066c56-6db1-4605-8d7c-0739335d30b8', 'diskType': 'file', 'alias': 'ua-4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'discard': False} 2020-01-09 02:18:44,934-0600 INFO (vm/c5d0a42f) [virt.vm] (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') Changed state to Down: Bad volume specification {'address': {'bus': '0', 'controller': '0', 'type': 'drive', 'target': '0', 'unit': '0'}, 'serial': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'index': 0, 'iface': 'scsi', 'apparentsize': '36440899584', 'specParams': {}, 'cache': 'writeback', 'imageID': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'truesize': '16916186624', 'type': 'disk', 'domainID': '6e627364-5e0c-4250-ac95-7cd914d0175f', 'reqsize': '0', 'format': 'cow', 'poolID': '25cd9bfc-bab6-11e8-90f3-78acc0b47b4d', 'device': 'disk', 'path': '/rhev/data-center/25cd9bfc-bab6-11e8-90f3-78acc0b47b4d/6e627364-5e0c-4250-ac95-7cd914d0175f/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8', 'propagateErrors': 'off', 'name': 'sda', 'bootOrder': '1', 'volumeID': 'f8066c56-6db1-4605-8d7c-0739335d30b8', 'diskType': 'file', 'alias': 'ua-4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'discard': False} (code=1) (vm:1689) 2020-01-09 02:18:44,963-0600 INFO (vm/c5d0a42f) [virt.vm] (vmId='c5d0a42f-3b1e-43ee-a567-7844654011f5') Stopping connection (guestagent:442) 2020-01-09 02:18:44,978-0600 INFO (jsonrpc/4) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:192.168.2.15,57858, flow_id=4b57f1a6, vmId=c5d0a42f-3b1e-43ee-a567-7844654011f5 (api:46) 2 Log excerpt from attempt to migrate the affected drive to another storage device: 2020-01-09 05:27:14,362-0600 INFO (jsonrpc/2) [storage.VolumeManifest] ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8 info is {'status': 'OK', 'domain': 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', 'voltype': 'LEAF', 'description': 'None', 'parent': 'a912e388-d80d-4f56-805b-ea5e2f35d741', 'format': 'COW', 'generation': 0, 'image': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'ctime': '1578559013', 'disktype': 'DATA', 'legality': 'LEGAL', 'mtime': '0', 'apparentsize': '219008', 'children': [], 'pool': '', 'capacity': '1503238553600', 'uuid': u'f8066c56-6db1-4605-8d7c-0739335d30b8', 'truesize': '26624', 'type': 'SPARSE', 'lease': {'path': u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', 'owners': [], 'version': None, 'offset': 0}} (volume:282) 2020-01-09 05:27:14,362-0600 INFO (jsonrpc/2) [vdsm.api] FINISH getVolumeInfo return={'info': {'status': 'OK', 'domain': 'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', 'voltype': 'LEAF', 'description': 'None', 'parent': 'a912e388-d80d-4f56-805b-ea5e2f35d741', 'format': 'COW', 'generation': 0, 'image': '4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', 'ctime': '1578559013', 'disktype': 'DATA', 'legality': 'LEGAL', 'mtime': '0', 'apparentsize': '219008', 'children': [], 'pool': '', 'capacity': '1503238553600', 'uuid': u'f8066c56-6db1-4605-8d7c-0739335d30b8', 'truesize': '26624', 'type': 'SPARSE', 'lease': {'path': u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', 'owners': [], 'version': None, 'offset': 0}}} from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, task_id=28e885f7-df18-4ea5-bb6e-eaee7385b519 (api:52) 2020-01-09 05:27:14,363-0600 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Volume.getInfo succeeded in 0.04 seconds (__init__:573) 2020-01-09 05:27:14,394-0600 INFO (jsonrpc/6) [vdsm.api] START sdm_copy_data(job_id=u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', source={u'img_id': u'4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', u'sd_id': u'6e627364-5e0c-4250-ac95-7cd914d0175f', u'endpoint_type': u'div', u'vol_id': u'f8066c56-6db1-4605-8d7c-0739335d30b8'}, destination={u'generation': 0, u'img_id': u'4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6', u'sd_id': u'ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7', u'endpoint_type': u'div', u'vol_id': u'f8066c56-6db1-4605-8d7c-0739335d30b8'}) from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, task_id=f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (api:46) 2020-01-09 05:27:14,395-0600 INFO (jsonrpc/6) [vdsm.api] FINISH sdm_copy_data return=None from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731, task_id=f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (api:52) 2020-01-09 05:27:14,395-0600 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call SDM.copy_data succeeded in 0.00 seconds (__init__:573) 2020-01-09 05:27:14,396-0600 INFO (tasks/4) [storage.ThreadPool.WorkerThread] START task f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (cmd=<bound method Task.commit of <vdsm.storage.task.Task instance at 0x7ff3a42613b0>>, args=None) (threadPool:208) 2020-01-09 05:27:14,396-0600 INFO (tasks/4) [root] Running job u'9a47a14f-d398-4fe8-81fa-59cba7122aa0'... (jobs:183) 2020-01-09 05:27:14,429-0600 INFO (jsonrpc/1) [api.host] START getJobs(job_type=u'storage', job_ids=[u'9a47a14f-d398-4fe8-81fa-59cba7122aa0']) from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:46) 2020-01-09 05:27:14,430-0600 INFO (jsonrpc/1) [api.host] FINISH getJobs return={'status': {'message': 'Done', 'code': 0}, 'jobs': {u'9a47a14f-d398-4fe8-81fa-59cba7122aa0': {'status': 'running', 'job_type': 'storage', 'id': u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', 'description': 'copy_data'}}} from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:52) 2020-01-09 05:27:14,430-0600 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getJobs succeeded in 0.00 seconds (__init__:573) 2020-01-09 05:27:14,459-0600 INFO (tasks/4) [storage.SANLock] Acquiring Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', offset=0) for host id 2 (clusterlock:386) 2020-01-09 05:27:14,496-0600 INFO (tasks/4) [storage.SANLock] Successfully acquired Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', offset=0) for host id 2 (clusterlock:424) 2020-01-09 05:27:14,498-0600 INFO (tasks/4) [storage.VolumeManifest] Volume: preparing volume 6e627364-5e0c-4250-ac95-7cd914d0175f/f8066c56-6db1-4605-8d7c-0739335d30b8 (volume:569) 2020-01-09 05:27:14,502-0600 INFO (tasks/4) [storage.SANLock] Releasing Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', offset=0) (clusterlock:487) 2020-01-09 05:27:14,504-0600 INFO (tasks/4) [storage.SANLock] Successfully released Lease(name='f8066c56-6db1-4605-8d7c-0739335d30b8', path=u'/rhev/data-center/mnt/192.168.2.223:_mnt_ovirt-main-pool/ec6ccb14-03c2-49cc-9cc0-b1a87d582ed7/images/4081ce8f-1ce1-4ee1-aa43-69af2dfc5ab6/f8066c56-6db1-4605-8d7c-0739335d30b8.lease', offset=0) (clusterlock:496) 2020-01-09 05:27:14,504-0600 ERROR (tasks/4) [root] Job u'9a47a14f-d398-4fe8-81fa-59cba7122aa0' failed (jobs:221) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 157, in run self._run() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/copy_data.py", line 61, in _run with self._source.prepare(), self._dest.prepare(): File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/copy_data.py", line 172, in prepare self.volume.prepare(rw=self._writable, justme=False) File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 574, in prepare raise se.prepareIllegalVolumeError(self.volUUID) prepareIllegalVolumeError: Cannot prepare illegal volume: ('f8066c56-6db1-4605-8d7c-0739335d30b8',) 2020-01-09 05:27:14,505-0600 INFO (tasks/4) [root] Job u'9a47a14f-d398-4fe8-81fa-59cba7122aa0' will be deleted in 3600 seconds (jobs:249) 2020-01-09 05:27:14,506-0600 INFO (tasks/4) [storage.ThreadPool.WorkerThread] FINISH task f1504b2d-c6c2-4866-97ce-e0476b0ba9a2 (threadPool:210) 2020-01-09 05:27:16,459-0600 INFO (jsonrpc/4) [api.host] START getJobs(job_type=u'storage', job_ids=[u'9a47a14f-d398-4fe8-81fa-59cba7122aa0']) from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:46) 2020-01-09 05:27:16,460-0600 INFO (jsonrpc/4) [api.host] FINISH getJobs return={'status': {'message': 'Done', 'code': 0}, 'jobs': {u'9a47a14f-d398-4fe8-81fa-59cba7122aa0': {'status': 'failed', 'error': {'message': "Cannot prepare illegal volume: ('f8066c56-6db1-4605-8d7c-0739335d30b8',)", 'code': 227}, 'job_type': 'storage', 'id': u'9a47a14f-d398-4fe8-81fa-59cba7122aa0', 'description': 'copy_data'}}} from=::ffff:192.168.2.15,57858, flow_id=94ad3bf0-c5f5-4d45-af2a-49aa4eaa6731 (api:52) 2 Regards, David Johnson Director of Development, Maxis Technology 844.696.2947 ext 702 (o) | 479.531.3590 (c) djohnson(a)maxistechnology.com [image: Maxis Techncology] <http://www.maxistechnology.com> www.maxistechnology.com *stay connected <http://www.linkedin.com/in/pojoguy>*

2 3

Storage I/O problem.
by Christian Reiss 09 Jan '20

09 Jan '20

Ugh, After having rebooted the 3-way HCI Cluster everything came back online, all the gluster volumes are online, no split-brain info detected. Also they are mounted on all nodes. The Volumes, Domains and Disks are all marked green in the Engine. Launching a VM fails with "VM test01 has been paused due to storage I/O problem." A md5 sum of an uploaded ISO image from all three mounted cluster members yield the same md5, so does the source file on my PC. Creating a new VM and attaching that ISO fails: The ISO is not readable (says the vm console). The Disk Image from the test01 vm seems sounds (file has correct size, file-tool shows correct magic header), other files (configs) are readable. I did complete cluster reboot etc. gluster> volume heal vms info split-brain Brick node01:/gluster_bricks/vms/vms Status: Connected Number of entries in split-brain: 0 Brick node02:/gluster_bricks/vms/vms Status: Connected Number of entries in split-brain: 0 Brick node03:/gluster_bricks/vms/vms Status: Connected Number of entries in split-brain: 0 Brick node01:/gluster_bricks/vms/vms Status: Connected Total Number of entries: 0 Number of entries in heal pending: 0 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Brick node02:/gluster_bricks/vms/vms Status: Connected Total Number of entries: 0 Number of entries in heal pending: 0 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Brick node03:/gluster_bricks/vms/vms Status: Connected Total Number of entries: 0 Number of entries in heal pending: 0 Number of entries in split-brain: 0 Number of entries possibly healing: 0 How would I fix this issue? Anyone got a clue on how to proceed? -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

1 1

Re: Question about HCI gluster_inventory.yml
by John Call 08 Jan '20

08 Jan '20

Simone, ovirt-users, I'm running into an issue with the ovirt.hosted_engine_setup role. I can't decide if my problem is 1) that the SSH connection to the HostedEngineLocal VM repeatedly fails due to that new VM not having an entry in ~/.ssh/known_hosts or 2) that I don't have some variable defined correctly. I can force my way past #1 by setting host_key_checking=false in ansible.cfg, but if I do that, I immediately get an error about an undefined hostvar variable... Can you point me in the right direction to debug this? I would really like to be able to rebuild my RHHI/RHV cluster using these gluster+ovirt roles. Here is the undefined variable error, and the variable files I'm including via the "ansible-playbook -e..." syntax: TASK [ovirt.hosted_engine_setup : Wait for the local VM] ***************************************************************************************** ok: [localhost -> rhvm.home.lab] TASK [ovirt.hosted_engine_setup : Add an entry for this host on /etc/hosts on the local VM] ****************************************************** fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. *The error was: u\"hostvars['rhhi1.home.lab']\" is undefined*\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml': line 8, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n timeout: 180\n - name: Add an entry for this host on /etc/hosts on the local VM\n ^ here\n"} Thank you, John Call Red Hat - Storage Domain Architect jcall(a)redhat.com (714) 267-8802 On Tue, Jan 7, 2020 at 12:27 AM Gobinda Das <godas(a)redhat.com> wrote: > Hi John, > Sorry misunderstood, I thought you are using cockpit based deployment. > Your gluster_inventory is correct for end to end deployment. > > On Tue, Jan 7, 2020 at 12:43 PM Gobinda Das <godas(a)redhat.com> wrote: > >> Hi John, >> I am seeing error: >> TASK [ovirt.hosted_engine_setup : Get local VM dir path] >> ***************************************************************************************** >> task path: >> /usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml:57 >> fatal: [localhost]: FAILED! => { >> "msg": "The task includes an option with an undefined variable. The >> error was: 'ansible.vars.hostvars.HostVarsVars object' has no attribute >> 'he_local_vm_dir'\n\nThe error appears to be in >> '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml': >> line 57, column 7, but may\nbe elsewhere in the file depending on the exact >> syntax problem.\n\nThe offending line appears to be:\n\n delegate_to: >> \"{{ he_ansible_host_name }}\"\n - name: Get local VM dir path\n ^ >> here\n" >> } >> Adding @Simone Tiraboschi <stirabos(a)redhat.com> >> Simone do we need to explicitly specify he_local_vm_dir ? >> In gluster_inventory you can't mention other hosts and SD informations to >> auto add. For that you need to create separate file under: >> /usr/share/ovirt-hosted-engine-setup/gdeploy-inventory.yml >> and add entries there like: >> >> gluster: >> hosts: >> host2: >> host3: >> vars: >> storage_domains: >> [{"name":"data","host":"host1","address":"host1","path":"/data","mount_options":"backup-volfile-servers=host2:host3"},{"name":"vmstore","host":"host1","address":"host1","path":"/vmstore","mount_options":"backup-volfile-servers=host2:host3"}] >> >> Then hook will automatically read this file and perform action >> accordingly. >> >> On Tue, Jan 7, 2020 at 11:53 AM John Call <jcall(a)redhat.com> wrote: >> >>> Hi Gobinda, ovirt-users, >>> >>> I think I'm close, but I'm running into a timeout/error when the >>> ovirt.hosted-engine-setup tasks try to connect to the new >>> "HostedEngineLocal" VM. It seems to complain about host_key_checking. I >>> disabled that via ansible.cfg, but it fails on the next task (see short >>> logs.) Do you see anything obviously wrong in my inventory and json >>> files? I've attached the verbose playbook logs when I run this from the >>> first HCI host... >>> >>> [root@rhhi1 hc-ansible-deployment]# pwd >>> /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment >>> >>> [root@rhhi1 hc-ansible-deployment]# ansible-playbook -b -vvv -i >>> gluster_inventory.yml hc_deployment.yml >>> --extra-vars='@he_gluster_vars.json' | tee playbook.logs >>> >>> >>> Thank you, >>> John Call >>> Red Hat - Storage Domain Architect >>> jcall(a)redhat.com >>> (714) 267-8802 >>> >>> >>> On Wed, Dec 11, 2019 at 11:09 PM Gobinda Das <godas(a)redhat.com> wrote: >>> >>>> Hi John, >>>> You need to specify storage-fqdn(Which should mapped to storage >>>> network) and ovirtmgmt-fqdn (Which should mapped to frontend network) like >>>> this: >>>> hc_nodes: >>>> hosts: >>>> host1-STORAGE-fqdn: >>>> host2-STORAGE-fqdn: >>>> host3-STORAGE-fqdn: >>>> vars: >>>> cluster_nodes: >>>> - host1-STORAGE-fqdn >>>> - host2-STORAGE-fqdn >>>> - host3-STORAGE-fqdn >>>> gluster_features_hci_cluster: "{{ cluster_nodes }}" >>>> >>>> gluster: >>>> host2-ovirtmgmt-fqdn: >>>> host3-ovirtmgmt-fqdn: >>>> storage_domains: >>>> [{"name":"data","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/data","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"},{"name":"vmstore","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/vmstore","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"}] >>>> >>>> >>>> On Thu, Dec 12, 2019 at 2:47 AM John Call <jcall(a)redhat.com> wrote: >>>> >>>>> Hi ovirt-users, >>>>> >>>>> I'm trying to automate my HCI deployment, but can't figure out how to >>>>> specify multiple network interfaces in gluster_inventory.yml. My servers >>>>> have two NICs, one for ovirtmgmt (and everything else), and the other is >>>>> just for Gluster. How should I populate the inventory/vars file? Is this >>>>> correct? >>>>> >>>>> [root@rhhi1 hc-ansible-deployment]# pwd >>>>> /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment >>>>> >>>>> [root@rhhi1 hc-ansible-deployment]# cat gluster_inventory.yml >>>>> --lots of stuff omitted-- >>>>> hc_nodes: >>>>> hosts: >>>>> host1-STORAGE-fqdn: >>>>> host2-STORAGE-fqdn: >>>>> host3-STORAGE-fqdn: >>>>> vars: >>>>> cluster_nodes: >>>>> - host1-ovirtmgmt-fqdn >>>>> - host2-ovirtmgmt-fqdn >>>>> - host3-ovirtmgmt-fqdn >>>>> gluster_features_hci_cluster: "{{ cluster_nodes }}" >>>>> >>>>> gluster: >>>>> host2-STORAGE-fqdn: >>>>> host3-STORAGE-fqdn: >>>>> storage_domains: >>>>> [{"name":"data","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/data","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"},{"name":"vmstore","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/vmstore","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"}] >>>>> _______________________________________________ >>>>> 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/TEAHUX6LSPM5Y… >>>>> >>>> >>>> >>>> -- >>>> >>>> >>>> Thanks, >>>> Gobinda >>>> >>> >> >> -- >> >> >> Thanks, >> Gobinda >> > > > -- > > > Thanks, > Gobinda >

1 1

upgrade the host with ovirt node ng update
by jingjie.jiang＠oracle.com 08 Jan '20

08 Jan '20

Hi, I have a 4.2.8 host which not installed with ovirt node ng installer. Can I use 4.3 ovirt node ng update to upgrade it? If so, is there a instruction to follow? Thanks, Jingjie

1 0

NIC Setup
by Christian Reiss 08 Jan '20

08 Jan '20

Hey folks, General question for understanding: Assume my hosts have - 1 10gb NIC with 10.0.0.0/24 ip for Storage/Gluster and Ovirt Engine, - 2 1gb NICs with no configured ip. Now the VMs can have a plethora of IPs from all the assigned ip blocks etc. I can't seem to figure out the right way to attach a ovirt Network to specific NICs. I keep reading that you should seperate the Storage from the VM traffic, but I am unable to find any documentation on the suggested layout, examples or anything, really. The closest thing I came to seperate the traffic, at least logically, is via vlan tagging on the ovirt storage network. But even that failed due to "No hosts has this network". *scratches head* Can someone enlighten me or push me to the Network Docs? -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

1 1

HCL: 4.3.7: Hosted engine fails
by Christian Reiss 08 Jan '20

08 Jan '20

Hey all, Using a homogeneous ovirt-node-ng-4.3.7-0.20191121.0 freshly created cluster using node installer I am unable to deploy the hosted engine. Everything else worked. In vdsm.log is a line, just after attempting to start the engine: libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: virt-ssbd I am using AMD EPYC 7282 16-Core Processors. I have attached - vdsm.log (during and failing the start) - messages (for bootup / libvirt messages) - dmesg (grub / boot config) - deploy.log (browser output during deployment) - virt-capabilites (virsh -r capabilities) I can't think -or don't know- off any other log files of interest here, but I am more than happy to oblige. notectl check tells me Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK layers: ovirt-node-ng-4.3.7-0.20191121.0: ovirt-node-ng-4.3.7-0.20191121.0+1 bootloader: default: ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64) entries: ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64): index: 0 title: ovirt-node-ng-4.3.7-0.20191121.0 (3.10.0-1062.4.3.el7.x86_64) kernel: /boot/ovirt-node-ng-4.3.7-0.20191121.0+1/vmlinuz-3.10.0-1062.4.3.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn_node01/swap rd.lvm.lv=onn_node01/ovirt-node-ng-4.3.7-0.20191121.0+1 rhgb quiet LANG=en_GB.UTF-8 img.bootid=ovirt-node-ng-4.3.7-0.20191121.0+1" initrd: /boot/ovirt-node-ng-4.3.7-0.20191121.0+1/initramfs-3.10.0-1062.4.3.el7.x86_64.img root: /dev/onn_node01/ovirt-node-ng-4.3.7-0.20191121.0+1 current_layer: ovirt-node-ng-4.3.7-0.20191121.0+1 The odd thing is the hosted engine vm does get started during initial configuration and works. Just when the ansible stuff is done an its moved over to ha storage the CPU quirks start. So far I learned that ssbd is a mitigation protection but the flag is not in my cpu. Well, ssbd is virt-ssbd is not. I am *starting* with ovirt. I would really, really welcome it if recommendations would include clues on how to make it happen. I do rtfm, but I was unable to find anything (or any solution) anywhere. Not after 80 hours of working on this. Thank you all. -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

2 3

Re: ISO Upload
by Strahil 07 Jan '20

07 Jan '20

Then ... It's a bug and shoiuld be reported. Best Regards, Strahil NikolovOn Jan 7, 2020 16:00, Chris Adams <cma(a)cmadams.net> wrote: > > Once upon a time, m.skrzetuski(a)gmail.com <m.skrzetuski(a)gmail.com> said: > > I'd give up on the ISO domain. I started like you and then read the docs which said that ISO domain is deprecated. > > I'd upload all files to a data domain. > > Note that that only works if your data domain is NFS... iSCSI data > domains will let you upload ISOs, but connecting them to a VM fails. > -- > Chris Adams <cma(a)cmadams.net> > _______________________________________________ > 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/ND4OHFK6IH6BW…

1 0

OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System
by bob.franzke＠mdaemon.com 07 Jan '20

07 Jan '20

Full disclosure here.....I am not an Ovirt Expert. I am a network Engineer that has been forced to take over sysadmin duties for a departed co-worker. I have little experience with Ovirt so apologies up front for anything I say that comes across as stupid or "RTM" questions. Normally I would do just that but I am in a bind and am trying to figure this out quickly. We have an OVirt installation setup that consists of 4 nodes and a server that hosts the ovirt-engine all running CentOS 7. The server that hosts the engine has a pair of failing hard drives and I need to replace the hardware ASAP. Need to outline the steps needed to build a new server to serve as and replace the ovirt engine server. I have backed up the entire /etc directory and the backups being done nightly by the engine itself. I also backed up the iscsi info and took a printout of all the disk arrangement . The disk has gotten so bad at this point that the DB won't back up any longer. Get fatal:backup failed error when trying to run the ovirt backup tool. Also the Ovirt management site is not rendering and I am not sure why. Is there anything else I need to make sure I backup in order to migrate the engine from one server to another? Also, until I can get the engine running again, is there any tool available to manage the VMs on the hosts themselves. The VMs on the hosts are running but need a way to manage them if needed in case something happens while the engine is being repaired. Any info on this as well as what to backup and the steps to move the engine from one server to another would be much much appreciated. Sorry I know this a real RTM type post but I am in a bind and need a solution rather quickly. Thanks in advance.

4 11

Ansible example for creating VM from qcow2 image?
by m.skrzetuski＠gmail.com 07 Jan '20

07 Jan '20

Hello there, anyone Ansible examples on how to create a VM (including cloud init) from a previously uploaded qcow2 file (using the ovirt_vm module from https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html#ovirt-… I simply cannot wrap my head around it. Do you create a disk from the qcow2 and attach it to the VM? Or do you mount it as ISO in CDROM of the VM and the automate the installation? What are the exact steps? Do I have to use templates (I don't want to)? Kind regards Skrzetuski

2 1

Deleted gluster volume
by Christian Reiss 07 Jan '20

07 Jan '20

Hey folks, I accidently deleted a volume in the oVirt Engine, Storage -> Volumes. The gluster is still up on all three nodes, but the ovirt engine refuses to re-scan it. Or to re-introduce it. How could I add the still valid and working (but deleted in the ovirt engine) gluster volume back to the engine? It's a test setup. I am trying to break & repair things. Still I am unable to find any documentation on this "use case". Thanks! -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 2

strength of oVirt compared to others???
by yam yam 07 Jan '20

07 Jan '20

Hi everyone! I want to know clear strength of oVirt compared to openstack and kubevirt(VM add-on for k8s). compared OpenStack, I heard oVirt is specialized in long-lasting traditional apps requiring robust and resilient infra while OpenStack is cloud solution. so, backend is suited for oVirt and frontend like web server is suited for OpenStack. but I 'm wondering why these traditional apps are not suited for OpenStack because I think OpenStack encompasses functions(live migration, scale-up, snapshot, ...) oVirt provides. I want to know which features in oVirt make such difference. compared to kubevirt, it seems more difficult to find strength in that both are designed to run legacy apps. under mixed environment, it seems like rather kubevirt has more benefits :'(

1 0

Question about HCI gluster_inventory.yml
by John Call 07 Jan '20

07 Jan '20

Hi ovirt-users, I'm trying to automate my HCI deployment, but can't figure out how to specify multiple network interfaces in gluster_inventory.yml. My servers have two NICs, one for ovirtmgmt (and everything else), and the other is just for Gluster. How should I populate the inventory/vars file? Is this correct? [root@rhhi1 hc-ansible-deployment]# pwd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment [root@rhhi1 hc-ansible-deployment]# cat gluster_inventory.yml --lots of stuff omitted-- hc_nodes: hosts: host1-STORAGE-fqdn: host2-STORAGE-fqdn: host3-STORAGE-fqdn: vars: cluster_nodes: - host1-ovirtmgmt-fqdn - host2-ovirtmgmt-fqdn - host3-ovirtmgmt-fqdn gluster_features_hci_cluster: "{{ cluster_nodes }}" gluster: host2-STORAGE-fqdn: host3-STORAGE-fqdn: storage_domains: [{"name":"data","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/data","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"},{"name":"vmstore","host":"host1-STORAGE-fqdn","address":"host1-STORAGE-fqdn","path":"/vmstore","mount_options":"backup-volfile-servers=host2-STORAGE-fqdn:host3-STORAGE-fqdn"}]

2 3

Confusion about storage domain ISO. How do I provision VMs?
by m.skrzetuski＠gmail.com 06 Jan '20

06 Jan '20

Hello there, I'm a bit confused about provisioning VMs (with Ansible). At first I wanted to setup a VM manually over the web UI, just to see how it works. I was not able to upload ISO files with cloud images to a data domain but I was able to upload to ISO domain. However I read that ISO domains are deprecated (see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht…) So what is the workflow/process of provisioning VMs from cloud images with cloud init? Where do I store my ISOs? Kind regards skrzetuski

3 9

VM auto start with Host?
by m.skrzetuski＠gmail.com 06 Jan '20

06 Jan '20

Hello everyone, please tell me it is possible to auto start all VMs together with a Host. How do I configure this? I found some RFEs and Bugzilla Bugs and Redhat engineers promising this but no docs about how to enable it. Kind regards Skrzetuski

2 3

Re: null
by Strahil 06 Jan '20

06 Jan '20

I do use automatic migration policy. The main question you have to solve is: 1. Why the nodes became 'Non-operational' .Usually this happens when the management interface (in your case HoatedEngine VM) could not reach the nodes over the management network. By default, management is going over the ovirtmgmt network. I guess you have created the new network. Marked that new network as management network and then the switch was off , causing 'Non-Operational state'. 2. Migrating VMs is usually a safe approach, but this behavior is quite strange. If a node ia Non-operational -> there could be no successful migration. 3. Some of the VMs got paused due to storage issue. Are you using GlusterFS, NFS or iSCSI ? If yes, you need to clarify why you lost your storage. I guess for now you can mark each VM to be migrated only manually (VM -> Edit) and if they are critical VMs , set a high Availability from each VM's Edit options. In such case, if a node fails, the VMs will be restarted on another node. 4. Have you setup node fencing ? For example APC, iLo, iDRAC and other fencing mechanisms can allow the HostedEngine use another Host as fencing proxy and to reset the problematic Hypervisor. P.S.: You can define the following alias in '~/.bashrc' : alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' Then you can verify your VMs even when a HostedEngine is down: 'virsh list --all' Best Regards, Strahil NikolovOn Dec 27, 2019 08:40, zhouhao(a)vip.friendtimes.net wrote: > > I had a crash yesterday in my ovirt cluster, which is made up of 3 nodes. > > I just tried to add a new network, but the whole cluster crashed > > I added a new network to my cluster, but while I was debugging the newswitch, when the switch was poweroff, the node detected the network card status down and then moved to Non-Operational state. > > > > At this time all of 3 nodes moved to Non-Operational state. > > All virtual machines have started automatic migration,When I received the alert email, all virtual machines were suspended > > > > > > In 15 minutes my newswitch were power up again.The 3 ovirt-nodes become active again, but many virtual machines become unresponsive or suspended due to forced migration, and only a few virtual machines are pulled up again due to cancelled migration > > After I tried to terminate the migration tasks and restart ovirt-engine service, I was still unable to restore most of the virtual machines, so I had to restart 3 ovirt-nodes to restore my virtual machine > > I didn't recover all the virtual machines until an hour later > > > Then I modify my migration policy to " Do Not Migrate Virtual Machines" > > Which migration Policy do you recommend? > > I'm afraid to use cluster... > > ________________________________ > zhouhao(a)vip.friendtimes.net

2 1

Re: Cluster CPU type update
by Strahil 06 Jan '20

06 Jan '20

Just a question from curiosity. Can't we just define second cluster and move each VM from old cluster to the new one ? Best Regards, Strahil NikkolovOn Jan 5, 2020 12:29, Eli Mesika <emesika(a)redhat.com> wrote: > > This is the right way to do that IMO > > On Sat, Jan 4, 2020 at 3:09 AM Morris, Roy <roy.morris(a)ventura.org> wrote: >> >> Hello, >> >> I'm running a 4.3 cluster with 56 VMs all set to default cluster and the cluster itself is set to Intel Westmere Family. I am getting a new server and retiring 3 old ones which brings me to my question. >> >> When implementing the new host into the cluster and retiring the older hosts. I want to change the CPU type setting in the cluster default to Broadwell which is what my new 3 host cluster will be. To make this change, I assume the process would be to turn off all VMs, set cluster cpu type to broadwell, then turn on VMs to get the new CPU flags? >> >> Just wanted to reach out and see if someone else has had to go through this before and has any notes/tips. >> >> Best regards, >> >> Roy >> >> _______________________________________________ >> 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/FKFGEOW5OI6A2…

2 1

How do I do bridged networking?
by m.skrzetuski＠gmail.com 06 Jan '20

06 Jan '20

Hello everyone, how do I set up bridged networking? I want to give my VMs direct access to the network, that is: they should get an IP from DHCP and appear as "normal" nodes. This is working out of the box for Proxmox. I was not able to find documentation that would make it possible to configure. Can I configure it via https://github.com/oVirt/ovirt-ansible-infra? Kind regards Skrzetuski

2 2

Usage statistics or graph for an oVirt environment?
by Victor Hooi 06 Jan '20

06 Jan '20

Hi, Is there an easy way to generate a dashboard or some kind of graph to track the usage of an oVirt environment? This would be things like how many VMs were created, or started, how many successful logins, how many clones etc. (Use case is to justify an internal environment/use case) Thanks, Victor

1 0

Looking for Ovirt Consultants
by Bob Franzke 06 Jan '20

06 Jan '20

Having an issue with Ovirt. Ovirt Engine server died. I have no idea about Ovirt and I am way over my head here. Trying to put the engine back together to get my environment working again. Can anyone help me here? Thanks in advance.

3 2

Re: How do I do bridged networking?
by Strahil 05 Jan '20

05 Jan '20

I setup my VMs to use the ovirtmgmt network as it is defined for all kinds of traffic. As you use Intel NUC - just create a VM manually with ovirtmgmt and if it works - check the ansible playbooks. Best Regards, Strahil Nikolov On Jan 5, 2020 18:30, m.skrzetuski(a)gmail.com wrote: > > Hello everyone, > > how do I set up bridged networking? I want to give my VMs direct access to the network, that is: they should get an IP from DHCP and appear as "normal" nodes. This is working out of the box for Proxmox. I was not able to find documentation that would make it possible to configure. Can I configure it via https://github.com/oVirt/ovirt-ansible-infra? > > Kind regards > Skrzetuski > _______________________________________________ > 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/YEO4WIVR6IKIE…

1 0

Re: Power management and storage domains error when running Ansible tasks!
by Strahil 05 Jan '20

05 Jan '20

If you have some kind of ethernet-controlled power plug - you can have fencing (at least I have considered that). Or you can edit the Host and disable the power management at all. Best Regards, Strahil Nikolov On Jan 5, 2020 17:45, m.skrzetuski(a)gmail.com wrote: > > Well this is impossible on an Intel NUC. Or am I wrong? > Any way to get rid of the error messages? Deactivate them maybe? > _______________________________________________ > 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/77VJEXJ4C7N5A…

1 0

Re: Power management and storage domains error when running Ansible tasks!
by Strahil 05 Jan '20

05 Jan '20

You need to speciify the method to be used for power fencing - that could be HPE's iLO, Dell's iDRAC, APC UPS or something else. Best Regards, Strahil NikolovOn Jan 5, 2020 14:13, m.skrzetuski(a)gmail.com wrote: > > I don't feel comfortable uploading the whole file with all the information inside it. > I can see the following entries around power management. > > 2020-01-05 12:58:18,031+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3) [26be9219] EVENT_ID: VDS_HOST_NOT_RESPONDING(9,027), Host <myhost> is not responding. Host cannot be fenced automatically because power management for the host is disabled. > [...] > 2020-01-05 12:58:24,435+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-25) [cff01c0] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host <myhost>. > > When (in the web UI) I try to activate power management for the host I get an error: Cannot edit Host. Power Management is enabled for Host but no Agent type selected. > > Which agent is the error talking about? Do I have to run an agent somewhere? > _______________________________________________ > 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/7A5KBUZALRXP7…

2 1

Re: Cluster CPU type update
by Eli Mesika 05 Jan '20

05 Jan '20

This is the right way to do that IMO On Sat, Jan 4, 2020 at 3:09 AM Morris, Roy <roy.morris(a)ventura.org> wrote: > Hello, > > I'm running a 4.3 cluster with 56 VMs all set to default cluster and the > cluster itself is set to Intel Westmere Family. I am getting a new server > and retiring 3 old ones which brings me to my question. > > When implementing the new host into the cluster and retiring the older > hosts. I want to change the CPU type setting in the cluster default to > Broadwell which is what my new 3 host cluster will be. To make this change, > I assume the process would be to turn off all VMs, set cluster cpu type to > broadwell, then turn on VMs to get the new CPU flags? > > Just wanted to reach out and see if someone else has had to go through > this before and has any notes/tips. > > Best regards, > > Roy > > _______________________________________________ > 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/FKFGEOW5OI6A2… >

1 0

Re: Cluster CPU type update
by Mathieu Simon 04 Jan '20

04 Jan '20

Hi Roy > To make this change, I assume the process would be to turn off all VMs, set cluster cpu type to broadwell, then turn on VMs to get the new CPU flags? Exactly, you can only reliably change the CPU type for a cluster once the last Westmere-based host is gone. That's what I had to do when I when we upgraded CPU microcode on clusters to enable the various CPU mitigations within the guests. After changing the CPU type at the cluster level, you should see an orange triangle shown with each VM in the Web UI indicating what VM needs a restart in order to pick up the change. Because of those various updates to CPU microcodes, check your current BIOS/UEFI (though microcode is part of CentOS/RHEL) then check the CPU Type in the tab of each Broadwell-based host. As of writing, ideally set "Intel Broadwell IBRS SSBD MDS" (or the -noTSX) variant. Regards Mathieu

1 0

Cluster CPU type update
by Morris, Roy 04 Jan '20

04 Jan '20

Hello, I'm running a 4.3 cluster with 56 VMs all set to default cluster and the cluster itself is set to Intel Westmere Family. I am getting a new server and retiring 3 old ones which brings me to my question. When implementing the new host into the cluster and retiring the older hosts. I want to change the CPU type setting in the cluster default to Broadwell which is what my new 3 host cluster will be. To make this change, I assume the process would be to turn off all VMs, set cluster cpu type to broadwell, then turn on VMs to get the new CPU flags? Just wanted to reach out and see if someone else has had to go through this before and has any notes/tips. Best regards, Roy

1 0

Can't add host with "Certificate enrollment failed". Any ideas?
by m.skrzetuski＠gmail.com 03 Jan '20

03 Jan '20

Hello everyone, I am trying to add a new host with the "ovirt.infra" role and use the following Ansible snippet for it. hosts: - name: delirium address: delirium.home cluster: Matrix public_key: true power_management_enabled: true I am getting the following error. msg: 'Error message: [''Host delirium installation failed. Certificate enrollment failed.'', ''An error has occurred during installation of Host delirium: Certificate enrollment failed.'']' Any ideas? The error does not say what exactly is wrong. The following are my SSL certs. [skrzetuski@delirium ~]$ sudo ls -lR /etc/pki/ovirt-engine/ /etc/pki/ovirt-engine/: total 68 lrwxrwxrwx. 1 root root 28 Jan 2 23:51 apache-ca.pem -> /etc/pki/ovirt-engine/ca.pem -rw-r--r--. 1 root root 384 Jan 2 23:51 cacert.conf -rw-r--r--. 1 root root 384 Jan 2 23:51 cacert.template -rw-r--r--. 1 root root 384 Nov 12 14:16 cacert.template.in -rw-r--r--. 1 root root 1647 Jan 3 01:12 ca.pem -rw-r--r--. 1 root root 1444 Jan 2 23:51 cert.conf drwxr-xr-x. 2 ovirt ovirt 4096 Jan 2 23:52 certs -rw-r--r--. 1 root root 1444 Jan 2 23:51 cert.template -rw-r--r--. 1 root root 1156 Nov 12 14:16 cert.template.in -rw-r--r--. 1 ovirt ovirt 800 Jan 2 23:52 database.txt -rw-r--r--. 1 ovirt ovirt 20 Jan 2 23:52 database.txt.attr -rw-r--r--. 1 ovirt ovirt 20 Jan 2 23:52 database.txt.attr.old -rw-r--r--. 1 ovirt ovirt 733 Jan 2 23:52 database.txt.old drwxr-xr-x. 2 root root 4096 Jan 2 23:52 keys -rw-r--r--. 1 root root 550 Nov 12 14:16 openssl.conf drwxr-x---. 2 ovirt ovirt 20 Jan 2 23:51 private drwxr-xr-x. 2 ovirt ovirt 4096 Jan 3 12:22 requests -rw-r--r--. 1 ovirt ovirt 5 Jan 2 23:52 serial.txt -rw-r--r--. 1 ovirt ovirt 5 Jan 2 23:52 serial.txt.old /etc/pki/ovirt-engine/certs: total 244 -rw-r--r--. 1 root root 1310 Jan 2 23:51 1000.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1001.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1002.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1003.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1004.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1005.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1006.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1007.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1008.pem -rw-r--r--. 1 root root 5109 Jan 2 23:51 1009.pem -rw-r--r--. 1 root root 4925 Jan 2 23:52 100A.pem -rw-r--r--. 1 root root 5011 Jan 2 23:52 100B.pem -rw-r--r--. 1 root root 5011 Jan 2 23:52 100C.pem -rw-r--r--. 1 root root 1968 Jan 3 01:12 apache.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 apache.cer.20200102235148 -rw-r--r--. 1 root root 1310 Jan 2 23:51 ca.der -rw-r--r--. 1 root root 5109 Jan 2 23:51 engine.cer -rw-r--r--. 1 root root 1727 Jan 2 23:51 imageio-proxy.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 imageio-proxy.cer.20200102235148 -rw-r--r--. 1 root root 5109 Jan 2 23:51 jboss.cer -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovirt-provider-ovn.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovirt-provider-ovn.cer.20200102235149 -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovn-ndb.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovn-ndb.cer.20200102235148 -rw-r--r--. 1 root root 1727 Jan 2 23:51 ovn-sdb.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 ovn-sdb.cer.20200102235149 -rw-r--r--. 1 root root 1727 Jan 2 23:51 reports.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 reports.cer.20200102235148 -rw-r--r--. 1 root root 4925 Jan 2 23:52 vmconsole-proxy-helper.cer -rw-r--r--. 1 root root 5011 Jan 2 23:52 vmconsole-proxy-host.cer -rw-r--r--. 1 root root 1391 Jan 2 23:52 vmconsole-proxy-host-cert.pub -rw-r--r--. 1 root root 381 Jan 2 23:52 vmconsole-proxy-host.pub -rw-r--r--. 1 root root 5011 Jan 2 23:52 vmconsole-proxy-user.cer -rw-r--r--. 1 root root 1423 Jan 2 23:52 vmconsole-proxy-user-cert.pub -rw-r--r--. 1 root root 381 Jan 2 23:52 vmconsole-proxy-user.pub -rw-r--r--. 1 root root 1727 Jan 2 23:51 websocket-proxy.cer -rw-r--r--. 1 root root 5109 Jan 2 23:51 websocket-proxy.cer.20200102235148 /etc/pki/ovirt-engine/keys: total 84 -rw-r-----. 1 root ovirt 1675 Jan 3 01:12 apache.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 apache.p12 -rw-------. 1 ovirt ovirt 1828 Jan 2 23:51 engine_id_rsa -rw-------. 1 ovirt root 2709 Jan 2 23:51 engine.p12 -rw-------. 1 root root 1828 Jan 2 23:51 imageio-proxy.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 imageio-proxy.p12 -rw-------. 1 ovirt root 2709 Jan 2 23:51 jboss.p12 -rw-------. 1 root root 1828 Jan 2 23:51 ovirt-provider-ovn.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovirt-provider-ovn.p12 -rw-------. 1 root root 1828 Jan 2 23:51 ovn-ndb.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovn-ndb.p12 -rw-------. 1 root root 1832 Jan 2 23:51 ovn-sdb.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 ovn-sdb.p12 -rw-------. 1 root root 1828 Jan 2 23:51 reports.key.nopass -rw-------. 1 root root 2709 Jan 2 23:51 reports.p12 -rw-------. 1 ovirt-vmconsole ovirt-vmconsole 1832 Jan 2 23:52 vmconsole-proxy-helper.key.nopass -rw-------. 1 root root 2677 Jan 2 23:52 vmconsole-proxy-helper.p12 -rw-------. 1 root root 2693 Jan 2 23:52 vmconsole-proxy-host.p12 -rw-------. 1 root root 2693 Jan 2 23:52 vmconsole-proxy-user.p12 -rw-------. 1 ovirt ovirt 1828 Jan 2 23:51 websocket-proxy.key.nopass -rw-------. 1 ovirt root 2709 Jan 2 23:51 websocket-proxy.p12 /etc/pki/ovirt-engine/private: total 4 -rw-r-----. 1 ovirt ovirt 1675 Jan 2 23:51 ca.pem /etc/pki/ovirt-engine/requests: total 64 -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:04 192.168.1.5.req -rw-r--r--. 1 root root 863 Jan 2 23:51 apache.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ca.csr -rw-r--r--. 1 root root 863 Jan 2 23:51 engine.req -rw-r--r--. 1 root root 863 Jan 2 23:51 imageio-proxy.req -rw-r--r--. 1 root root 863 Jan 2 23:51 jboss.req -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:11 delirium.home.req -rw-r--r--. 1 ovirt ovirt 862 Jan 3 12:22 delirium.mysecretdomain.ch.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovirt-provider-ovn.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovn-ndb.req -rw-r--r--. 1 root root 863 Jan 2 23:51 ovn-sdb.req -rw-r--r--. 1 root root 863 Jan 2 23:51 reports.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-helper.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-host.req -rw-r--r--. 1 root root 863 Jan 2 23:52 vmconsole-proxy-user.req -rw-r--r--. 1 root root 863 Jan 2 23:51 websocket-proxy.req Kind regards skrzetuski

1 1

2 node redundant cluster without hyperconverged
by gokerdalar＠gmail.com 03 Jan '20

03 Jan '20

Hello, I want to get an idea in this topic. I have two servers with the same capabilities and 8 same physical disc per node. I want to setup a cluster using a redundant disc.I dont have another server for gluster hyperconverged . How i should build for this structure ? Thanks in advance, Göker

1 0

Re: Confusion about storage domain ISO. How do I provision VMs?
by Strahil 03 Jan '20

03 Jan '20

On Jan 2, 2020 23:34, m.skrzetuski(a)gmail.com wrote: > > Hello there, > > I'm a bit confused about provisioning VMs (with Ansible). > > At first I wanted to setup a VM manually over the web UI, just to see how it works. > I was not able to upload ISO files with cloud images to a data domain but I was able to upload to ISO domain. However I read that ISO domains are deprecated (see https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht…) You should be able to import any ISO to data domains... What is the error you get ? > So what is the workflow/process of provisioning VMs from cloud images with cloud init? Where do I store my ISOs? In Storage -> Storage Domains -> Ovirt-Image-repository there are a lot of cloud images that can be imported and later used (I have neverr done that so far). So far, I'm using the ISO domain as it was in active isse when I setup my lab. > Kind regards > skrzetuski Best Regards, Strahil Nikolov

1 0

Re: 4.2.8 to 4.3.7 > Management slow
by Strahil 02 Jan '20

02 Jan '20

None is when you use multiple queues , which seems to be enabled on my HostedEngine VM by default. In both cases, we shouldn't reorder I/O requests in the VM, just to do the same on the Host. That's why I left queueing to happen only on the host. Best Regards, Strahil NikolovOn Jan 2, 2020 07:54, Guillaume Pavese <guillaume.pavese(a)interactiv-group.com> wrote: > > Hi, > > I use something similar > However, I think that the correct scheduler in case of virtio-scsi devices (sd*) should be "noop" instead of "none" > > Best, > > > Guillaume Pavese > Ingénieur Système et Réseau > Interactiv-Group > > > On Tue, Dec 31, 2019 at 9:27 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> You can manually change the I/O scheduler of the disks and if that works better for you, put a rule in udev. >> >> Here is mine: >> >> [root@engine rules.d]# cat /etc/udev/rules.d/90-default-io-scheduler.rules >> ACTION=="add|change", KERNEL=="sd*[!0-9]", ATTR{queue/scheduler}="none" >> ACTION=="add|change", KERNEL=="vd*[!0-9]", ATTR{queue/scheduler}="none" >> >> [root@engine rules.d]# cat /sys/block/vda/queue/scheduler >> [none] mq-deadline kyber >> >> Best Regards, >> Strahil Nikolov >> >> On Dec 31, 2019 12:30, Demeter Tibor <tdemeter(a)itsmart.hu> wrote: >>> >>> Dear Users, >>> >>> I've successfully upgraded my 4 node hyperconverged system from 4.2.8 to 4.3.7. >>> After upgrade everything seems to working fine, but the whole management system seems very slow. >>> Spends many seconds when I clicking on "virtual machines" or I want to edit a virtual machines. >>> The speed of vms and the IO is fine. >>> >>> It is running on a glusterfs (distributed replicate, on 3 node, 9 bricks). There are no errors, everything fine. but terrible slow:( >>> The engine vm has 0.2-0.3 load. >>> >>> What can I do? >>> >>> Thanks in advance and I wish Happy New Year! >>> >>> Regards, >>> Tibor >>> >>> >> _______________________________________________ >> 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/EYHGQ6JVLHDJI… > > > Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité

1 0

I am interested in using oVirt for my homelab but is it dead?
by m.skrzetuski＠gmail.com 02 Jan '20

02 Jan '20

Hi there, I'm a huge Ansible fan and work a lot with OpenStack and OpenShift. At home I purchased an Intel NUC to host some services for my home(-lab). I was reading about oVirt and it sounded promising, I saw all the Ansible roles. I installed ovirt on CentOS 8 (and used the Ansible roles from the Galaxy) and hit few strange walls like the standard SSL cert not being accepted by Google Chrome on Mac OSX with error "revoked". Additionally the community seems so small compared to others (like Proxmox). So I guess what I wanted to ask is: Is it dead? What's the future of oVirt? Is Redhat investing in the project? Kind regards skrzetuski

3 5

ovirt 4.3.7 + Gluster in hyperconverged (production design)
by adrianquintero＠gmail.com 02 Jan '20

02 Jan '20

Hi, After playing a bit with oVirt and Gluster in our pre-production environment for the last year, we have decided to move forward with a our production design using ovirt 4.3.7 + Gluster in a hyperconverged setup. For this we are looking get answers to a few questions that will help out with our design and eventually lead to our production deployment phase: Current HW specs (total servers = 18): 1.- Server type: DL380 GEN 9 2.- Memory: 256GB 3.-Disk QTY per hypervisor: - 2x600GB SAS (RAID 0) for the OS - 9x1.2TB SSD (RAID[0, 6..]..? ) for GLUSTER. 4.-Network: - Bond1: 2x10Gbps - Bond2: 2x10Gbps (for migration and gluster) Our plan is to build 2x9 node clusters, however the following questions come up: 1.-Should we build 2 separate environments each with its own engine? or should we do 1 engine that will manage both clusters? 2.-What would be the best gluster volume layout for #1 above with regards to RAID configuration: - JBOD or RAID6 or…?. - what is the benefit or downside of using JBOD vs RAID 6 for this particular scenario? 3.-Would you recommend Ansible-based deployment (if supported)? If yes where would I find the documentation for it? or should we just deploy using the UI?. - I have reviewed the following and in Chapter 5 it only mentions Web UI https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras… - Also looked at https://github.com/gluster/gluster-ansible/tree/master/playbooks/hc-ansible… but could not get it to work properly. 4.-what is the recommended max server qty in a hyperconverged setup with gluster, 12, 15, 18...? Thanks, Adrian

3 2

Re: Issue deploying self hosted engine on new install
by Sang Un Ahn 02 Jan '20

02 Jan '20

Hi, I have figured it out that the root cause of the deployment failure is timing out while the hosted engine was trying to connect to host vis SSH as shown in engine.log (located in /var/log/ovirt-hosted-engine-setup/engine-logs-2019-12-31T06:34:38Z/ovirt-engine): 2019-12-31 15:43:06,082+09 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) [f48796e7-a4c5-4c09-a70d-956f0c4249b4] Failed to establish session with host 'alice-ovirt-01.sdfarm.kr': SSH connection timed out connecting to 'root(a)alice-ovirt-01.sdfarm.kr' 2019-12-31 15:43:06,085+09 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) [f48796e7-a4c5-4c09-a70d-956f0c4249b4] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server alice-ovirt-01.sdfarm.kr,VDS_CANNOT_CONNECT_TO_SERVER 2019-12-31 15:43:06,129+09 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot add Host. Connecting to host via SSH has failed, verify that the host is reachable (IP address, routable address etc.) You may refer to the engine.log file for further details.] The FQDN of hosted engine (alice-ovirt-engine.sdfarm.kr <http://alice-ovirt-engine.sdfarm.kr/>) is resolved as well as the host (alice-ovirt-01.sdfarm.kr <http://alice-ovirt-01.sdfarm.kr/>) and SSH is the one of services that are allowed by firewalld. I believe the rules of firewalld is automatically configured during the deployment to work with hosted engine and the host. Also root access is configured to be allowed at the first stage of deployment. I was just wondering how I can verify the hosted engine can access to the host at this stage? Once it fails to deploy, the deployment script make all things rolled back (I believe it cleans all up) and the vm-status of hosted-engine is un-deployed. Thank you in advance, Best regards, Sang-Un

2 4

Re: oVirt and Containers
by Jan Zmeskal 02 Jan '20

02 Jan '20

Hi Robert and happy new year! :) If I understand correctly, with OKD, I just need to build full vm's in the > oVirt environment which will become hosts, compute nodes, for containers > that get deployed. > You don't even need to build the VMs. If you follow the steps outlined here <https://docs.okd.io/3.11/install_config/configuring_for_rhv.html>, the installation playbooks will take care of creating the VMs for you. Otherwise, you're right. Those VM will become master, infra and compute nodes of OKD cluster. OKD is basically just container management and it does not care whether or > not the compute nodes are VM's or bare metal. > That's correct - at least in theory. In practice the difference is mostly in installation process. But you're right - once the OKD cluster is up and running, it does not care whether its nodes are VMs or bare metal machines. Best regards Jan On Thu, Dec 26, 2019 at 6:22 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > Jan, > > Thanks for taking the time for a great reply. > > For what I am trying to accomplish here in my home lab, it seems that OKD > is the safest path. If I understand correctly, with OKD, I just need to > build full vm's in the oVirt environment which will become hosts, compute > nodes, for containers that get deployed. OKD is basically just container > management and it does not care whether or not the compute nodes are VM's > or bare metal. > > Again, thanks for taking the time to educate me. > > Robert > > ________________________________________ > From: Jan Zmeskal <jzmeskal(a)redhat.com> > Sent: Tuesday, December 24, 2019 4:43 PM > To: Robert Webb > Cc: users > Subject: Re: [ovirt-users] oVirt and Containers > > Okay, so this topic is quite vast, but I believe I can at the very least > give you a few pointers and maybe others might chime in as well. > > Firstly, there's the Kubevirt project. It enables you to manage both > application containers and virtual machines workloads (that cannot be > easily containerized) in a shared environment. Another benefit is getting > advantages of the powerful Kubernetes scheduler. I myself am not too > familiar with Kubevirt, so I can only offer this high-level overview. More > info here: https://kubevirt.io/ > > Then there is another approach which I am more familiar with. You might > want to use oVirt as an infrastructure layer on top of which you run > containerized workflow. This is achieved by deploying either OpenShift< > https://www.openshift.com/> or the upstream project OKD< > https://www.okd.io/> in the oVirt virtual machines. In that scenario, > oVirt VMs are considered by OpenShift as compute resources and are used for > scheduling containers. There are some advantages to this setup and two come > into mind. Firstly, you can scale such OpenShift cluster up or down by > adding/removing oVirt VMs according to your needs. Secondly, you don't need > to set up all of this yourself. > For OpenShift 3, Red Hat provides detailed guide on how to go about this. > Part of that guide are Ansible playbooks that automate the deployment for > you as long as you provide required variables. More info here: > https://docs.openshift.com/container-platform/3.11/install_config/configuri… > When it comes to OpenShift 4, there are two types of deployment. There's > UPI - user provisioned infrastructure. In that scenario, you prepare all > the resources for OpenShift 4 beforehand and deploy it in that existing > environment. And there's also IPI - installer provisioned infrastructure. > This means that you just give the installer access to your environment > (e.g. AWS public cloud) and the installer provisions resources for itself > based on recommendations and best practices. At this point, neither UPI nor > IPI is supported for oVirt. However there is a GitHub repository< > https://github.com/sa-ne/openshift4-rhv-upi> that can guide you through > UPI installation on oVirt and also provides automation playbooks for that. > I have personally followed the steps from the repository and deployed > OpenShift 4.2 on top of oVirt without any major issues. As far as I > remember, I might have needed occasional variable here and there but the > process worked. > > Hope this helps! > Jan > > On Tue, Dec 24, 2019 at 8:21 PM Robert Webb <rwebb(a)ropeguru.com<mailto: > rwebb(a)ropeguru.com>> wrote: > Hi Jan, > > Honestly, I didn't have anything specific in mind, just what is being used > out there today and what may be more prevalent. > > Just getting my oVIrt set up and want to know what might be recommended. > Would probably be mostly deploying images like Homeassistent, piHole, etc.. > for now. > > I guess if there is good oVirt direct integration, it would be nice to > keep it all in a single interface. > > Thanks.. > > ________________________________________ > From: Jan Zmeskal <jzmeskal(a)redhat.com<mailto:jzmeskal@redhat.com>> > Sent: Tuesday, December 24, 2019 1:54 PM > To: Robert Webb > Cc: users > Subject: Re: [ovirt-users] oVirt and Containers > > Hi Robert, > > there are different answers based on what you mean by integrating oVirt > and containers. Do you mean: > > - Installing container management (Kubernetes or OpenShift) on top of > oVirt and using oVirt as infrastructure? > - Managing containers from oVirt interface? > - Running VM workloads inside containers? > - Something different? > > I can elaborate more based on your specific needs > > Best regards > Jan > > On Tue, Dec 24, 2019 at 3:52 PM Robert Webb <rwebb(a)ropeguru.com<mailto: > rwebb(a)ropeguru.com><mailto:rwebb@ropeguru.com<mailto:rwebb@ropeguru.com>>> > wrote: > I was searching around to try and figure out the best way to integrate > oVirt and containers. > > I have found some sites that discuss it but all of them are like 2017 and > older. > > Any recommendations? > > Just build VM’s to host containers or is there some direct integration? > > Here are a couple of the old sites > > https://fromanirh.github.io/containers-in-ovirt.html > > > https://kubernetes.io/docs/setup/production-environment/on-premises-vm/ovir… > > > https://www.ovirt.org/develop/release-management/features/integration/conta… > _______________________________________________ > Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org><mailto: > users(a)ovirt.org<mailto:users@ovirt.org>> > To unsubscribe send an email to users-leave(a)ovirt.org<mailto: > users-leave(a)ovirt.org><mailto:users-leave@ovirt.org<mailto: > 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/7BIW2Z3ILBSAG… > > > -- > > Jan Zmeskal > > Quality Engineer, RHV Core System > > Red Hat <https://www.redhat.com> > > [ > https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9d… > ]<https://www.redhat.com> > > > > -- > > Jan Zmeskal > > Quality Engineer, RHV Core System > > Red Hat <https://www.redhat.com> > > [ > https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9d… > ]<https://www.redhat.com> > > -- Jan Zmeskal Quality Engineer, RHV Core System Red Hat <https://www.redhat.com> <https://www.redhat.com>

1 0

Re: 4.2.8 to 4.3.7 > Management slow
by Strahil 02 Jan '20

02 Jan '20

You can manually change the I/O scheduler of the disks and if that works better for you, put a rule in udev. Here is mine: [root@engine rules.d]# cat /etc/udev/rules.d/90-default-io-scheduler.rules ACTION=="add|change", KERNEL=="sd*[!0-9]", ATTR{queue/scheduler}="none" ACTION=="add|change", KERNEL=="vd*[!0-9]", ATTR{queue/scheduler}="none" [root@engine rules.d]# cat /sys/block/vda/queue/scheduler [none] mq-deadline kyber Best Regards, Strahil NikolovOn Dec 31, 2019 12:30, Demeter Tibor <tdemeter(a)itsmart.hu> wrote: > > Dear Users, > > I've successfully upgraded my 4 node hyperconverged system from 4.2.8 to 4.3.7. > After upgrade everything seems to working fine, but the whole management system seems very slow. > Spends many seconds when I clicking on "virtual machines" or I want to edit a virtual machines. > The speed of vms and the IO is fine. > > It is running on a glusterfs (distributed replicate, on 3 node, 9 bricks). There are no errors, everything fine. but terrible slow:( > The engine vm has 0.2-0.3 load. > > What can I do? > > Thanks in advance and I wish Happy New Year! > > Regards, > Tibor > >

2 1

Re: I am interested in using oVirt for my homelab but is it dead?
by Strahil 02 Jan '20

02 Jan '20

On Jan 1, 2020 12:46, m.skrzetuski(a)gmail.com wrote: > > Hi there, > > I'm a huge Ansible fan and work a lot with OpenStack and OpenShift. At home I purchased an Intel NUC to host some services for my home(-lab). I was reading about oVirt and it sounded promising, I saw all the Ansible roles. I installed ovirt on CentOS 8 (and used the Ansible roles from the Galaxy) and hit few strange walls like the standard SSL cert not being accepted by Google Chrome on Mac OSX with error "revoked". Additionally the community seems so small compared to others (like Proxmox). Current stable is 4.3.X based on EL7. Anything above might have issues. > > So I guess what I wanted to ask is: Is it dead? What's the future of oVirt? Is Redhat investing in the project? Not only Red Hat, but also Oracle is now providing their own solution based on Ovirt, so you can expect it won't be dead any time soon. The project is good and the community will never ignore you. Don't forget that this is the upstream of RHV/OVM and as every upstream there will be bugs (so far nothing serious). > > Kind regards > skrzetuski Best Regards, Strahil Nikolov

1 0

Re: Issue deploying self hosted engine on new install
by thomas＠hoberg.net 02 Jan '20

02 Jan '20

Yes, I have had the same and posted about it here somewhere: I believe it's an incompatible Ansible change. Here is the critical part if the message below: "The 'ovirt_host_facts' module has been renamed to 'ovirt_host_info', and the renamed one no longer returns ansible_facts" and that change was made in the transition of Ansible 2.8* to 2.9, from what I gathered. I guess I should just make it a bug report if you find the same message in your logs. [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": [{"address": "xdrd1022s.priv.atos.fr", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": {"organization": "priv.atos.fr", "subject": "O=priv.atos.fr,CN=xdrd1022s.priv.atos.fr"}, "cluster": {"href": "/ovirt-engine/api/clusters/c407e776-1c3c-11ea-aeed-00163e56112a", "id": "c407e776-1c3c-11ea-aeed-00163e56112a"}, "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "device_passthrough": {"enabled": false}, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": {"supported_rng_sources": []}, "hooks": [], "href": "/ovirt-engine/api/hosts/a5bb73a1-f923-4568-8dda-434e07f7e243", "id": "a5bb73a1-f923-4568-8dda-434e07f7e243", "katello_errata": [], "kdump_status": "unknown", "ksm": {"enabled": false}, "max_scheduling_memory": 0, "memory": 0, "name": "xdrd1022s.priv.atos.fr", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supporte d": false, "os": {"custom_kernel_cmdline": ""}, "permissions": [], "port": 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", "se_linux": {}, "spm": {"priority": 5, "status": "none"}, "ssh": {"fingerprint": "SHA256:wqpBWq9Kb9+Nb3Jwtw61QJzo+R4gGOP2dLubssU5EPs", "port": 22}, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": {"total": 0}, "tags": [], "transparent_huge_pages": {"enabled": false}, "type": "rhel", "unmanaged_networks": [], "update_available": false, "vgpu_placement": "consolidated"}]}, "attempts": 120, "changed": false, "deprecations": [{"msg": "The 'ovirt_host_facts' module has been renamed to 'ovirt_host_info', and the renamed one no longer returns ansible_facts", "version": "2.13"}]}

4 5

What does this error mean?
by zhouhao＠vip.friendtimes.net 01 Jan '20

01 Jan '20

event ID:10802 VDSM 192.168.10.56 command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '<Fault 1: "<type \'exceptions.AttributeError\'>:\'NoneType\' object has no attribute \'statistics\'">'}

1 0

Re: Node not starting | blk_cloned_rq_check_limits: over max size limit
by Strahil 31 Dec '19

31 Dec '19

By the way, why do you use multipath for local storage like this EVO nvme ? Happy New Year ! Best Regards, Strahil NikolovOn Dec 31, 2019 21:51, Strahil <hunter86_bg(a)yahoo.com> wrote: > > You can check https://access.redhat.com/solutions/2437991 & https://access.redhat.com/solutions/3014361 > > You have 2 options: > 1. Set a udev rule like this one (replace NETAPP with your storage) > ACTION!="add|change", GOTO="rule_end" ENV{ID_VENDOR}=="NETAPP*", RUN+="/bin/sh -c 'echo 4096 > /sys%p/queue/max_sectors_kb'" LABEL="rule_end" > > 2. Set max_sectors_kb in devices section of multipath.conf > You will need to stop LVM and then flush the device map , so the new option to take effect (faster is to reboot) > > Good Luck & Happy New Year. > > Best Regards, > Strahil Nikolov > On Dec 31, 2019 17:53, Stefan Wolf <shb256(a)gmail.com> wrote: > > > > hi all, > > > > i ve 4 nodes running with current ovirt. > > I ve only a problem on one host even after a fresh installation . > > I ve installed the latest image. > > Than I add the node to the cluster > > Everything is working good. > > After this I configure the network. > > BUT, after a restart the host does not come up again. > > I got this error: blk_cloned_rq_check_limits: over max size limit > > every 5 seconds > > > > I can continue with control-D > > or I can login with root password to fix the problem. but i dont know what is the problem and where does it came from > > > > I ve also changed the sas disk to nvme storage, but I ve changed this on every host. And this problem exists only on one host > > > > i found this https://lists.centos.org/pipermail/centos/2017-December/167727.html > > the output is > > [root@kvm380 ~]# ./test.sh > > Sys Block Node : Device max_sectors_kb max_hw_sectors_kb > > /sys/block/dm-0 : onn_kvm380-pool00_tmeta 256 4096 > > /sys/block/dm-1 : onn_kvm380-pool00_tdata 256 4096 > > /sys/block/dm-10 : onn_kvm380-var 256 4096 > > /sys/block/dm-11 : onn_kvm380-tmp 256 4096 > > /sys/block/dm-12 : onn_kvm380-home 256 4096 > > /sys/block/dm-13 : onn_kvm380-var_crash 256 4096 > > /sys/block/dm-2 : onn_kvm380-pool00-tpool 256 4096 > > /sys/block/dm-3 : onn_kvm380-ovirt--node--ng--4.3.7--0.20191121.0+1 256 4096 > > /sys/block/dm-4 : onn_kvm380-swap 256 4096 > > /sys/block/dm-5 : eui.0025385991b1e27a 512 2048 > > /sys/block/dm-6 : eui.0025385991b1e27a1 512 2048 > > /sys/block/dm-7 : onn_kvm380-pool00 256 4096 > > /sys/block/dm-8 : onn_kvm380-var_log_audit 256 4096 > > /sys/block/dm-9 : onn_kvm380-var_log 256 4096 > > cat: /sys/block/nvme0n1/device/vendor: Datei oder Verzeichnis nicht gefunden > > /sys/block/nvme0n1: Samsung SSD 970 EVO 1TB 512 2048 > > /sys/block/sda : HP LOGICAL VOLUME 256 4096 > > > > is the nvme not starting correct > > [root@kvm380 ~]# systemctl status multipathd > > ● multipathd.service - Device-Mapper Multipath Device Controller > > Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) > > Active: active (running) since Di 2019-12-31 16:16:32 CET; 31min ago > > Process: 1919 ExecStart=/sbin/multipathd (code=exited, status=0/SUCCESS) > > Process: 1916 ExecStartPre=/sbin/multipath -A (code=exited, status=0/SUCCESS) > > Process: 1911 ExecStartPre=/sbin/modprobe dm-multipath (code=exited, status=0/SUCCESS) > > Main PID: 1921 (multipathd) > > Tasks: 7 > > CGroup: /system.slice/multipathd.service > > └─1921 /sbin/multipathd > > > > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed > > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 > > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 > > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: 259:0: reinstated > > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: queue_if_no_path enabled > > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Recovered to normal mode > > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 1 > > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed > > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 > > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 > > > > why is it marked as failed? > > > > if i create a new volume with cockpit and use it for bricks for gluster, every thing is fine. until reboot > > > > > > maybe some one can point me the direction > > _______________________________________________ > > 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/MHHFFWAY5T5BV…

1 0

Re: Node not starting | blk_cloned_rq_check_limits: over max size limit
by Strahil 31 Dec '19

31 Dec '19

You can check https://access.redhat.com/solutions/2437991 & https://access.redhat.com/solutions/3014361 You have 2 options: 1. Set a udev rule like this one (replace NETAPP with your storage) ACTION!="add|change", GOTO="rule_end" ENV{ID_VENDOR}=="NETAPP*", RUN+="/bin/sh -c 'echo 4096 > /sys%p/queue/max_sectors_kb'" LABEL="rule_end" 2. Set max_sectors_kb in devices section of multipath.conf You will need to stop LVM and then flush the device map , so the new option to take effect (faster is to reboot) Good Luck & Happy New Year. Best Regards, Strahil Nikolov On Dec 31, 2019 17:53, Stefan Wolf <shb256(a)gmail.com> wrote: > > hi all, > > i ve 4 nodes running with current ovirt. > I ve only a problem on one host even after a fresh installation . > I ve installed the latest image. > Than I add the node to the cluster > Everything is working good. > After this I configure the network. > BUT, after a restart the host does not come up again. > I got this error: blk_cloned_rq_check_limits: over max size limit > every 5 seconds > > I can continue with control-D > or I can login with root password to fix the problem. but i dont know what is the problem and where does it came from > > I ve also changed the sas disk to nvme storage, but I ve changed this on every host. And this problem exists only on one host > > i found this https://lists.centos.org/pipermail/centos/2017-December/167727.html > the output is > [root@kvm380 ~]# ./test.sh > Sys Block Node : Device max_sectors_kb max_hw_sectors_kb > /sys/block/dm-0 : onn_kvm380-pool00_tmeta 256 4096 > /sys/block/dm-1 : onn_kvm380-pool00_tdata 256 4096 > /sys/block/dm-10 : onn_kvm380-var 256 4096 > /sys/block/dm-11 : onn_kvm380-tmp 256 4096 > /sys/block/dm-12 : onn_kvm380-home 256 4096 > /sys/block/dm-13 : onn_kvm380-var_crash 256 4096 > /sys/block/dm-2 : onn_kvm380-pool00-tpool 256 4096 > /sys/block/dm-3 : onn_kvm380-ovirt--node--ng--4.3.7--0.20191121.0+1 256 4096 > /sys/block/dm-4 : onn_kvm380-swap 256 4096 > /sys/block/dm-5 : eui.0025385991b1e27a 512 2048 > /sys/block/dm-6 : eui.0025385991b1e27a1 512 2048 > /sys/block/dm-7 : onn_kvm380-pool00 256 4096 > /sys/block/dm-8 : onn_kvm380-var_log_audit 256 4096 > /sys/block/dm-9 : onn_kvm380-var_log 256 4096 > cat: /sys/block/nvme0n1/device/vendor: Datei oder Verzeichnis nicht gefunden > /sys/block/nvme0n1: Samsung SSD 970 EVO 1TB 512 2048 > /sys/block/sda : HP LOGICAL VOLUME 256 4096 > > is the nvme not starting correct > [root@kvm380 ~]# systemctl status multipathd > ● multipathd.service - Device-Mapper Multipath Device Controller > Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) > Active: active (running) since Di 2019-12-31 16:16:32 CET; 31min ago > Process: 1919 ExecStart=/sbin/multipathd (code=exited, status=0/SUCCESS) > Process: 1916 ExecStartPre=/sbin/multipath -A (code=exited, status=0/SUCCESS) > Process: 1911 ExecStartPre=/sbin/modprobe dm-multipath (code=exited, status=0/SUCCESS) > Main PID: 1921 (multipathd) > Tasks: 7 > CGroup: /system.slice/multipathd.service > └─1921 /sbin/multipathd > > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 > Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: 259:0: reinstated > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: queue_if_no_path enabled > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Recovered to normal mode > Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 1 > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 > Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 > > why is it marked as failed? > > if i create a new volume with cockpit and use it for bricks for gluster, every thing is fine. until reboot > > > maybe some one can point me the direction > _______________________________________________ > 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/MHHFFWAY5T5BV…

1 0

Node not starting | blk_cloned_rq_check_limits: over max size limit
by Stefan Wolf 31 Dec '19

31 Dec '19

hi all, i ve 4 nodes running with current ovirt. I ve only a problem on one host even after a fresh installation . I ve installed the latest image. Than I add the node to the cluster Everything is working good. After this I configure the network. BUT, after a restart the host does not come up again. I got this error: blk_cloned_rq_check_limits: over max size limit every 5 seconds I can continue with control-D or I can login with root password to fix the problem. but i dont know what is the problem and where does it came from I ve also changed the sas disk to nvme storage, but I ve changed this on every host. And this problem exists only on one host i found this https://lists.centos.org/pipermail/centos/2017-December/167727.html the output is [root@kvm380 ~]# ./test.sh Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-0 : onn_kvm380-pool00_tmeta 256 4096 /sys/block/dm-1 : onn_kvm380-pool00_tdata 256 4096 /sys/block/dm-10 : onn_kvm380-var 256 4096 /sys/block/dm-11 : onn_kvm380-tmp 256 4096 /sys/block/dm-12 : onn_kvm380-home 256 4096 /sys/block/dm-13 : onn_kvm380-var_crash 256 4096 /sys/block/dm-2 : onn_kvm380-pool00-tpool 256 4096 /sys/block/dm-3 : onn_kvm380-ovirt--node--ng--4.3.7--0.20191121.0+1 256 4096 /sys/block/dm-4 : onn_kvm380-swap 256 4096 /sys/block/dm-5 : eui.0025385991b1e27a 512 2048 /sys/block/dm-6 : eui.0025385991b1e27a1 512 2048 /sys/block/dm-7 : onn_kvm380-pool00 256 4096 /sys/block/dm-8 : onn_kvm380-var_log_audit 256 4096 /sys/block/dm-9 : onn_kvm380-var_log 256 4096 cat: /sys/block/nvme0n1/device/vendor: Datei oder Verzeichnis nicht gefunden /sys/block/nvme0n1: Samsung SSD 970 EVO 1TB 512 2048 /sys/block/sda : HP LOGICAL VOLUME 256 4096 is the nvme not starting correct [root@kvm380 ~]# systemctl status multipathd ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) Active: active (running) since Di 2019-12-31 16:16:32 CET; 31min ago Process: 1919 ExecStart=/sbin/multipathd (code=exited, status=0/SUCCESS) Process: 1916 ExecStartPre=/sbin/multipath -A (code=exited, status=0/SUCCESS) Process: 1911 ExecStartPre=/sbin/modprobe dm-multipath (code=exited, status=0/SUCCESS) Main PID: 1921 (multipathd) Tasks: 7 CGroup: /system.slice/multipathd.service └─1921 /sbin/multipathd Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 Dez 31 16:47:58 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: 259:0: reinstated Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: queue_if_no_path enabled Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Recovered to normal mode Dez 31 16:48:02 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 1 Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: nvme0n1: mark as failed Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: Entering recovery mode: max_retries=4 Dez 31 16:48:03 kvm380.durchhalten.intern multipathd[1921]: eui.0025385991b1e27a: remaining active paths: 0 why is it marked as failed? if i create a new volume with cockpit and use it for bricks for gluster, every thing is fine. until reboot maybe some one can point me the direction

1 0

4.2.8 to 4.3.7 > Management slow
by Demeter Tibor 31 Dec '19

31 Dec '19

Dear Users, I've successfully upgraded my 4 node hyperconverged system from 4.2.8 to 4.3.7. After upgrade everything seems to working fine, but the whole management system seems very slow. Spends many seconds when I clicking on "virtual machines" or I want to edit a virtual machines. The speed of vms and the IO is fine. It is running on a glusterfs (distributed replicate, on 3 node, 9 bricks). There are no errors, everything fine. but terrible slow:( The engine vm has 0.2-0.3 load. What can I do? Thanks in advance and I wish Happy New Year! Regards, Tibor

1 0

Re: Issue deploying self hosted engine on new install
by Strahil 31 Dec '19

31 Dec '19

Hi, Most probably it is a bug. Can you add 'debugger: on_failed' to the task ? Maybe it will provide a hint where is the issue. Best Regards, Strahil NikolovOn Dec 31, 2019 06:36, realapyo(a)gmail.com wrote: > > Hi, > > I have encountered the same error that results in the failure of hosted engine deployment. I have tried to replace "ovirt_host_facts" by "ovirt_host_info" in /usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml however it did not help with the following error message: > > 2019-12-31 11:23:27,595+0900 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Wait for the host to be up] > 2019-12-31 11:23:28,997+0900 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {u'msg': u"The conditional check 'host_result_up_check is succeeded and host_result_up_check.ansible_facts.ovirt_hosts|length >= 1 and ( host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'up' or host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'non_operational' )' failed. The error was: error while evaluating conditional (host_result_up_check is succeeded and host_result_up_check.ansible_facts.ovirt_hosts|length >= 1 and ( host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'up' or host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'non_operational' )): 'dict object' has no attribute 'ansible_facts'", u'_ansible_no_log': False} > 2019-12-31 11:23:29,098+0900 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"msg": "The conditional check 'host_result_up_check is succeeded and host_result_up_check.ansible_facts.ovirt_hosts|length >= 1 and ( host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'up' or host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'non_operational' )' failed. The error was: error while evaluating conditional (host_result_up_check is succeeded and host_result_up_check.ansible_facts.ovirt_hosts|length >= 1 and ( host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'up' or host_result_up_check.ansible_facts.ovirt_hosts[0].status == 'non_operational' )): 'dict object' has no attribute 'ansible_facts'"} > > According to the latest doc of Ansible (2.9) regarding "ovirt_host_facts", it is deprecated and one should use "ovirt_host_info" instead as you can refer here: https://docs.ansible.com/ansible/latest/modules/ovirt_host_facts_module.html > > And one of the requirements to use "ovirt_host_info" is "ovirt-engine-sdk-python >= 4.3.0" however in my installation, the installed package is "python-ovirt-engine-sdk4 (4.3.2-2.el7)" instead of "ovirt-engine-sdk-python". The "ovirt-engine-sdk-python" package is available however the version is 3.6.9.1-1.el7. > > I have been trying to install the latest oVirt (based in 4.3 repository) and hyperconverged mode using 3 nodes. Tried already with cockpit installation and now debugging it by using CLI installation. > > Is this a bug or is there already a fix? > > Best regards, > Sang-Un > _______________________________________________ > 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/V2OYCPZAHUVLF…

1 0

Re: Cannot add Foreman as a provider
by Strahil 30 Dec '19

30 Dec '19

Maybe 6.1 means Foreman with Red Hat Satellite 6.1 ? Best Regards, Strahil NikolovOn Dec 30, 2019 16:41, Robert Webb <rwebb(a)ropeguru.com> wrote: > > oVirt – 4.3.7 > > Foreman - foreman-1.24.0-15.el7.noarch > > > > I have not tried any downgrades at this point. > > > > Looking at this page, https://www.ovirt.org/documentation/admin-guide/chap-External_Providers.html , it would seem that 4.3.x of oVirt is not compatible with any version of Foreman, as the page shows oVirt 4.2 is supported with Foreman 6.1. Which also confuses me as I cannot find any Foreman version 6.1. > > > > > > From: Strahil Nikolov <hunter86_bg(a)yahoo.com> > Sent: Sunday, December 29, 2019 5:00 PM > To: users <users(a)ovirt.org>; Robert Webb <rwebb(a)ropeguru.com> > Subject: Re: [ovirt-users] Cannot add Foreman as a provider > >

2 1

Re: Cannot add Foreman as a provider
by Strahil Nikolov 30 Dec '19

30 Dec '19

Hi Robert, I'm just speculating, but maybe the package on the oVirt is too new or too old ? What version is your Foreman ? Have you tried to downgrade/upgrade the packages for the integration between the 2 systems ? Best Regards,Strahil Nikolov В неделя, 29 декември 2019 г., 18:53:53 ч. Гринуич+2, Robert Webb <rwebb(a)ropeguru.com> написа: So I just setup a brand new Foreman instance and have been trying to get it setup with oVirt. I was able to install the oVirt plugins under Foreman and have the oVirt engine setup as a computer resource. Where I am running into an issue is adding Foreman as an additional provider under oVirt. In the log I get: Command 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' failed: EngineException: https://foreman.saroza-webb.internal:443/api/v2/discovered_hosts?format=jso… (Failed with error PROVIDER_FAILURE and code 5050) I have done some searching, but everything I have found seems to be from years ago and deals with oVirt 3.5.x Any thoughts? _______________________________________________ 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/CO64DW24PDJJC…

2 1