- Users - oVirt List Archives

Upgrade success story (4.3.0->4.3.3)
by Juhani Rautiainen 13 May '19

13 May '19

Hi! Just wanted to let you know that I succesfully upgrade our cluster to 4.3.3 (FC SAN based system and no Gluster). I postponed upgrade a lot because of the difficulties I had when upgrading from 4.2.8->4.3.0. This time Hosted Engine upgrade went without any problems. The first node also upgraded itself from admin UI without any problems. The second node was different story. I couldn't upgrade it because yum complained about missing packages. This was mysterious as I just had upgraded the other node. I bypassed this by taking ovirt-4.3 repos from other node since diffing files gave results that they differed. After that node upgraded from UI but went missing after reboot. Contacting it via ILO I found out that it had turned to DHCP again (which it never should do). Somehow settings in VDSM persistent settings were still wrong and pointing to DHCP (it has always been in fixed address). Fixed this by hand by using vdsm persistent settings from the running node. Now the node reboots reliably. Anyway thanks for all the good work oVirt people put in. Small problems here and there but it's getting better by the release. -Juhani

1 0

Node losing management network address?
by Juhani Rautiainen 13 May '19

13 May '19

Hi! I had weird occurence in my two node ovirt cluster today (I have HE). I noticed that one node had ovirtmgmt network unsynchronized. I tried to resynchronize it. This led the node being rebooted by HP ILO. After reboot the node came up with DHCP address. Tried to change it back by fixing ifcfg-ovirtmgmt to original static address. It reverter back to DHCP if I tried the resync the network. I decided to remove HE from the node in order to remove the node in order to be able to add it back. After I started HE removal, address popped back to static address. I did upgrade which was pending on node and after reboot it came back with DHCP address again. After this I removed the node from the cluster, added it back and now it seems to work. I'm just wondering how I prevent this from happening again? How this unsync situation happens for instance and why it decides that DHCP is the way to go? -Juhani

5 11

VMs import over slow 1gig interface instead of fast 10gig interface?
by Jacob Green 13 May '19

13 May '19

Ok, so I want to try and more thoroughly explain my situation. I want to better understand what is happening, and if there is a way to force import over the faster connection. Today I have two Ovirt environments, one on 4.1 and one on 4.2, on the new environment we have migrated to new VLANs for Management and Data. The export domain is a NFS domain hosted on a Trunas device that has an ip address of X.X.12.100. Our host has multiple Ethernet connections, one Bonded 20Gigabit interface. That is where we have the ovirtmgmt profile. And a secondary 1 Gigabit interface that we call our VLAN12 profile or server VLAN. *The problem.... *When importing a VM from the export domain, the import is happening over the 1Gigabit interface on the VLAN12 profile. Instead of the 20gigabit Bonded interface on VLAN 100. *My understanding.... *So I probably just misunderstand how this works, but here is what I thought should happen, in the *Setup Host Network* screen for this host I have the ovirtmgmt on VLAN100 with the bonded 20Gigabit interface performing the following. "*Management, Display, Migration, VM and Default Route*." Then I have the secondary 1 Gigabit interface just doing "*VM*" on VLAN12. What I thought should happen is that anything Migration related "*/Includes importing from export domain?/*" should happen on the Migration interface, which in my case is the ovritmgmt interface on VLAN100. I have also confirmed that I can ping from the VLAN100 ovirtmgmt interface to the storage on VLAN12. So there is connectivity from that interface to the storage. What I am trying to figure out is there a way to force it to do imports over the 20Gigabit interface that resides on VLAN100 instead of the slower VLAN12 interface, that is just there for general VM connectivity. Thank you for any advice or guidance on this matter. -- Jacob Green Systems Admin American Alloy Steel

7 9

Re: OvfUpdateIntervalInMinutes restored to original value too early?
by Andreas Elvers 12 May '19

12 May '19

I suppose the /var/log/ovirt-hosted-engine-setup/engine-logs-2019-05-10T16:16:14Z/ovirt-engine/engine.log is the bootstrap engine log. It is attached. The bootstrap engine looks quite ok when glancing through the dashboard, datacenter, storage domains,… Although there are two old hosted storage domains.

1 1

Upgrade engine to 4.3.3 or setup a new engine
by Magnus Isaksson 12 May '19

12 May '19

Hello all I'm having trouble upgrading my engine to 4.3.3 from 4.2.8 The upgrade goes well, no errors but webgui wont load, it just says "waiting for engine" I have tried to set up a new machine with engine and import the DB from the old(after upgrade) still the same problem. So after quite a few tries i gave up and set up a fresh new engine 4.3.3 But can i move/migrate the hosts with running VM:s in to the new engine? In vmware vcenter it is just to add the host and all VM:s and stuff comes over, but im guessing from what ive read that it is not that simple with ovirt. Or how should i solve this? //Magnus

2 1

HostedEngine cleaned up
by Sakhi Hadebe 12 May '19

12 May '19

