- Users - oVirt List Archives

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