May 2019 - Users - oVirt List Archives

[Urgent] USB passthrough
by Juan Pablo Lorier 08 May '19

08 May '19

Hi, I'm trying to attach an USB device to a VM but although the host detects the USB device (is shown in lsusb), the host device tab in the VM is not showing that device. It show all other but not that one. Is there something I should do to update ovrit host devices? Regards

1 0

Re: Creating Thin-provisioned disks on a gluster volume
by Strahil 08 May '19

08 May '19

I have already opened a bug for that. If you are not in a hurry - postpone the migration. Best Regards, Strahil NikolovOn May 8, 2019 00:49, Dmitry Filonov <filonov(a)hkl.hms.harvard.edu> wrote: > > Hi - > We want to migrate our aging oVirt cluster to a new one and decided to go for the hyperconverged setup with Gluster and hosted engine. Got 3 new machines, set everything up, did a test VM migration and were almost ready to do final migration of our VMs when I notice one really weird thing. > When migrating VMs from NFS storage onto Gluster they stay thin provisioned. But if I try creating new disk image from the oVirt GUI - I get preallocated volume. No matter if I select "thin provision" or "Preallocated" I always get preallocated volume created. > > The engine.log says - > 2019-05-07 17:14:20,562-04 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default task-20) [bbd94792-2f86-44eb-9334-807dd44d0742] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{storagePoolId='43550c2c-7100-11e9-9b45-00163e4babb7', ignoreFailoverLimit='false', storageDomainId='1de2f7ac-ee52-43fb-89ac-f86b62f73b9a', imageGroupId='86c5c5e9-6533-4caf-a5a5-401556a5059a', imageSizeInBytes='21474836480', volumeFormat='RAW', newImageId='470b8035-9380-408d-a644-96e8d74c4e8e', imageType='Preallocated', newImageDescription='{"DiskAlias":"test","DiskDescription":""}', imageInitialSizeInBytes='0'}), log id: 228ddfd5 > > Is there any tweak I didn't notice to make things actually what it suppose to be doing? > > oVirt 4.3.3.5-1.el7 > glusterfs 5.5-1.el7 > CentOS Linux release 7.6.1810 > > Thank you! > > -- > Dmitry Filonov > Linux Administrator > SBGrid Core | Harvard Medical School > 250 Longwood Ave, SGM-114 > Boston, MA 02115

1 0

Best arquitecture for 2 location
by raul.caballero.girol＠gmail.com 08 May '19

08 May '19

Hi everybody, I have 2 location separate geographically. I want to deploy an ovirt installation. Evary location has 3 host with a storage system. What is the best arquitecture for this scenario?. My problem is that I don know how to recover the manager if its storage is down. With a backup/recover? How I remove the old manager when I recover the storage? Cheers

2 4

Creating Thin-provisioned disks on a gluster volume
by Dmitry Filonov 07 May '19

07 May '19

Hi - We want to migrate our aging oVirt cluster to a new one and decided to go for the hyperconverged setup with Gluster and hosted engine. Got 3 new machines, set everything up, did a test VM migration and were almost ready to do final migration of our VMs when I notice one really weird thing. When migrating VMs from NFS storage onto Gluster they stay thin provisioned. But if I try creating new disk image from the oVirt GUI - I get preallocated volume. No matter if I select "thin provision" or "Preallocated" I always get preallocated volume created. The engine.log says - 2019-05-07 17:14:20,562-04 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default task-20) [bbd94792-2f86-44eb-9334-807dd44d0742] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{storagePoolId='43550c2c-7100-11e9-9b45-00163e4babb7', ignoreFailoverLimit='false', storageDomainId='1de2f7ac-ee52-43fb-89ac-f86b62f73b9a', imageGroupId='86c5c5e9-6533-4caf-a5a5-401556a5059a', imageSizeInBytes='21474836480', volumeFormat='RAW', newImageId='470b8035-9380-408d-a644-96e8d74c4e8e',* imageType='Preallocated', *newImageDescription='{"DiskAlias":"test","DiskDescription":""}', imageInitialSizeInBytes='0'}), log id: 228ddfd5 Is there any tweak I didn't notice to make things actually what it suppose to be doing? oVirt 4.3.3.5-1.el7 glusterfs 5.5-1.el7 CentOS Linux release 7.6.1810 Thank you! -- Dmitry Filonov Linux Administrator SBGrid Core | Harvard Medical School 250 Longwood Ave, SGM-114 Boston, MA 02115