Hi, We have a situation where the HostedEngine was cleaned up and the VMs are no longer running. Looking at the logs we can see the drive files as: 2019-03-26T07:42:46.915838Z qemu-kvm: -drive file=/rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685,format=qcow2,if=none,id=drive-ua-b2b872cd-b468-4f14-ae20-555ed823e84b,serial=b2b872cd-b468-4f14-ae20-555ed823e84b,werror=stop,rerror=stop,cache=none,aio=native: 'serial' is deprecated, please use the corresponding option of '-device' instead I assume this is the disk was writing to before it went down. Trying to list the file gives an error and the file is not there; ls -l /rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685 Is there a way we can recover the VM's disk images ? NOTE: No HostedEngine backups -- Regards, Sakhi Hadebe

7 13

engine-setup failed in upgrade step to 4.3.2 with DNF errors on Centos 7.6
by Oliver Riesener 12 May '19

12 May '19

# engine-setup ``` [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-aio.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20190329154037-huchep.log Version: otopi-1.8.1 (otopi-1.8.1-1.el7) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloaded Extra Packages for Enterprise Linux 7 - x86_64 [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- Set up Cinderlib integration (Currently in tech preview) (Yes, No) [No]: [ INFO ] ovirt-provider-ovn already installed, skipping. --== PACKAGES ==-- [ INFO ] Checking for product updates... [ ERROR ] DNF 'Base' object has no attribute '_group_persistor' [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': 'Base' object has no attribute '_group_persistor' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190329154037-huchep.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190329154107-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed What can i do ? ```

2 2

[Users] Lifecycle / upgradepath
by Sven Kieske 11 May '19

11 May '19

Hi Community, Currently, there is no single document describing supported (which means: working ) upgrade scenarios. I think the project has matured enough, to have such an supported upgradepath, which should be considered in the development of new releases. As far as I know, currently it is supported to upgrade from x.y.z to x.y.z+1 and from x.y.z to x.y+1.z but not from x.y-1.z to x.y+1.z directly. maybe this should be put together in a wiki page at least. also it would be cool to know how long a single "release" would be supported. In this context I would define a release as a version bump from x.y.z to x.y+1.z or to x+1.y.z a bump in z would be a bugfix release. The question is, how long will we get bugfix releases for a given version? What are your thoughts? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

2 1

Planned restart of production services
by Evgheni Dereveanchin 11 May '19

11 May '19

Hi everyone, I will be restarting several production systems within the following hour to apply updates. The following services may be unreachable for some period of time: - resources.ovirt.org - package repositories - jenkins.ovirt.org - CI master Package repositories will be unreachable for a short period of time. No new CI jobs will be started during this period. I will announce you once maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

[Users] Nested virtualization with Opteron 2nd generation and oVirt 3.1 possible?
by Gianluca Cecchi 11 May '19

11 May '19

Hello, I have 2 physical servers with Opteron 2nd gen cpu. There is CentOS 6.3 installed and some VM already configured on them. Their /proc/cpuinfo contains ... model name : Dual-Core AMD Opteron(tm) Processor 8222 ... kvm_amd kernel module is loaded with its default enabled nested option # systool -m kvm_amd -v Module = "kvm_amd" Attributes: initstate = "live" refcnt = "15" srcversion = "43D8067144E7D8B0D53D46E" Parameters: nested = "1" npt = "1" ... I already configured a fedora 17 VM as a oVirt 3.1 Engine I'm trying to configure another VM as oVirt 3.1 node with ovirt-node-iso-2.5.5-0.1.fc17.iso It seems I'm not able to configure so that ovirt install doesn't complain. After some attempts, I tried this in my vm.xml for the cpu: <cpu mode='custom' match='exact'> <model fallback='allow'>athlon</model> <vendor>AMD</vendor> <feature policy='require' name='pni'/> <feature policy='require' name='rdtscp'/> <feature policy='force' name='svm'/> <feature policy='require' name='clflush'/> <feature policy='require' name='syscall'/> <feature policy='require' name='lm'/> <feature policy='require' name='cr8legacy'/> <feature policy='require' name='ht'/> <feature policy='require' name='lahf_lm'/> <feature policy='require' name='fxsr_opt'/> <feature policy='require' name='cx16'/> <feature policy='require' name='extapic'/> <feature policy='require' name='mca'/> <feature policy='require' name='cmp_legacy'/> </cpu> Inside node /proc/cpuinfo becomes processor : 3 vendor_id : AuthenticAMD cpu family : 6 model : 2 model name : QEMU Virtual CPU version 0.12.1 stepping : 3 microcode : 0x1000065 cpu MHz : 3013.706 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext fxsr_opt lm nopl pni cx16 hypervisor lahf_lm cmp_legacy cr8_legacy bogomips : 6027.41 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: 2 questions: 1) Is there any combination in xml file to give to my VM so that oVirt doesn't complain about missing hardware virtualization with this processor? 2) suppose 1) is not possible in my case and I still want to test the interface and try some config operations to see for example the differences with RHEV 3.0, how can I do? At the moment this complaint about hw virtualization prevents me to activate the node. I get Installing Host f17ovn01. Step: RHEV_INSTALL. Host f17ovn01 was successfully approved. Host f17ovn01 running without virtualization hardware acceleration Detected new Host f17ovn01. Host state was set to Non Operational. Host f17ovn01 moved to Non-Operational state. Host f17ovn01 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : CpuFlags Can I lower the requirements to be able to operate without hw virtualization in 3.1? Thanks in advance, Gianluca

2 1