- Users - oVirt List Archives

Strange behavior when changing memory and virtual cpu for VM
by matthias.barmeier＠sourcepark.de 06 Feb '19

06 Feb '19

Hi, after creating a VM from a template everything works fine. After a while I would like to increase memory and cpus. I changed the memory and virtual cpu settings in the "System" settings. I restarted the VM. From this moment on the VM hangs on boot with this messages filling the console: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' Connection to 169.254.169.254 timed out. This goes on for ever. What can I do to make the VM work again ? I tried to restore the settings to the values it has before but this does not help. The VM contains debian 9 (stretch) with cloud init. Ovirt version: 4.2.7.5-1.el7 Ciao Matze

4 4

But in the web interface?
by Hetz Ben Hamo 06 Feb '19

06 Feb '19

Hi, I upgraded to 4.3 and on the hosted engine web interface, I see the "dashboard" button twice, one below the other. How can I fix it or is it a known bug? Thanks Hetz

7 14

Re: Changing CPU type from Opteron G3 to Epyc with hosted engine in 4.3
by Simone Tiraboschi 06 Feb '19

06 Feb '19

On Wed, Feb 6, 2019 at 11:02 AM Juhani Rautiainen < juhani.rautiainen(a)gmail.com> wrote: > On Wed, Feb 6, 2019 at 11:27 AM Juhani Rautiainen > <juhani.rautiainen(a)gmail.com> wrote: > > > > On Wed, Feb 6, 2019 at 10:31 AM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > > > > > > The only case that could prevent that is that you are in hosted-engine > mode and so you cannot set the latest host into maintenance mode without > loosing the engine itself. > > > > > > If this is your case, > > > what you can do is: > > > - set HE global maintenance mode > > > - set one of the hosted-engine hosts into maintenance mode > > > - move it to a different cluster > > > - shutdown the engine VM > > > - manually restart the engine VM on the host on the custom cluster > directly executing on that host: hosted-engine --vm-start > > > - connect again to the engine > > > - set all the hosts of the initial cluster into maintenance mode > > > - upgrade the cluster > > > - shut down again the engine VM > > > - manually restart the engine VM on one of the hosts of the initial > cluster > > > - move back the host that got into a temporary cluster to its initial > cluster > > > > I might try this one. > > I tried this one and it worked. There was problem with couple of VM's > (they were made from OVA from Virtualbox). It couldn't upgrade old > cluster until they were moved to temporary cluster too (complaining > about wrong cluster level). It might have been the real reason why the > normal upgrade failed? Maybe the error message was wrong? > Thanks for the report, honestly I have to double check it because it looks a bit suspicious. I also think that an addition to https://github.com/oVirt/ovirt-ansible-cluster-upgrade to handle also the upgrade of the hosted-engine cluster making it smoother could make a lot of sense. > > Thanks a lot, > Juhani >

1 0

Changing CPU type from Opteron G3 to Epyc with hosted engine in 4.3
by Juhani Rautiainen 06 Feb '19

06 Feb '19

Hi! Now that I have engine and nodes on 4.3 level I'm stuck on upgrading the CPU type. I have 2 node cluster with Epyc processors. It was originally installed with 4.2 so it chose CPU type as Opteron G3 (no Epyc support back then). In Engine 4.3 Epyc is available as CPU type when I choose Compatibility Version: 4.3. Big problem is that it doesn't allow to upgrade CPU because all hosts are not in maintenance: "Error while executing action: Cannot change Cluster CPU type unless all Hosts attached to this Cluster are in Maintenance". Putting all hosts to maintenance is impossible because Engine is hosted in the cluster. I tried with Global HA maintenance, but that didn't help. What is the correct way to solve this problem? Thanks, -Juhani

2 3

Issue when adding new hypervisor to cluster
by Jonas Lindholm 06 Feb '19

06 Feb '19

Background: We had an issue when an operator decided to just install Windows on a running oVirt hypervisor with VMs running. Somehow the Windows installation somehow corrupted some of the storage metadata for one storage domain (The storage domain could not be activated, activation failed after ~5 minutes each time I tried). I was able to move all disks on that storage domain except two to another a new storage domain so all important data was saved. After data was moved I removed the corrupted storage domain from the cluster/datacenter with no issues. I then destroyed the storage domain. The existing hypervisors in the cluster can reboot without any issues with the existing storage domains. So far so good. Issue: However when I try to add an additional hypervisor to the cluster I get an error referencing the corrupted storage domain (UUID is for the bad one that no longer exists). My question is where can the reference still be, in the DB or in any active data structure the hypervisors are using? if it is in the DB I guess some clever SQL statement might be able to remove it but if that's the case I would need help with those SQL statements. Thanks /Jonas *********************************************************** CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient and may constitute non-public information. Personal data in this email is governed by our Privacy Policy at http://business.nasdaq.com/privacy-statement unless explicitly excluded from it; please see the section in the policy entitled “Situations Where This Privacy Policy Does Not Apply” for circumstances where different privacy terms govern emailed personal data. If you received this e-mail in error, disclosing, copying, distributing or taking any action in reliance of this e-mail is strictly prohibited and may be unlawful. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive any work product or other applicable legal privilege(s) by the transmission of this message. ***********************************************************