2 2

Hosted engine restore went very wrong
by Andreas Elvers 07 May '19

07 May '19

I really feel like an idiot. I tried to move our hosted engine from our Default datacenter to our Ceph Datacenter. I ran intro problems which were correctly addressed. see: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/ZFCLFWRN6XR6KM… It was in case a race condition. I was able to bring back the engine to our Default Cluster. And then I tried to do the move again to our Ceph Datacenter. I got the error "The target Data Center does not contain the Virtual Disk" twice yesterday. Because it was late, I decided to do it in the next morning. I did a new backup from the engine. Copied it over to the new node of the Ceph Datacenter and started the hosted-engine --deploy. But I FORGET TO SHUTDOWN the other engine! Oh man. The deploy script errored out with: [ ERROR ] fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} [ ERROR ] fatal: [localhost -> engine.infra.solutions.work]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned accord Then I realised something was different this time. I shutdown and undefined the Local Engine. The node is now in a degraded state. Is it possible to start the deployment again on a degraded node? I started the old engine again, but I'm not able to reach the login page. Any Idea what to do next?

1 5

Re: All Windows vms report "Actual timezone in guest doesn't match configuration"
by michael＠wanderingmad.com 07 May '19

07 May '19

I got my questions mixed up, restarting guest services does nothing.

6 9

vm_dynamic table very big in ovirt engine db
by Nardus Geldenhuys 07 May '19

07 May '19

Hi There Hope you are well. We have two clusters with two ovirt-engines. On the one cluster's ovirt -engine the vm_dynamic tables is almost 3.5 GB big, is that normal ? We are on the latest engine software. Regards Nar

1 0

Host has available update for ovirt-host, but nothing found
by Gianluca Cecchi 07 May '19

07 May '19

I have 4.3.3 on engine and hosts in 4.3.3 with plain CentOS, updated from 4.3.2 on 2/5. Since the day after, 3/5, I get the event Check for available updates on host ov200 was completed successfully with message 'found updates for packages ovirt-host'. and also the icon at side of host in web admin gui. But: [root@ov200 ~]# yum update Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos, subscription-manager, : vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Repository centos-sclo-rh-release is listed more than once in the configuration Loading mirror speeds from cached hostfile * base: centos.mirror.garr.it * epel-util: epel.besthosting.ua * extras: centos.mirror.garr.it * ovirt-4.3: ftp.nluug.nl * ovirt-4.3-epel: epel.besthosting.ua * updates: centos.mirror.garr.it No packages marked for update [root@ov200 ~]# [root@ov200 ~]# rpm -q ovirt-host package ovirt-host is not installed [root@ov200 ~]# yum search ovirt-host: ===================================== N/S matched: ovirt-host ====================================== ovirt-host-deploy-common.noarch : Commong files for ovirt-host-deploy ovirt-host-deploy-java.noarch : ovirt-host-deploy java support ovirt-host-deploy-javadoc.noarch : Javadocs for ovirt-host-deploy ovirt-host.x86_64 : Track required packages for oVirt hosts ovirt-host-dependencies.x86_64 : This meta package pulls in all the dependencies needed for minimal : oVirt hosts. ovirt-hosted-engine-ha.noarch : oVirt Hosted Engine High Availability Manager ovirt-hosted-engine-setup.noarch : oVirt Hosted Engine setup tool python2-ovirt-host-deploy.noarch : oVirt host deploy tool This is not an oVirt-NG host, but plain CentOS.... What to do? Do I have to install the ovirt-host package anyway? Thanks in advance, Gianluca

2 4

silent install failing in 4.3.3.5-1 due to question on fqdn of host
by Brian Kircher 07 May '19

