August 2019 - Users - Ovirt List Archives

by Rick A

So I updated our environment a bit ago during a scheduled down time from 4.2 to 4.3. Everything went smoothly, but it looks like I forgot to update the Data Center Compatibility (See alert message below). My question is, can I just change the Data Center compatibility to 4.3 while the environment is running without causing issues, or do i need to shutdown all my VM's and put the hosts into maintenance mode? The compatibility version for everything else is already set to 4.3. Thanks Alert Message: "Data Center compatibility version is 4.2, which is lower than latest engine version 4.3. Please upgrade your Data Center to latest version to successfully finish upgrade of your setup"

5 years, 3 months

2
1
0 / 0

[ANN] oVirt 4.3.5 Fifth Release Candidate is now available for testing

by Sandro Bonazzola

The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 Fifth Release Candidate for testing, as of July 11th, 2019. While testing this release candidate please consider deeper testing on gluster upgrade since with this release we are switching from Gluster 5 to Gluster 6. This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is laready available - oVirt Node is already available[2] Additional Resources: * Read more about the oVirt 4.3.5 release highlights: http://www.ovirt.org/release/4.3.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.5/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

5 years, 3 months

3
7
0 / 0

ovirt-release43-pre-4.3.6-0.1 - python-ioprocess RPM version

by Maton, Brett

Hi, I just ran yum update on my test cluster and ran into the following issue: I did notice that the python2-ioprocess is currently installed from the ovirt-4.2 repo... Any suggestions? Thanks, Brett Repo RPM: ovirt-release43-pre-4.3.6-0.1.rc1.el7.noarch yum -y upgrade ... Error: Package: vdsm-python-4.30.25-1.el7.noarch (ovirt-4.3-pre) Requires: python-ioprocess >= 1.2.1 Installed: python2-ioprocess-1.1.2-1.el7.x86_64 (@ovirt-4.2) python-ioprocess = 1.1.2 Available: python-ioprocess-0.16.1-1.el7.noarch (ovirt-4.3-centos-ovirt43) python-ioprocess = 0.16.1-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

5 years, 3 months

2
1
0 / 0

4.3.5 update error

by Kapetanakis Giannis

Hi, Trying today engine-setup to update from 4.3.3 -> 4.3.5 I got this error: [ ERROR ] Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment In log file I see: 2019-07-31 10:43:00,375+0300 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _validation self._checkSnapshotCompatibilityVersion() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 212, in _checkSnapshotCompatibilityVersion 'v': snapshot_cl, UnboundLocalError: local variable 'snapshot_cl' referenced before assignment 2019-07-31 10:43:00,381+0300 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Setup validation': local variable 'snapshot_cl' referenced before assignment Any hints? thanks Giannis

5 years, 3 months

5
5
0 / 0

[ANN] oVirt Engine 4.3.5 async update is now available

by Sandro Bonazzola

The oVirt Team has just released a new version of ovirt-engine package that fixes one upgrade related issue.[1] We recommend to users experiencing upgrade issues to try again with this new release. Thanks, [1] https://bugzilla.redhat.com/1734699 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 years, 3 months

1
0
0 / 0

oVirt tools

by old.good.mail＠gmail.com

Greetings, After installing oVirt tools on my w2016 virtual server I've noticed that all devices (nic, disks, etc.) are connected as USB devices and I have option available to eject those devices. Is there any way to prvent those devices being ejected on behalf of VM user? (e.g. make sure noone inside the VM can actually eject nic, disk or something)

5 years, 3 months

4
4
0 / 0

[ANN] oVirt 4.3.5 second async is now available

by Sandro Bonazzola

The oVirt Team has just released a new version of the following packages: - ovirt-ansible-hosted-engine-setup-1.0.26 - ovirt-release43-4.3.5.2 The async release includes additional fixes: - Bug 1734171 <https://bugzilla.redhat.com/show_bug.cgi?id=1734171> - RHV-M 4.3.4 does not boot with fips=1 when OpenSCAP profile used resulting in non FIPS compliant certificates Notes: - oVirt Node is already available[2] oVirt Node has been updated including above packages and: - Latest CentOS Virt SIG update: - CESA-2019:1968 - Important qemu-kvm-ev Security Update Upstream details at https://access.redhat.com/errata/RHSA-2019:1968 - Latest CentOS 7.6 updates including: - CEBA-2019:1899 CentOS 7 bind BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023376.html> - CESA-2019:1880 Low CentOS 7 curl Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023377.html> - CEBA-2019:1889 CentOS 7 ipa BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023380.html> - CESA-2019:1873 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023374.html> - CEBA-2019:1895 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023393.html> - CEBA-2019:1875 CentOS 7 samba BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023397.html> - CESA-2019:1884 Moderate CentOS 7 libssh2 Security Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023383.html> - CEBA-2019:1874 CentOS 7 net-snmp BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023386.html> - CEBA-2019:1878 CentOS 7 selinux-policy BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023391.html> - CEBA-2019:1885 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023392.html> - CEEA-2019:1887 CentOS 7 sysstat Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023396.html> - CEBA-2019:1901 CentOS 7 tuned BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-July/023394.html> Additional Resources: * Read more about the oVirt 4.3.5 release highlights: http://www.ovirt.org/release/4.3.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.5/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 years, 3 months

