- Users - oVirt List Archives

Re: HostedEngine Unreachable
by Simone Tiraboschi 25 Feb '19

25 Feb '19

On Mon, Feb 25, 2019 at 2:53 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi Simone, > > The name resolution is working fine. > > Running: > getent ahosts engine.sanren.ac.za > > gives the same output: > > 192.168.x.x STREAM engine.sanren.ac.za > 192.168.x.x DGRAM > 192.168.x.x RAW > The IP address being the engine IP Address. > > The hosts are on the same subnet as the HostedEngine. I can ping the hosts > from each other. There is a NATting device, that NATs the private IP > addresses to public IP addresses. From the hosts I can reach the internet, > but I cant ping from outside (security measure). We also using this device > to VPN to the cluster > > *[root@gohan ~]# virsh -r list* > * Id Name State* > *----------------------------------------------------* > * 13 HostedEngine running* > > *[root@gohan ~]# virsh -r dumpxml HostedEngine | grep -i tlsPort > <graphics type='spice' port='5901' tlsPort='5902' autoport='yes' > listen='192.168.x.x' passwdValidTo='1970-01-01T00:00:01'>* > > *[root@gohan ~]# virsh -r vncdisplay HostedEngine* > *192.168.x.x:0* > > *[root@gohan ~]# hosted-engine --add-console-password* > *Enter password:* > > *You can now connect the hosted-engine VM with VNC at 192.168.x.x:5900* > > VNCing with the above gives me the blank black screen and a cursor (See > attached). I cant do anything on that screen. > OK, I can suggest to to power off the engine VM with hosted-engine --vm-poweroff and then start it again with hosted-engine --vm-start in order to follow the whole boot process over VNC > > > Please help > > > > On Mon, Feb 25, 2019 at 11:34 AM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >> >> >> On Mon, Feb 25, 2019 at 10:27 AM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: >> >>> Hi Simone, >>> >>> Thank you for your response. Executing the command below, gives this: >>> >>> [root@ovirt-host]# curl http://$(grep fqdn /etc/ovirt-hosted-engine/hosted-engine.conf >>> | cut -d= -f2)/ovirt-engine/services/health >>> curl: (7) Failed to connect to engine.sanren.ac.za:80; No route to host >>> >>> I tried to enable http traffic on the ovirt-host, but the error persists >>> >> >> Run, on your hosts, >> getent ahosts engine.sanren.ac.za >> >> and ensure that it got resolved as you wish. >> Fix name resolution and routing on your hosts in a coherent manner. >> >> > > -- > Regards, > Sakhi Hadebe > > Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR > > Tel: +27 12 841 2308 <+27128414213> > Fax: +27 12 841 4223 <+27128414223> > Cell: +27 71 331 9622 <+27823034657> > Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> > >

1 0

[oVirt 4.3.1 Test Day] cmdline HE Deployment
by Guillaume Pavese 25 Feb '19

25 Feb '19