1 0

rebooting an ovirt cluster
by feral 05 Feb '19

05 Feb '19

How is an oVirt hyperconverged cluster supposed to come back to life after a power outage to all 3 nodes? Running ovirt-node (ovirt-node-ng-installer-4.2.0-2019013006.el7.iso) to get things going, but I've run into multiple issues. 1. During the gluster setup, the volume sizes I specify, are not reflected in the deployment configuration. The auto-populated values are used every time. I manually hacked on the config to get the volume sizes correct. I also noticed if I create the deployment config with "sdb" by accident, but click back and change it to "vdb", again, the changes are not reflected in the config. My deployment config does seem to work. All volumes are created (though the xfs options used don't make sense as you end up with stripe sizes that aren't a multiple of the block size). Once gluster is deployed, I deploy the hosted engine, and everything works. 2. Reboot all nodes. I was testing for power outage response. All nodes come up, but glusterd is not running (seems to have failed for some reason). I can manually restart glusterd on all nodes and it comes up and starts communicating normally. However, the engine does not come online. So I figure out where it last lived, and try to start it manually through the web interface. This fails because vdsm-ovirtmgmt is not up. I figured out the correct way to start up the engine would be through the cli via hosted-engine --vm-start. This does work, but it takes a very long time, and it usually starts up on any node other than the one I told it to start on. So I guess two (or three) questions. What is the expected operation after a full cluster reboot (ie: in the event of a power failure)? Why doesn't the engine start automatically, and what might be causing glusterd to fail, when it can be restarted manually and works fine? -- _____ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people.

6 10

Version 4.3.0 installed, but shows 4.2.8
by arturo＠somosespeciales.com 05 Feb '19

05 Feb '19

Hi: I just made a new installation from scratch since the last version of oVirt (ovirt-node-ng-installer-4.3.0-2019020409.el7.iso) and at the end of the installation and entering the cockpit, appears that the version is 4.2.8. Here is a screenshot: https://drive.google.com/uc?export=download&id=1muIsMPeiMYi-FN4Y4NTxSfQ-EeV… Any ideas? Thanks in advance. Greetings

1 2

oVirt 4.3 node-ng host kernel options for nvidia vGPU
by Edward Berger 05 Feb '19

05 Feb '19

Hi, One of our projects wants to try offering VMs with nvidia vGPU. My co-worker had some problems before, so I thought I'd try the latest 4.3 ovirt-node-ng. In the "Edit Host" -> kernel dialog I see two promising checkbox options Hostdev Passthrough & SR-IOV (which adds to kernel line intel_iommu=on) and Blacklist Nouveau (which adds to kernel line rdblacklist=nouveau) but they seem to be acting as mutually exclusive options, when both are selected the kernel command line box is outlined in red and I can't continue on. Am I wrong to want both options?

1 0

Host compatibility issue after upgrade from 4.2.8 to 4.3.0
by ronjero＠gmail.com 05 Feb '19

05 Feb '19

I have a three node (hyper converged) cluster, all hosts are identical hardware wise, however after the upgrade one of the three is getting kicked out of the cluster with the following error: Host is compatible with versions (3.6,4.0,4.1,4.2) and cannot join Cluster... The hosts have SandyBridge processors but do have SSBD: CPU Type: Intel SandyBridge IBRS SSBD Family. virsh -r capabilities | grep ssbd <feature name='ssbd'/> The only other thing I should mention is that I *may* have change the cluster compatibly level to 4.3 while this particular node was in maintenance mode (don't know if that has any influence on this issue). Any help getting this node back into the cluster would be greatly appreciated. Ron.

3 4

ERROR running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode
by mhumaj＠gmail.com 05 Feb '19

05 Feb '19

Hi, We run ovirt upgrade to 4.3, after upgrade we wanted to run engine-setup but we do not know how to put this host which is simply another virtual machine with ovirt-engine. hosted-engine is running on hosts. During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode. In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data. [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup detected, but Global Maintenance is not set. [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190205121802-l7llrw.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190205121855-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed from the hosted nodes --== Host 2 status ==-- Host ID : 2 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Can anyone please tell me how to put the global maintenance on virtual machine where the ovirt-engine is? not the hosts even if I put them on the global maintenance I am unable to run engine-setup on vm with ovirt-enging. thanks

2 1