1
0
0 / 0

Linux VM keeps crashing on copying files "with lost communication with qemu"

by kevin.doyle＠manchester.ac.uk

HI I think it is a bug with qemu, and isci disks. Has anyone else seen this issue VM crashes and lost communication with qemu Can I update qemu ? if so what is the latest support version to use on Ovirt 4.3.2.1-1.el7 Current versions of qemu installed Installed Packages qemu-img-ev.x86_64 10:2.12.0-18.el7_6.3.1 qemu-kvm-common-ev.x86_64 10:2.12.0-18.el7_6.3.1 qemu-kvm-ev.x86_64 10:2.12.0-18.el7_6.3.1 Many thanks Kevin

5 years, 3 months

2
1
0 / 0

Use public-signed SSL certs?

by Chris Adams

I installed an SSL cert from a public CA (Let's Encrypt) on my engine, following this: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/... That gets the regular web UI working, but I can't upload an ISO. I assume that I need to do something with the imageio-proxy service on the engine, but not sure what... I tried replacing imageio-proxy.cer and imageio-proxy.key.nopass, but that didn't work. I'm trying to avoid ever needing to install a special CA cert in browsers. -- Chris Adams <cma(a)cmadams.net>

5 years, 3 months

6
19
0 / 0

Re: Manual Migration not working and Dashboard broken after 4.3.4 update

by Strahil

I'm not sure, but I always thought that you need an agent for live migrations. You can always try installing either qemu-guest-agent or ovirt-guest-agent and check if live migration between hosts is possible. Have you set the new cluster/dc version ? Best Regards Strahil NikolovOn Jul 9, 2019 17:42, Neil <nwilson123(a)gmail.com> wrote: > > I remember seeing the bug earlier but because it was closed thought it was unrelated, this appears to be it.... > > https://bugzilla.redhat.com/show_bug.cgi?id=1670701 > > Perhaps I'm not understanding your question about the VM guest agent, but I don't have any guest agent currently installed on the VM, not sure if the output of my qemu-kvm process maybe answers this question?.... > > /usr/libexec/qemu-kvm -name guest=Headoffice.cbl-ho.local,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Headoffice.cbl-ho.lo/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu Broadwell,vme=on,f16c=on,rdrand=on,hypervisor=on,arat=on,xsaveopt=on,abm=on,rtm=on,hle=on -m 8192 -realtime mlock=off -smp 8,maxcpus=64,sockets=16,cores=4,threads=1 -numa node,nodeid=0,cpus=0-7,mem=8192 -uuid 9a6561b8-5702-43dc-9e92-1dc5dfed4eef -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-3.1611.el7.centos,serial=4C4C4544-0034-5810-8033-C2C04F4E4B32,uuid=9a6561b8-5702-43dc-9e92-1dc5dfed4eef -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=31,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2019-07-09T10:26:53,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/59831b91-00a5-01e4-0294-000000000018/8a607f8a-542a-473c-bb18-25c05fe2a3d4/images/56e8240c-a172-4f52-b0c1-2bddc4f34f93/9f245467-d31d-4f5a-8037-7c5012a4aa84,format=qcow2,if=none,id=drive-virtio-disk0,serial=56e8240c-a172-4f52-b0c1-2bddc4f34f93,werror=stop,rerror=stop,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -netdev tap,fd=33,id=hostnet0,vhost=on,vhostfd=34 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:5b,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,fd=35,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,fd=36,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5900,addr=10.0.1.11,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -incoming defer -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x8 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on > > Please shout if you need further info. > > Thanks. > > > > > > > On Tue, Jul 9, 2019 at 4:17 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Shouldn't cause that problem. >> >> You have to find the bug in bugzilla and report a regression (if it's not closed) , or open a new one and report the regression. >> As far as I remember , only the dashboard was affected due to new features about vdo disk savings. >>

5 years, 3 months

5
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users August 2019