He deployment with "hosted-engine --deploy" fails at TASK [ovirt.hosted_engine_setup : Get local VM IP] See following Error : 2019-02-25 12:46:50,154+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Get local VM IP] 2019-02-25 12:55:26,823+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {u'_ansible_parsed': True, u'stderr_lines': [], u'cmd': u"virsh -r net-dhcp-leases default | grep -i 00 :16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", u'end': u'2019-02-25 12:55:26.666925', u'_ansible_no_log': False, u'stdout': u'', u'changed': True, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u"virsh -r net-dhcp-leases default | grep -i 00:16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'std in': None}}, u'start': u'2019-02-25 12:55:26.584686', u'attempts': 50, u'stderr': u'', u'rc': 0, u'delta': u'0:00:00.082239', u'stdout_lines': []} 2019-02-25 12:55:26,924+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:3e:fe:28 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.082239", "end": "2019-02-25 12:55:26.666925", "rc": 0, "start": "2019-02-25 12:55:26.584686", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

3 5

Gluster - performance.strict-o-direct and other performance tuning in different storage backends
by Leo David 25 Feb '19

25 Feb '19

Hello Everyone, As per some previous posts, this "performance.strict-o-direct=on" setting caused trouble or poor vm iops. I've noticed that this option is still part of default setup or automatically configured with "Optimize for virt. store" button. In the end... is this setting a good or a bad practice for setting the vm storage volume ? Does it depends ( like maybe other gluster performance options ) on the storage backend: - raid type / jbod - raid controller cache size I am usually using jbod disks attached to lsi hba card ( no cache ). Any gluster recommendations regarding this setup ? Is there any documentation for best practices on configurating ovirt's gluster for different types of storage backends ? Thank you very much ! Have a great week, Leo -- Best regards, Leo David

2 2

Problem deploying self-hosted engine on ovirt 4.3.0
by matteo fedeli 25 Feb '19

25 Feb '19

after several attempts I managed to install and deploying the ovel gluster but during the self-hosted engine deploy stuck on [INFO] TASK ["oVirt.engine-setup: Install oVirt Engine package"] for 30 minutes ... How to safely interrupt ? I let it go on while I look at some logs?

2 4

[oVirt 4.3.1 Test Day] Cockpit HE Deployment
by Guillaume Pavese 25 Feb '19

25 Feb '19

As indicated on Trello, HE deployment though cockpit is stuck at the beginning with "Please correct errors before moving to next step", but no Error is explicitly shown or highlighted. Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Unable to change cluster and data center compatibility version
by Jonathan Mathews 25 Feb '19

25 Feb '19

Good Day I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run into an issue where I am unable to change the cluster and data center compatibility version. I get the following error in the GUI: Ovirt: Some of the hosts still use legacy protocol which is not supported by cluster 3.6 or higher. In order to change it a host needs to be put to maintenance and edited in advanced options section. This error was received with all VM's off and all hosts in maintenance. The environment has the following currently installed: Engine - CentOS 7.4 - Ovirt Engine 3.6.7.5 Host1 - CentOS 6.9 - VDSM 4.16.30 Host2 - CentOS 6.9 - VDSM 4.16.30 Host3 - CentOS 6.9 - VDSM 4.16.30 I also have the following from engine.log [root@ovengine ~]# tail -f /var/log/ovirt-engine/engine.log 2018-09-22 07:11:33,920 INFO [org.ovirt.engine.core.vdsbroker.VmsStatisticsFetcher] (DefaultQuartzScheduler_Worker-93) [7533985f] Fetched 0 VMs from VDS 'd82a026c-31b4-4efc-8567-c4a6bdcaa826' 2018-09-22 07:11:34,685 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-99) [4b7e3710] FINISH, DisconnectStoragePoolVDSCommand, log id: 1ae6f0a9 2018-09-22 07:11:34,687 INFO [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] Running command: DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2018-09-22 07:11:34,706 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] START, DisconnectStorageServerVDSCommand(HostName = ovhost3, StorageServerConnectionManagementVDSParameters:{runAsync='true', hostId='d82a026c-31b4-4efc-8567-c4a6bdcaa826', storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageType='NFS', connectionList='[StorageServerConnections:{id='3fdffb4c-250b-4a4e-b914-e0da1243550e', connection='172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='4d95c8ca-435a-4e44-86a5-bc7f3a0cd606', connection='172.16.0.20:/data/ov-export', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='82ecbc89-bdf3-4597-9a93-b16f3a6ac117', connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}, StorageServerConnections:{id='29bb3394-fb61-41c0-bb5a-1fa693ec2fe2', connection='172.16.0.11:/raid1/data/_NAS_NFS_Exports_/iso', iqn='null', vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 48c5ffd6 2018-09-22 07:11:34,991 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-99) [2a6aa6f6] FINISH, DisconnectStorageServerVDSCommand, return: {3fdffb4c-250b-4a4e-b914-e0da1243550e=0, 29bb3394-fb61-41c0-bb5a-1fa693ec2fe2=0, 82ecbc89-bdf3-4597-9a93-b16f3a6ac117=0, 4d95c8ca-435a-4e44-86a5-bc7f3a0cd606=0}, log id: 48c5ffd6 2018-09-22 07:11:56,367 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-29) [1a31cc53] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:12:41,017 WARN [org.ovirt.engine.core.bll.storage.UpdateStoragePoolCommand] (default task-29) [efd285b] CanDoAction of action 'UpdateStoragePool' failed for user admin@internal. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS 2018-09-22 07:13:15,717 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-6) [4c9f3ee8] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:15:21,460 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-28) [649bae65] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:18:44,633 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-8) [23167cfd] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION 2018-09-22 07:24:20,372 WARN [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (default task-15) [5d2ce633] CanDoAction of action 'UpdateVdsGroup' failed for user admin@internal. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_WRONG_PROTOCOL_FOR_CLUSTER_VERSION I would appreciate some advice in resolving this. Thanks

3 5

Problem with snapshots in illegal status
by Bruno Rodriguez 25 Feb '19

25 Feb '19

Hello, We are experiencing some problems with some snapshots in illegal status generated with the python API. I think I'm not the only one, and that is not a relief but I hope someone can help about it. I'm a bit scared because, for what I see, the creation date in the engine for every snapshot is way different from the date when it was really created. The name of the snapshot is in the format backup_snapshot_YYYYMMDD-HHMMSS, but as you can see in the following examples, the stored date is totally random... Size Creation Date Snapshot Description Status Disk Snapshot ID 33 GiB Mar 2, 2018, 5:03:57 PM backup_snapshot_20190217-011645 Illegal 5734df23-de67-41a8-88a1-423cecfe7260 33 GiB May 8, 2018, 10:02:56 AM backup_snapshot_20190216-013047 Illegal f649d9c1-563e-49d4-9fad-6bc94abc279b 10 GiB Feb 21, 2018, 11:10:17 AM backup_snapshot_20190217-010004 Illegal 2929df28-eae8-4f27-afee-a984fe0b07e7 43 GiB Feb 2, 2018, 12:55:51 PM backup_snapshot_20190216-015544 Illegal 4bd4360e-e0f4-4629-ab38-2f0d80d3ae0f 11 GiB Feb 13, 2018, 12:51:08 PM backup_snapshot_20190217-010541 Illegal fbaff53b-30ce-4b20-8f10-80e70becb48c 11 GiB Feb 13, 2018, 4:05:39 PM backup_snapshot_20190217-011207 Illegal c628386a-da6c-4a0d-ae7d-3e6ecda27d6d 11 GiB Feb 13, 2018, 4:38:25 PM backup_snapshot_20190216-012058 Illegal e9ddaa5c-007d-49e6-8384-efefebb00aa6 11 GiB Feb 13, 2018, 10:52:09 AM backup_snapshot_20190216-012550 Illegal 5b6db52a-bfe3-45f8-b7bb-d878c4e63cb4 55 GiB Jan 22, 2018, 5:02:29 PM backup_snapshot_20190217-012659 Illegal 7efe2e7e-ca24-4b27-b512-b42795c79ea4 When I'm getting the logs for the first one, to check what happened to it, I get the following 2019-02-17 01:16:45,839+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-100) [96944daa-c90a-4ad7-a556-c98e66550f87] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', ignoreFailoverLimit='false', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageSizeInBytes='32212254720', volumeFormat='COW', newImageId='fa154782-0dbb-45b5-ba62-d6937259f097', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='5734df23-de67-41a8-88a1-423cecfe7260', sourceImageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f'}), log id: 497c168a 2019-02-17 01:18:26,506+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] START, GetVolumeInfoVDSCommand(HostName = hood13.pic.es, GetVolumeInfoVDSCommandParameters:{hostId='0a774472-5737-4ea2-b49a-6f0ea4572199', storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageId='5734df23-de67-41a8-88a1-423cecfe7260'}), log id: 111a34cf 2019-02-17 01:18:26,764+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Successfully added Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') for image transfer command '11104d8c-2a9b-4924-96ce-42ef66725616' 2019-02-17 01:18:27,310+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.AddImageTicketVDSCommand] (default task-212) [19f00d3e-5159-48aa-b3a0-615a085b62d9] START, AddImageTicketVDSCommand(HostName = hood11.pic.es, AddImageTicketVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e', ticketId='0d389c3e-5ea5-4886-8ea7-60a1560e3b2d', timeout='300', operations='[read]', size='35433480192', url='file:///rhev/data-center/mnt/blockSD/e655abce-c5e8-44f3-8d50-9fd76edf05cb/images/c5cc464e-eb71-4edf-a780-60180c592a6f/5734df23-de67-41a8-88a1-423cecfe7260', filename='null'}), log id: f5de141 2019-02-17 01:22:28,898+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Renewing transfer ticket for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:26:33,588+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Renewing transfer ticket for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:26:49,319+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Finalizing successful transfer for Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:27:17,771+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hood11.pic.es command TeardownImageVDS failed: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/5734df23-de67-41a8-88a1-423cecfe7260 in use.\', \' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/fa154782-0dbb-45b5-ba62-d6937259f097 in use.\']\\ne655abce-c5e8-44f3-8d50-9fd76edf05cb/[\'5734df23-de67-41a8-88a1-423cecfe7260\', \'fa154782-0dbb-45b5-ba62-d6937259f097\']",)',) 2019-02-17 01:27:17,772+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Command 'TeardownImageVDSCommand(HostName = hood11.pic.es, ImageActionsVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e'})' execution failed: VDSGenericException: VDSErrorException: Failed in vdscommand to TeardownImageVDS, error = Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/5734df23-de67-41a8-88a1-423cecfe7260 in use.\', \' Logical volume e655abce-c5e8-44f3-8d50-9fd76edf05cb/fa154782-0dbb-45b5-ba62-d6937259f097 in use.\']\\ne655abce-c5e8-44f3-8d50-9fd76edf05cb/[\'5734df23-de67-41a8-88a1-423cecfe7260\', \'fa154782-0dbb-45b5-ba62-d6937259f097\']",)',) 2019-02-17 01:27:19,204+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-6) [e73bfbec-d6bd-40e5-8009-97e6005ad1d4] START, MergeVDSCommand(HostName = hood11.pic.es, MergeVDSCommandParameters:{hostId='79cbda85-35f4-44df-b309-01b57bc2477e', vmId='addd5eba-9078-41aa-9244-fe485aded951', storagePoolId='fa64792e-73b3-4da2-9d0b-f334422aaccf', storageDomainId='e655abce-c5e8-44f3-8d50-9fd76edf05cb', imageGroupId='c5cc464e-eb71-4edf-a780-60180c592a6f', imageId='fa154782-0dbb-45b5-ba62-d6937259f097', baseImageId='5734df23-de67-41a8-88a1-423cecfe7260', topImageId='fa154782-0dbb-45b5-ba62-d6937259f097', bandwidth='0'}), log id: 1d956d48 2019-02-17 01:27:29,923+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-49) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Transfer was successful. Download disk 'vm.example.com_Disk1' (id '5734df23-de67-41a8-88a1-423cecfe7260') 2019-02-17 01:27:30,997+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-46) [19f00d3e-5159-48aa-b3a0-615a085b62d9] Successfully transferred disk '5734df23-de67-41a8-88a1-423cecfe7260' (command id '11104d8c-2a9b-4924-96ce-42ef66725616') For what I understand, there was a "Cannot deactivate logical volume" problem that I would thank very much if someone can help me about how to solve Thanks again -- Bruno Rodríguez Rodríguez "Si algo me ha enseñado el tetris, es que los errores se acumulan y los triunfos desaparecen"

2 5

VM creation using python api specifying an appropriate timezone
by ckennedy288＠gmail.com 25 Feb '19

25 Feb '19

Hi, I'm looking for a way to accurately specify the timezone of a VM at VM creation time. At the moment all VMs that get created using a simple in-house python script are set with a GMT timezone e.g.: if ( "windows" in OS ): vm_tz="GMT Standard Time" else: vm_tz="Etc/GMT" Is there a better way to choose a more appropriate timezone based on the VMs global location? is there a way to get a list of ovirt supported time zones for Windows and Linux and compare that with the VMs location and OS type and then choose an appropriate timezone?

1 0

Info about AD integration and Root CA
by Gianluca Cecchi 25 Feb '19

25 Feb '19

Hello, in docs for 4.2 RHV (I think it applies to oVirt 4.2 too) for attaching to AD there is the statement " To set up secure connection between the LDAP server and the Manager, ensure a PEM- encoded CA certificate has been prepared. See Section D.2, “Setting Up Encrypted Communication between the Manager and an LDAP Server” for more information. " and in Appendix " To set up encrypted communication between the Red Hat Virtualization Manager and an LDAP server, obtain the root CA certificate of the LDAP server. . . " and in readme file referred in the Appendix (/usr/share/doc/ovirt-engine-extension-aaa-ldap-1.3.8/README) there is the command: " Active Directory Windows: > certutil -ca.cert myrootca.der Linux: $ openssl -in myrootca.der -inform DER -out myrootca.pem " In my case on Windows DC (that is a Windows 2012 R2 server with "Domain functional level: Windows Server 2003") I get this error: C:\Users\Administrator.MYDOMAIN>certutil -ca.cert mydomain.der CertUtil: The system cannot find the file specified. C:\Users\Administrator.MYDOMAIN> What does it mean exactly? Thanks in advance, Gianluca

2 2

HostedEngine Unreachable
by Sakhi Hadebe 25 Feb '19

25 Feb '19

Hi, Our cluster was running fine, until we moved it to the new network. Looking at the agent.log file, it stills pings the old gateway. Not sure if this is the reason it's failing the liveliness check. Please help. On Thu, Feb 21, 2019 at 4:39 PM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi, > > I need some help. We had a working ovirt cluster in the testing > environment. We have just moved it to the production environment with the > same network settings. The only thing we changed is the public VLAN. In > production we're using a different subnet. > > The problem is we can't get the HostedEngine Up. It does come up but it > fails the LIVELINESS CHECK and its health status is bad. We can't ping even > ping it. It is on the same subnet as host machines: 192.168.x.x/24: > > *HostedEngine VM status:* > > [root@garlic qemu]# hosted-engine --vm-status > > > --== Host 1 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : goku.sanren.ac.za > Host ID : 1 > Engine status : {"reason": "vm not running on this > host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 57b2ece9 > local_conf_timestamp : 8463 > Host timestamp : 8463 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=8463 (Thu Feb 21 16:32:29 2019) > host-id=1 > score=3400 > vm_conf_refresh_time=8463 (Thu Feb 21 16:32:29 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > > > --== Host 2 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : garlic.sanren.ac.za > Host ID : 2 > Engine status : {"reason": "failed liveliness check", > "health": "bad", "vm": "up", "detail": "Powering down"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 71dc3daf > local_conf_timestamp : 8540 > Host timestamp : 8540 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=8540 (Thu Feb 21 16:32:31 2019) > host-id=2 > score=3400 > vm_conf_refresh_time=8540 (Thu Feb 21 16:32:31 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineStop > stopped=False > timeout=Thu Jan 1 04:24:29 1970 > > > --== Host 3 status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : gohan.sanren.ac.za > Host ID : 3 > Engine status : {"reason": "vm not running on this > host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 49645620 > local_conf_timestamp : 5480 > Host timestamp : 5480 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=5480 (Thu Feb 21 16:32:22 2019) > host-id=3 > score=3400 > vm_conf_refresh_time=5480 (Thu Feb 21 16:32:22 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > You have new mail in /var/spool/mail/root > > The service are running but with errors: > *vdsmd.service:* > [root@garlic qemu]# systemctl status vdsmd > ● vdsmd.service - Virtual Desktop Server Manager > Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor > preset: enabled) > Active: active (running) since Thu 2019-02-21 16:12:12 SAST; 3min 31s > ago > Process: 40117 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh > --post-stop (code=exited, status=0/SUCCESS) > Process: 40121 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh > --pre-start (code=exited, status=0/SUCCESS) > Main PID: 40224 (vdsmd) > Tasks: 47 > CGroup: /system.slice/vdsmd.service > ├─40224 /usr/bin/python2 /usr/share/vdsm/vdsmd > └─40346 /usr/libexec/ioprocess --read-pipe-fd 65 > --write-pipe-fd 64 --max-threads 10 --max-queued-requests 10 > > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running nwfilter > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: libvirt: > Network Filter Driver error : Requested operation is not valid: nwfilter is > in use > Feb 21 16:12:11 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running dummybr > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running tune_system > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running test_space > Feb 21 16:12:12 garlic.sanren.ac.za vdsmd_init_common.sh[40121]: vdsm: > Running test_lo > Feb 21 16:12:12 garlic.sanren.ac.za systemd[1]: Started Virtual Desktop > Server Manager. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN MOM not available. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN MOM not available, > KSM stats will be missing. > Feb 21 16:12:13 garlic.sanren.ac.za vdsm[40224]: WARN Not ready yet, > ignoring event '|virt|VM_status|e2608f14-39fe-4ab6-b6be-9c60679e8c76' > args={'e2608f14-39fe-4ab6-b6be-9c606..., 'type': ' > Hint: Some lines were ellipsized, use -l to show in full. > > *libvirtd.service:* > [root@garlic qemu]# systemctl status libvirtd > ● libvirtd.service - Virtualization daemon > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; > vendor preset: enabled) > Drop-In: /etc/systemd/system/libvirtd.service.d > └─unlimited-core.conf > Active: active (running) since Thu 2019-02-21 16:06:50 SAST; 9min ago > Docs: man:libvirtd(8) > https://libvirt.org > Main PID: 38485 (libvirtd) > Tasks: 17 (limit: 32768) > CGroup: /system.slice/libvirtd.service > └─38485 /usr/sbin/libvirtd --listen > > Feb 21 16:06:50 garlic.sanren.ac.za systemd[1]: Starting Virtualization > daemon... > Feb 21 16:06:50 garlic.sanren.ac.za systemd[1]: Started Virtualization > daemon. > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: info : libvirt version: 3.9.0, package: > 14.el7_5.8 (CentOS BuildSystem <http://bugs.c...centos.org) > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: info : hostname: garlic.sanren.ac.za > Feb 21 16:07:43 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:07:43.033+0000: 38485: error : virNetSocketReadWire:1808 : End of file > while reading data: Input/output error > Feb 21 16:12:08 garlic.sanren.ac.za libvirtd[38485]: 2019-02-21 > 14:12:08.791+0000: 38485: error : virNetSocketReadWire:1808 : End of file > while reading data: Input/output error > Hint: Some lines were ellipsized, use -l to show in full. > > *ovirt-ha-broker & ovirt-ha-agent services:* > [root@garlic qemu]# systemctl restart ovirt-ha-broker > ^[[A[root@garlic qemu]# systemctl status ovirt-ha-broker > ● ovirt-ha-broker.service - oVirt Hosted Engine High Availability > Communications Broker > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; > enabled; vendor preset: disabled) > Active: active (running) since Thu 2019-02-21 16:18:43 SAST; 30s ago > Main PID: 41493 (ovirt-ha-broker) > Tasks: 13 > CGroup: /system.slice/ovirt-ha-broker.service > ├─41493 /usr/bin/python > /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker > ├─41688 /bin/sh /usr/sbin/hosted-engine --check-liveliness > └─41689 python -m ovirt_hosted_engine_setup.check_liveliness > > Feb 21 16:18:43 garlic.sanren.ac.za systemd[1]: Started oVirt Hosted > Engine High Availability Communications Broker. > Feb 21 16:18:43 garlic.sanren.ac.za systemd[1]: Starting oVirt Hosted > Engine High Availability Communications Broker... > [root@garlic qemu]# systemctl status ovirt-ha-agent > ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability > Monitoring Agent > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; > enabled; vendor preset: disabled) > Active: active (running) since Thu 2019-02-21 16:18:53 SAST; 25s ago > Main PID: 41581 (ovirt-ha-agent) > Tasks: 2 > CGroup: /system.slice/ovirt-ha-agent.service > └─41581 /usr/bin/python > /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent > > Feb 21 16:18:53 garlic.sanren.ac.za systemd[1]: Started oVirt Hosted > Engine High Availability Monitoring Agent. > Feb 21 16:18:53 garlic.sanren.ac.za systemd[1]: Starting oVirt Hosted > Engine High Availability Monitoring Agent... > > Attached are logs of files that might contain some useful information to > troubleshoot. > > > Your assistance will be highly appreciated > > -- > Regards, > Sakhi Hadebe > > Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR > > Tel: +27 12 841 2308 <+27128414213> > Fax: +27 12 841 4223 <+27128414223> > Cell: +27 71 331 9622 <+27823034657> > Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za> > > -- Regards, Sakhi Hadebe Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR Tel: +27 12 841 2308 <+27128414213> Fax: +27 12 841 4223 <+27128414223> Cell: +27 71 331 9622 <+27823034657> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za>

2 3