October 2020 - Users - oVirt List Archives

user role
by kim.kargaard＠noroff.no 08 Oct '20

08 Oct '20

Hi all, For a group of users added to ovirt through AD, which role should one add to an ISO for the group to be able to select an ISO when creating VM's in the VM portal? Thanks. Kim

2 1

[ANN] oVirt 4.4.3 Fourth Release Candidate is now available for testing
by Lev Veyde 08 Oct '20

08 Oct '20

oVirt 4.4.3 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Fourth Release Candidate for testing, as of October 8th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.4.3/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Re: Is it possible to backup stopped vm? (ovirt 4.4)
by Eyal Shenitzky 08 Oct '20

08 Oct '20

Hi Lukaz, Backup using the new incremental backup API is supported only for running VMs. On Thu, 8 Oct 2020 at 12:36, Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > While trying to backup stopped VM (with POST on > /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got > the response: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <fault> > <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</ > detail> > <reason>Operation Failed</reason> > </fault> > > I found here: > https://www.ovirt.org/develop/release-management/features/storage/increment… > that it should be possible to back up a virtual machine that is not running. > *"If the VM is not running, the system will create a paused, stripped-down > version of the VM, with only backup disks attached, and use libvirt API to > start and stop the backup."* > If you will read until the end of the paragraph you will see that the support for this deferred at this time- We considered alternative solution using qemu-nbd, but According to Eric Blake qemu-nbd does not support yet exposing bitmap info, so we would not be able to provide the change block list. Since creating special paused VM for backing up non-running VM is a lot of work, we may defer support for backing up non-running VMs. > > But it doesn't seem to work. > > Regards, > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QGUVJW5HWQG6W… > -- Regards, Eyal Shenitzky

1 0

oVirt documentation updates
by Sandro Bonazzola 08 Oct '20

08 Oct '20

The oVirt documentation team updated the following guides: - Administration Guide <https://ovirt.org/documentation/administration_guide/> - Data Warehouse Guide <https://ovirt.org/documentation/data_warehouse_guide/> - Disaster Recovery Guide <https://ovirt.org/documentation/disaster_recovery_guide/> - Virtual Machine Management Guide <https://ovirt.org/documentation/virtual_machine_management_guide/> Thanks, -- 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.* * <https://www.redhat.com/it/forums/emea/italy-track>*

1 0

Re: Upgrade Host Compatibility Version
by jb 07 Oct '20

07 Oct '20

Sorry, last time I didn't answer to the mailing list... Here are the output: *CentOS Linux release 8.2.2004 (Core)* I use the kernel-plus, because of an old raid controller. Can this be a problem? ** Jonathan * * * * Am 07.10.20 um 13:21 schrieb Dana Elfassy: > Thanks Jonathan > Can you tell me what is the OS version of the host that you're using? > (cat /etc/redhat-release) > > Dana > > On Mon, Oct 5, 2020 at 4:31 PM jb <jonbae77(a)gmail.com > <mailto:jonbae77@gmail.com>> wrote: > > Hello Dana, > > I added a second host, and tried again, without success. > > The error is unspecific, it just says: *Upgrade of cluster default > failed.* > > Here the engine.log > > > Jonathan > > > > * > * > > Am 05.10.20 um 11:00 schrieb Dana Elfassy: >> Hi Jonathan, >> What is the error you're getting when you're trying to upgrade >> using the upgrade guide? >> Can you also attach the engine log? >> (/var/log/ovirt-engine/engine.log) >> Thanks, >> Dana >> >> On Sun, Oct 4, 2020 at 6:54 PM jb <jonbae77(a)gmail.com >> <mailto:jonbae77@gmail.com>> wrote: >> >> Hello everybody, >> >> for some days I upgrade our environment from ovirt 4.3 to >> 4.4.2 and now >> I stuck on upgrading the host compatibility version. It show >> there a >> compatibility until version 4.4. The VMs have a limit until >> version 4.5 >> and the cluster shows to that I can upgrade them until 4.5. >> >> On the cluster page is also a Upgrade guide, but this fails >> when I try >> that one. At the moment I have only one host to upgrade (no >> hosted >> engine)... >> >> Thanks for helping! >> >> Jonathan >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email to users-leave(a)ovirt.org >> <mailto:users-leave@ovirt.org> >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> <https://www.ovirt.org/privacy-policy.html> >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/OULJ2FCU3CLFQ… >> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OULJ2FCU3CLFQ…> >>

2 2

oVirt Survey Autumn 2020
by Sandro Bonazzola 07 Oct '20

07 Oct '20

As we continue to develop oVirt 4.4, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. Please help us to hit the mark by completing this short survey. The survey will close on October 18th 2020. If you're managing multiple oVirt deployments with very different use cases or very different deployments you can consider answering this survey multiple times. *Please note the answers to this survey will be publicly accessible*. This survey is under oVirt Privacy Policy available at https://www.ovirt.org/site/privacy-policy.html . The survey is available https://forms.gle/bPvEAdRyUcyCbgEc7 -- 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.*

3 4

ldap auth problem after upgrade from 4.4.1 to 4.4.2
by Jiří Sléžka 07 Oct '20

07 Oct '20

Hi, I just upgraded my HE to 4.4.2 but now I cannot login using my ldap aaa profile anymore. We are using Novell/NetIQ E-directory (load ballanced by haproxy, probably not important...) In 4.4.1 I was hit by removed TLSv1 (which is the newest protocol supported by our edir) from default crypto policies but I was able revert it by update-crypto-policies --set LEGACY after upgrade to 4.4.2 the error is server_error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) but our ldap server is reachable from ovirt, I tested it via (also ldaps and startls variants are working) ldapsearch -H ldap://ldap1.slu.cz -x -D cn=*****,ou=******,o=su -w '************' -b 'o=su' As a workaround I tried to set plain ldap protocol in profile cat /etc/ovirt-engine/aaa/CRO.properties include = <rfc2307-edir.properties> vars.server = ldap1.slu.cz vars.port = 389 vars.user = cn=*****,ou=******,o=su vars.password = ************** pool.default.serverset.single.server = ${global:vars.server} pool.default.serverset.single.port = ${global:vars.port} pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.ssl.startTLS = false pool.default.ssl.enable = false #pool.default.ssl.protocol = TLSv1 #pool.default.ssl.startTLSProtocol = TLSv1 #pool.default.ssl.insecure = true sequence-init.init.100-my-edir-init-vars = my-edir-init-vars sequence.my-edir-init-vars.010.description = set baseDN sequence.my-edir-init-vars.010.type = var-set sequence.my-edir-init-vars.010.var-set.variable = simple_baseDN sequence.my-edir-init-vars.010.var-set.value = o=su #search.default.search-request.derefPolicy = ALWAYS but the error is the same... ovirt-engine-extensions-tool aaa login-user --profile=CRO --user-name=my_user .... WARNING: [ovirt-engine-extension-aaa-ldap.authn::SU-LDAP-authentication] TLS/SSL insecure mode ... WARNING: [ovirt-engine-extension-aaa-ldap.authn::auth.CRO.slu.cz] Cannot initialize LDAP framework, deferring initialization. Error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) ... INFO: API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='CRO' user='my_user' Password: ... WARNING: [ovirt-engine-extension-aaa-ldap.authn::auth.CRO.slu.cz] Cannot initialize LDAP framework, deferring initialization. Error: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) Oct 01, 2020 10:57:37 AM org.ovirt.engine.exttool.core.ExtensionsToolExecutor main SEVERE: An error occurred while attempting to connect to server ldap1.slu.cz:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap1.slu.cz/193.84.206.212:389: SocketException(Network is unreachable (connect failed)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb')) debug with tcpdump reveals only that connection is made and there are only "bindRequest" and "bindResponse success" messages visible (with correct tcp handshake and close) and nothing more any help would be appreciated Cheers, Jiri