07 May '19

Anyone happen to know if I can get the following into an answer file for a silent deployment? It’s asking to confirm or change from the fqdn of the host doing the HE install. Default is fine, but I have to connect in to the screen to answer this before it will continue. Default hostname changed to generic in below log. Forward and reverse are both working via dns. QUESTION/1/OVESETUP_NETWORK_FQDN_first_HE 019-04-30 18:56:38,802-0500 DEBUG otopi.context context.dumpEnvironment:745 ENVIRONMENT DUMP - END 2019-04-30 18:56:38,804-0500 DEBUG otopi.context context._executeMethod:127 Stage validation METHOD otopi.plugins.gr_he_common.network<http://otopi.plugins.gr_he_common.network> .bridge.Plugin._validate_hostname_first_host 2019-04-30 18:56:38,806-0500 DEBUG otopi.plugins.gr_he_common.network<http://otopi.plugins.gr_he_common.network> .bridge dialog.queryEnvKey:90 queryEnvKey called for key OVEHOSTED_NETWORK/host_name 2019-04-30 18:56:38,806-0500 DEBUG otopi.plugins.otopi.dialog.human human.queryString:159 query OVESETUP_NETWORK_FQDN_first_HE 2019-04-30 18:56:38,807-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Please provide the hostname of this host on the management network [ host01.domain.com<http://host01.domain.com> ]: Version 4.3.3.5<http://4.3.3.5>-1.el7 Thanks, Brian ________________________________ This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.

3 4

Re: Best arquitecture for 2 location
by Strahil 07 May '19

07 May '19

You may use gluster with geo-replucation, but that doesn't support gluster updates from remote to local side, so the second location is your DR site and nothing else should be running. Maybe Simone/Sahina can clarify the ovirt part of the setup. Best Regards, Strahil NikolovOn May 6, 2019 18:15, raul.caballero.girol(a)gmail.com wrote: > > Hi everybody, > > I have 2 location separate geographically. I want to deploy an ovirt installation. Evary location has 3 host with a storage system. What is the best arquitecture for this scenario?. My problem is that I don know how to recover the manager if its storage is down. With a backup/recover? How I remove the old manager when I recover the storage? > > Cheers > _______________________________________________ > 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/O2TACPYDX3OYK…

1 0

replaced ovirt certs, now i'm locked out with unable to find valid certification path
by michael＠wanderingmad.com 06 May '19

06 May '19

I followed the guide here to replace the self-signed certs with 3rd party certs, and now i'm getting this error on signin: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target do i need to have the .p12 in place also? I extracted the .key and .cer from the existing PFX, and copied them to all the places in the article, renaming the .cer to .pem as neded and I always get that error. Yes, I did copy to the java directory and ran the program to update the trust store, and I can list out the trust store and see it listed. Has there been a recent change in how it handles certs? I tried it with the blank password for the certstore, with "changeit" and also changing the password to "123456" and none work.

2 5

Problem with restoring engine
by Andreas Elvers 06 May '19

06 May '19

Hello today I tried to migrate the hosted engine from our Default Datacenter (NFS) to our Ceph Datacenter. The deployment worked with the automatic "hosted-engine --deploy --restore-from-file=backup/file_name" command. Perfect. Only thing is: I messed up with the cluster name. The name should be Luise01 but I entered Luise1. Duh... Now I want to bring the engine back to the Default Datacenter. Easy thing. Just repeat the same steps again. 1. Enable global ha maintenenace 2. Stop and disable the engine 3. create the engine backup 4 ... continue with all the steps from chapter 13.1.8 RHEV Docs 4.3 Beta. Everything looked great. The ansible playbook was running, then asking for the storage domain. I entered the NFS path. It got registered, but then the ansible playbook errors out with [ INFO ] TASK [ovirt.hosted_engine_setup : Add VM] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Cannot attach Virtual Disk. The target Data Center does not contain the Virtual Disk.]". HTTP response code is 409. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot attach Virtual Disk. The target Data Center does not contain the Virtual Disk.]\". HTTP response code is 409."} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources I see that there is a bug report on https://bugzilla.redhat.com/show_bug.cgi?id=1649424 Any idea how to get around this error ? Additionally I now have a HostedEngineLocal (shut off) on that node... How do I remove it? engine-cleanup ? Have to get some sleep. best regards.