4 8

engine-setup in 4.4.2 not using yum/dnf proxy?
by Gianluca Cecchi 07 Oct '20

07 Oct '20

Hello, I'm testing upgrade from 4.3.10 to 4.4.2 for a standalone manager with local database environment. I configured the new engine system as a CentOS 8.2 with a proxy in /etc/yum.conf (that is a link to /etc/dnf/dnf.com) and that worked for all the steps until engine-setup. Now I get this [root@ovmgr1 ~]# 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-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20201006112458-p84x9i.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloading CentOS-8 - AppStream 0.00/0.00KB [ INFO ] DNF Downloaded CentOS-8 - AppStream [ INFO ] DNF Errors during downloading metadata for repository 'AppStream': .... [ ERROR ] Execution of setup failed and I see in netstat during the phase tcp 0 1 10.4.192.43:33418 18.225.36.18:80 SYN_SENT so it seems it is not using the proxy. Do I have to put proxy info into any other file? Thanks, Gianluca

2 2

Upgrade oVirt from 4.3.10 to 4.4.2 and AD users
by Gianluca Cecchi 06 Oct '20

06 Oct '20

Hello, I'm upgrading a standalone engine with local database and with 3 hosts from oVirt 4.3.10 to 4.4.2 and I'm cross checking both oVirt and RHV documents. In my oVirt environment I have integration with AD for web admin access. Inside RHV upgrade guide docs there is this statement regarding manager upgrade: " Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine. # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j NOTE The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process. " In my case I had ovirt-engine-extension-aaa-ldap and ovirt-engine-extension-aaa-misc installed on 4.3.10. So after "engine-backup --mode=restore ...." command I executed: [root@ovmgr1 ~]# yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc Last metadata expiration check: 0:01:11 ago on Tue 06 Oct 2020 11:23:04 AM CEST. Dependencies resolved. ========================================================================================== Package Arch Version Repository Size ========================================================================================== Installing: ovirt-engine-extension-aaa-ldap noarch 1.4.1-1.el8 ovirt-4.4 127 k ovirt-engine-extension-aaa-misc noarch 1.1.0-1.el8 ovirt-4.4 37 k Installing dependencies: unboundid-ldapsdk noarch 4.0.14-2.el8 ovirt-4.4-centos-ovirt44 4.0 M Transaction Summary ========================================================================================== Install 3 Packages Total download size: 4.2 M Installed size: 4.5 M and followed the next upgrade flow steps. After finishing the engine upgrade with the "engine-setup" step, it seems actually that I can still connect to my engine with my AD accounts, so that I don't have to do any manual step described... Does it match any one other experience? Gianluca

2 1

oVirt Node 4.4.2 is now generally available
by Sandro Bonazzola 06 Oct '20

06 Oct '20

oVirt Node 4.4.2 is now generally available The oVirt project is pleased to announce the general availability of oVirt Node 4.4.2 , as of September 25th, 2020. This release completes the oVirt 4.4.2 release published on September 17th Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.2 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.2 (redeploy in case of already being on 4.4.2). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt Node 4.4.2 Release? oVirt Node has been updated, including: - oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/ - Ansible 2.9.13: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Advanced Virtualization 8.2.1 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ - 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.4.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4/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.*

6 27