2 2

NonResponsive Host and unknown VMs
by Alexis Grillon 06 May '19

06 May '19

Hello, Context : (probably) After a failed deletion of snapshot during a backup (it had been somes times since i got this problem), one of my host has gone Nonresponsive, and with him, all the VMs who was stored on it or run on it. Instead of removing the problem snapshot (usually it does the trick). I did reboot the host (and without maintenance, it wasn't available) On the Host log, it seems there's nothing wrong, on the Engine log, there's mostly a "ERROR [org.ovirt.engine.core.dal.dbbroker. auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM xxx command Get Host Capabilities failed: Message timeout which can be caused by communication issues", without further informations. One last thing, it seems gluster is working well but the command "gluster volume status" goes timeout (nothing from log seems wrong) Of course, the host ping from the engine, and the engine ping from the host. You'll find on the bottom of the mail more informations about the setup. Here are a few questions if someone can help : - Should i open a bug on that (looks a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1404082 but i can't do all the test of this bug) ? - Should i be worried about the gluster timeout (the engine is on it) / should i move the gluster point of the unresponsive host on another, and remove the unresponsive host from the pool to fix that ? - i guess that if i fix the unresponsivness of the host, it'll fix the vm (that one is an easy one i hope !) - Once i will have found why the host is unresponsive, and if i can't fix it (have to reinstall it by example), how can i remove the host and the affected vms from the cluster (nearly everything is unavailable on them, maintenance for storage and host are unavailable) ? Any help will be greatly appreciated, thank you. Informations about the setup : ovirt 4.2.8.2 Gluster has been created on system before the installation of ovirt (but is well working this way). Mostly, storage of VMs are made with NFS mount on host, not on a gluster exception made for the engine. The unresponsive host is the arbiter brick of the gluster volumes. I can wipe the unresponsive host, but the cluster is a production cluster, i can't shutdown everything :) ---- Cordialement, Alexis Grillon Pôle Humanités Numériques, Outils, Méthodes et Analyse de Données. Maison Européenne des Sciences de l'Homme et de la Société MESHS - Lille Nord de France / CNRS tel. +33 (0)3 20 12 58 57 | alexis.grillon(a)meshs.fr www.meshs.fr | 2, rue des Canonniers 59000 Lille GPG fingerprint AC37 4C4B 6308 975B 77D4 772F 214F 1E97 6C08 CD11

1 0

Cascade Lake CPU in oVirt
by Matthias Leopold 06 May '19

06 May '19

Hi, do I get it right that hypervisor hosts with Cascade Lake CPU could be used in oVirt, but would be recognized as "Skylake"? Cascade Lake specific features could only be used in VMs after CL is supported by libvirt (https://bugzilla.redhat.com/show_bug.cgi?id=1677209) and this libvirt is imported in oVirt? We're thinking about buying new hardware and I want to be sure it can be used... thx matthias

2 1

Q35 in pre 4.3 updated environments?
by Gianluca Cecchi 06 May '19

06 May '19

Hello, having some environments born before 4.3.0 and Q35 introduction. Now on 4.3.3, but of course existing VMs seem not impacted and retain their machine type, eg a dumpxml gives: <type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type> Any advise if I want to update any of them to Q35 (supposing their installed OS does support that kind of hw emulation, of course)? Apart from shutdown, edit, system, advanced parameters, change, save and boot? This question leads me to something strange I have noticed: updating cluster to 4.3, when 4.3.0 was released, seems not to have changed default "Emulated Machine" type for it. In fact if I go in my cluster, I see it still with value "pc-i440fx-rhel7.6.0", even if its compatibility version is 4.3. Is this expected? If I edit the cluster I don't see an option to change to q35. My cpu type is "Intel Westmere IBRS SSBD Family", could it influence this situation in any way? Thanks in advance, Gianluca

2 1

Migrating from RHV to ovirt
by Andrés Jiménez 06 May '19

06 May '19

Hi, all I do have a 5 hosts cluster with over 300 VMs in production with Red Hat Virtualization version 4.2.8 and I am willing to switch to a pure CentOS + oVirt 4.2 setup. Management is based in a RHVM hosted-engine in a dedicated iSCSI DataStore and our hosts are a mix of RHVH nodes (3) and CentOS with oVirt 4.2 repositories (2). I was wondering if I can just set up a new hosted-engine in a CentOS host and recover a backup of our current ovirt- engine (rhvm). Would that work straight away without affecting my running VMs? Cheers, -- Andrés Jiménez Gómez Linube e-mail: soporte(a)linube.com www.linube.com La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias

1 0

Please Help, Ovirt Node Hosted Engine Deployment Problems 4.3.2
by Todd Barton 06 May '19

06 May '19

I've having to rebuild an environment that started back in the early 3.x days. A lot has changed and I'm attempting to use the Ovirt Node based setup to build a new environment, but I can't get through the hosted engine deployment process via the cockpit (I've done command line as well). I've tried static DHCP address and static IPs as well as confirmed I have resolvable host-names. This is a test environment so I can work through any issues in deployment. When the cockpit is displaying the waiting for host to come up task, the cockpit gets disconnected. It appears to a happen when the bridge network is setup. At that point, the deployment is messed up and I can't return to the cockpit. I've tried this with one or two nic/interfaces and tried every permutation of static and dynamic ip addresses. I've spent a week trying different setups and I've got to be doing something stupid. Attached is a screen capture of the resulting IP info after my latest try failing. I used two nics, one for the gluster and bridge network and the other for the ovirt cockpit access. I can't access cockpit on either ip address after the failure. I've attempted this setup as both a single host hyper-converged setup and a three host hyper-converged environment...same issue in both. Can someone please help me or give me some thoughts on what is wrong? Thanks! Todd Barton

4 13

oVirt 4.3.3 third async update is now available
by Sandro Bonazzola 06 May '19

06 May '19

The oVirt Team has just released a new version of the following packages: - ovirt-engine-4.3.3.7 The async release includes an additional fix ( https://gerrit.ovirt.org/#/c/99738/) for Bug 1697367 <https://bugzilla.redhat.com/show_bug.cgi?id=1697367> - make SMT setting more user friendly Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Stale hosted engine node information harmful ?
by Andreas Elvers 02 May '19

02 May '19

I have 5 nodes (node01 to node05). Originally all those nodes were part of our default datacenter/cluster with a NFS storage domain for vmdisk, engine and iso-images. All five nodes were engine HA nodes. Later node01, node02 and node03 were re-installed to have engine HA removed. Then those nodes were removed from the default cluster. Eventually node01,02 and 03 were completely re-installed to host our new Ceph/Gluster based datecenter. The engine is still running on the old default Datacenter. Now I wish to move it over to our ceph/gluster datacenter. when I look at the current output of "hosted-engine --vm-status" I see: --== Host node01.infra.solutions.work (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : False Hostname : node01.infra.solutions.work Host ID : 1 Engine status : unknown stale-data Score : 0 stopped : True Local maintenance : False crc32 : e437bff4 local_conf_timestamp : 155627 Host timestamp : 155877 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=155877 (Fri Aug 3 13:09:19 2018) host-id=1 score=0 vm_conf_refresh_time=155627 (Fri Aug 3 13:05:08 2018) conf_on_shared_storage=True maintenance=False state=AgentStopped stopped=True --== Host node02.infra.solutions.work (id: 2) status ==-- conf_on_shared_storage : True Status up-to-date : False Hostname : node02.infra.solutions.work Host ID : 2 Engine status : unknown stale-data Score : 0 stopped : True Local maintenance : False crc32 : 11185b04 local_conf_timestamp : 154757 Host timestamp : 154856 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=154856 (Fri Aug 3 13:22:19 2018) host-id=2 score=0 vm_conf_refresh_time=154757 (Fri Aug 3 13:20:40 2018) conf_on_shared_storage=True maintenance=False state=AgentStopped stopped=True --== Host node03.infra.solutions.work (id: 3) status ==-- conf_on_shared_storage : True Status up-to-date : False Hostname : node03.infra.solutions.work Host ID : 3 Engine status : unknown stale-data Score : 0 stopped : False Local maintenance : True crc32 : 9595bed9 local_conf_timestamp : 14363 Host timestamp : 14362 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=14362 (Thu Aug 2 18:03:25 2018) host-id=3 score=0 vm_conf_refresh_time=14363 (Thu Aug 2 18:03:25 2018) conf_on_shared_storage=True maintenance=True state=LocalMaintenance stopped=False --== Host node04.infra.solutions.work (id: 4) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : node04.infra.solutions.work Host ID : 4 Engine status : {"health": "good", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : 245854b1 local_conf_timestamp : 317498 Host timestamp : 317498 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=317498 (Thu May 2 09:44:47 2019) host-id=4 score=3400 vm_conf_refresh_time=317498 (Thu May 2 09:44:47 2019) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False --== Host node05.infra.solutions.work (id: 5) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : node05.infra.solutions.work Host ID : 5 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 3400 stopped : False Local maintenance : False crc32 : 0711afa0 local_conf_timestamp : 318044 Host timestamp : 318044 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=318044 (Thu May 2 09:44:45 2019) host-id=5 score=3400 vm_conf_refresh_time=318044 (Thu May 2 09:44:45 2019) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False The old node01, node02 and node03 are still present. The new incarnations of node01, node02 and node03 will be the destination the the deployment of the new home of our engine to which I wish to restore the backup to. But I'm not sure, if (and how) the old date should be removed first.

2 2

oVirt 4.3.3 - servers cannot be reached
by Wood Peter 02 May '19

02 May '19

Hi, I setup AD authentication and from command line all looks good. Unfortunately, on the Web UI users sometimes login successfully but most of the times the login screen just hangs and after 2-3 min. it displays "Unable to log in because servers cannot be reached. Try again later." In engine.log I see this: 2019-05-02 11:12:11,581-07 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-72) [] EVENT_ID: USER_VDC_LOGIN_FAILED(114), User peter(a)ad.mycompany.com connecting from '10.12.29.48' failed to log in : 'Unable to log in because servers cannot be reached. Try again later.'. 2019-05-02 11:12:11,583-07 ERROR [org.ovirt.engine.core.sso.servlets.InteractiveAuthServlet] (default task-68) [] Cannot authenticate user 'peter(a)ad.mycompany.com' connecting from '10.12.29.48': Unable to log in because servers cannot be reached. Try again later. Even when my login attempt on the Web UI is hanging I can still successfully run the login test from shell: ovirt-engine-extensions-tool aaa login-user --profile=ad.mycompany.com --user-name=peter The above command never fails. That makes me wonder why am I getting the "servers cannot be reached" error? I assume the AD servers cannot be reached but from the command line it works perfect every time. Any idea what could be the problem or where to look for the error. Thank you, -- Peter

1 0

oVirt VM Table View Survey
by Sandro Bonazzola 02 May '19

02 May '19

Hi, the oVirt UX team at Red Hat would like to get your feedback on the VM table view that's featured in the admin portal. The survey will also run during Summit out of the UXD research and feedback booth. We kindly ask you to join the survey and answer at https://redhatdg.co1.qualtrics.com/jfe/form/SV_cGwhuzRUQGTXnp3 This survey is under oVirt Privacy Policy available at https://www.ovirt.org/site/privacy-policy.html -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Prevent Gluster Volume being monitored by oVirt
by smirta＠gmx.net 02 May '19

02 May '19

Dear all We are running a oVirt GlusterFS hyperconverged setup with arbiter version 4.2.6.4-1.el7 here. It looks like we are affected by this bug https://bugzilla.redhat.com/show_bug.cgi?id=1614430 with one or more gluster volumes that are not storage domains of oVirt. Is there a way to exclude them from monitoring (vdsm-gluster) or to prevent being added to the engine's database? Thanks Simon

1 0

Re: Stale hosted engine node information harmful ?
by Strahil 02 May '19

02 May '19

In a Red Hat Solution , it is recommended to restart ovirt-ha-agent & ovirt-ha-broker. I usually set the global maintenance and wait 20s-30s . Then I just stop on all nodes ovirt-ha-agent.service & ovirt-ha-broker.service . Once everywhere is stopped, start the 2 services on all nodes and wait 4-5min. Last verify the status from each host, before removing global maintenance. Best Regards, Strahil NikolovOn May 2, 2019 12:30, Andreas Elvers <andreas.elvers+ovirtforum(a)solutions.work> wrote: > > I have 5 nodes (node01 to node05). Originally all those nodes were part of our default datacenter/cluster with a NFS storage domain for vmdisk, engine and iso-images. All five nodes were engine HA nodes. > Later node01, node02 and node03 were re-installed to have engine HA removed. Then those nodes were removed from the default cluster. Eventually node01,02 and 03 were completely re-installed to host our new Ceph/Gluster based datecenter. The engine is still running on the old default Datacenter. Now I wish to move it over to our ceph/gluster datacenter. > > when I look at the current output of "hosted-engine --vm-status" I see: > > --== Host node01.infra.solutions.work (id: 1) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node01.infra.solutions.work > Host ID : 1 > Engine status : unknown stale-data > Score : 0 > stopped : True > Local maintenance : False > crc32 : e437bff4 > local_conf_timestamp : 155627 > Host timestamp : 155877 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=155877 (Fri Aug 3 13:09:19 2018) > host-id=1 > score=0 > vm_conf_refresh_time=155627 (Fri Aug 3 13:05:08 2018) > conf_on_shared_storage=True > maintenance=False > state=AgentStopped > stopped=True > > > --== Host node02.infra.solutions.work (id: 2) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node02.infra.solutions.work > Host ID : 2 > Engine status : unknown stale-data > Score : 0 > stopped : True > Local maintenance : False > crc32 : 11185b04 > local_conf_timestamp : 154757 > Host timestamp : 154856 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=154856 (Fri Aug 3 13:22:19 2018) > host-id=2 > score=0 > vm_conf_refresh_time=154757 (Fri Aug 3 13:20:40 2018) > conf_on_shared_storage=True > maintenance=False > state=AgentStopped > stopped=True > > > --== Host node03.infra.solutions.work (id: 3) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node03.infra.solutions.work > Host ID : 3 > Engine status : unknown stale-data > Score : 0 > stopped : False > Local maintenance : True > crc32 : 9595bed9 > local_conf_timestamp : 14363 > Host timestamp : 14362 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=14362 (Thu Aug 2 18:03:25 2018) > host-id=3 > score=0 > vm_conf_refresh_time=14363 (Thu Aug 2 18:03:25 2018) > conf_on_shared_storage=True > maintenance=True > state=LocalMaintenance > stopped=False > > > --== Host node04.infra.solutions.work (id: 4) status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : node04.infra.solutions.work > Host ID : 4 > Engine status : {"health": "good", "vm": "up", "detail": "Up"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 245854b1 > local_conf_timestamp : 317498 > Host timestamp : 317498 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=317498 (Thu May 2 09:44:47 2019) > host-id=4 > score=3400 > vm_conf_refresh_time=317498 (Thu May 2 09:44:47 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineUp > stopped=False > > > --== Host node05.infra.solutions.work (id: 5) status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : node05.infra.solutions.work > Host ID : 5 > Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 0711afa0 > local_conf_timestamp : 318044 > Host timestamp : 318044 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=318044 (Thu May 2 09:44:45 2019) > host-id=5 > score=3400 > vm_conf_refresh_time=318044 (Thu May 2 09:44:45 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > > > The old node01, node02 and node03 are still present. > > The new incarnations of node01, node02 and node03 will be the destination the the deployment of the new home of our engine to which I wish to restore the backup to. But I'm not sure, if (and how) the old date should be removed first. > _______________________________________________ > 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/WF5BNCWZHS2ZF…

2 1

Re: All hosts non-operational after upgrading from 4.2 to 4.3
by Strahil 02 May '19

02 May '19

Are you able to access your iSCSI via the /rhev/data-center/mnt... mount point ? Best Regards, Strahil NikolovOn Apr 5, 2019 19:04, John Florian <jflorian(a)doubledog.org> wrote: > > I am in a severe pinch here. A while back I upgraded from 4.2.8 to 4.3.3 and only had one step remaining and that was to set the cluster compat level to 4.3 (from 4.2). When I tried this it gave the usual warning that each VM would have to be rebooted to complete, but then I got my first unusual piece when it then told me next that this could not be completed until each host was in maintenance mode. Quirky I thought, but I stopped all VMs and put both hosts into maintenance mode. I then set the cluster to 4.3. Things didn't want to become active again and I eventually noticed that I was being told the DC needed to be 4.3 as well. Don't remember that from before, but oh well that was easy. > > However, the DC and SD remains down. The hosts are non-op. I've powered everything off and started fresh but still wind up in the same state. Hosts will look like their active for a bit (green triangle) but then go non-op after about a minute. It appears that my iSCSI sessions are active/logged in. The one glaring thing I see in the logs is this in vdsm.log: > > 2019-04-05 12:03:30,225-0400 ERROR (monitor/07bb1bf) [storage.Monitor] Setting up monitor for 07bb1bf8-3b3e-4dc0-bc43-375b09e06683 failed (monitor:329) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 326, in _setupLoop > self._setupMonitor() > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 348, in _setupMonitor > self._produceDomain() > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 158, in wrapper > value = meth(self, *a, **kw) > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 366, in _produceDomain > self.domain = sdCache.produce(self.sdUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce > domain.getRealDomain() > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain > return self._cache._realProduce(self._sdUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce > domain = self._findDomain(sdUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain > return findMethod(sdUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain > raise se.StorageDomainDoesNotExist(sdUUID) > StorageDomainDoesNotExist: Storage domain does not exist: (u'07bb1bf8-3b3e-4dc0-bc43-375b09e06683',) > > How do I proceed to get back operational?

2 1

Re: Fwd: [Gluster-users] Announcing Gluster release 5.5
by Strahil 02 May '19

02 May '19

Hi Darrel, Will it fix the cluster brick sudden death issue ? Best Regards, Strahil NikolovOn Mar 21, 2019 21:56, Darrell Budic <budic(a)onholyground.com> wrote: > > This release of Gluster 5.5 appears to fix the gluster 3.12->5.3 migration problems many ovirt users have encountered. > > I’ll try and test it out this weekend and report back. If anyone else gets a chance to check it out, let us know how it goes! > > -Darrell > >> Begin forwarded message: >> >> From: Shyam Ranganathan <srangana(a)redhat.com> >> Subject: [Gluster-users] Announcing Gluster release 5.5 >> Date: March 21, 2019 at 6:06:33 AM CDT >> To: announce(a)gluster.org, gluster-users Discussion List <gluster-users(a)gluster.org> >> Cc: GlusterFS Maintainers <maintainers(a)gluster.org> >> >> The Gluster community is pleased to announce the release of Gluster >> 5.5 (packages available at [1]). >> >> Release notes for the release can be found at [3]. >> >> Major changes, features and limitations addressed in this release: >> >> - Release 5.4 introduced an incompatible change that prevented rolling >> upgrades, and hence was never announced to the lists. As a result we are >> jumping a release version and going to 5.5 from 5.3, that does not have >> the problem. >> >> Thanks, >> Gluster community >> >> [1] Packages for 5.5: >> https://download.gluster.org/pub/gluster/glusterfs/5/5.5/ >> >> [2] Release notes for 5.5: >> https://docs.gluster.org/en/latest/release-notes/5.5/ >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users(a)gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users > >

9 18