- Users - oVirt List Archives

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

Re: Is it possible to backup stopped vm? (ovirt 4.4)
by Nir Soffer 06 Oct '20

06 Oct '20

On Tue, Oct 6, 2020 at 4:08 PM Ł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> Yes, this is not supported now. > 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." This is a possible solution we considered, but it is not implemented yet. The next line is: 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. We got a request to implement this from other backup vendor, and we are discussing the possible solutions with platform folks. Nir

1 0

Is it possible to backup stopped vm? (ovirt 4.4)
by Łukasz Kołaciński 06 Oct '20

06 Oct '20

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." But it doesn't seem to work. Regards, Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [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.

1 0

Re: OVN Geneve tunnels not been established
by Konstantinos Betsis 06 Oct '20

06 Oct '20

I did a restart of the ovn-controller, this is the output of the ovn-controller.log 2020-09-11T10:54:07.566Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2020-09-11T10:54:07.568Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2020-09-11T10:54:07.568Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2020-09-11T10:54:07.570Z|00004|main|INFO|OVS IDL reconnected, force recompute. 2020-09-11T10:54:07.571Z|00005|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:07.571Z|00006|main|INFO|OVNSB IDL reconnected, force recompute. 2020-09-11T10:54:07.685Z|00007|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:07.685Z|00008|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.685Z|00009|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 2 seconds before reconnect 2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 4 seconds before reconnect 2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: continuing to reconnect in the background but suppressing further logging I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP OVIRTMGMT_NETWORK_DC This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can redo it if you wan. After the restart of the ovn-controller the OVIRT ENGINE still shows only two geneve connections one with DC01-host02 and DC02-host01. Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" hostname: "dc02-host01" Encap geneve ip: "DC02-host01_IP" options: {csum="true"} Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" hostname: "DC01-host02" Encap geneve ip: "DC01-host02" options: {csum="true"} I've re-done the vdsm-tool command and nothing changed.... again....with the same errors as the systemctl restart ovn-controller On Fri, Sep 11, 2020 at 1:49 PM Dominik Holler <dholler(a)redhat.com> wrote: > Please include ovirt-users list in your reply, to share the knowledge and > experience with the community! > > On Fri, Sep 11, 2020 at 12:12 PM Konstantinos Betsis <k.betsis(a)gmail.com> > wrote: > >> Ok below the output per node and DC >> DC01 >> node01 >> >> [root@dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE01*" >> >> node02 >> >> [root@dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE02*" >> >> DC02 >> node01 >> >> [root@dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC02-NODE01*" >> >> > Looks good. > > >> DC01 node01 and node02 share the same VM networks and VMs deployed on top >> of them cannot talk to VM on the other hypervisor. >> > > Maybe there is a hint on ovn-controller.log on dc01-node02 ? Maybe > restarting ovn-controller creates more helpful log messages? > > You can also try restart the ovn configuration on all hosts by executing > vdsm-tool ovn-config OVIRT_ENGINE_IP LOCAL_OVIRTMGMT_IP > on each host, this would trigger > > https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/setu… > internally. > > >> So I would expect to see the same output for node01 to have a geneve >> tunnel to node02 and vice versa. >> >> > Me too. > > >> On Fri, Sep 11, 2020 at 12:14 PM Dominik Holler <dholler(a)redhat.com> >> wrote: >> >>> >>> >>> On Fri, Sep 11, 2020 at 10:53 AM Konstantinos Betsis <k.betsis(a)gmail.com> >>> wrote: >>> >>>> Hi Dominik >>>> >>>> OVN is selected as the default network provider on the clusters and the >>>> hosts. >>>> >>>> >>> sounds good. >>> This configuration is required already during the host is added to oVirt >>> Engine, because OVN is configured during this step. >>> >>> >>>> The "ovn-sbctl show" works on the ovirt engine and shows only two >>>> hosts, 1 per DC. >>>> >>>> Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" >>>> hostname: "dc01-node02" >>>> Encap geneve >>>> ip: "X.X.X.X" >>>> options: {csum="true"} >>>> Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" >>>> hostname: "dc02-node1" >>>> Encap geneve >>>> ip: "A.A.A.A" >>>> options: {csum="true"} >>>> >>>> >>>> The new node is not listed (dc01-node1). >>>> >>>> When executed on the nodes the same command (ovn-sbctl show) times-out >>>> on all nodes..... >>>> >>>> The output of the /var/log/openvswitch/ovn-conntroller.log lists on all >>>> logs >>>> >>>> 2020-09-11T08:46:55.197Z|07361|stream_ssl|WARN|SSL_connect: unexpected >>>> SSL connection close >>>> >>>> >>>> >>> Can you please compare the output of >>> >>> ovs-vsctl --no-wait get open . external-ids:ovn-remote >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-type >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip >>> >>> of the working hosts, e.g. dc01-node02, and the failing host dc01-node1? >>> This should point us the relevant difference in the configuration. >>> >>> Please include ovirt-users list in your replay, to share the knowledge >>> and experience with the community. >>> >>> >>> >>>> Thank you >>>> Best regards >>>> Konstantinos Betsis >>>> >>>> >>>> On Fri, Sep 11, 2020 at 11:01 AM Dominik Holler <dholler(a)redhat.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, Sep 10, 2020 at 6:26 PM Konstantinos B <k.betsis(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi all >>>>>> >>>>>> We have a small installation based on OVIRT 4.3. >>>>>> 1 Cluster is based on Centos 7 and the other on OVIRT NG Node image. >>>>>> >>>>>> The environment was stable till an upgrade took place a couple of >>>>>> months ago. >>>>>> As such we had to re-install one of the Centos 7 node and start from >>>>>> scratch. >>>>>> >>>>> >>>>> To trigger the automatic configuration of the host, it is required to >>>>> configure ovirt-provider-ovn as the default network provider for the >>>>> cluster before adding the host to oVirt. >>>>> >>>>> >>>>>> Even though the installation completed successfully and VMs are >>>>>> created, the following are not working as expected: >>>>>> 1. ovn geneve tunnels are not established with the other Centos 7 >>>>>> node in the cluster. >>>>>> 2. Centos 7 node is configured by ovirt engine however no geneve >>>>>> tunnel is established when "ovn-sbctl show" is issued on the engine. >>>>>> >>>>> >>>>> Does "ovn-sbctl show" list the hosts? >>>>> >>>>> >>>>>> 3. no flows are shown on the engine on port 6642 for the ovs db. >>>>>> >>>>>> Does anyone have any experience on how to troubleshoot OVN on ovirt? >>>>>> >>>>>> >>>>> /var/log/openvswitch/ovncontroller.log on the host should contain a >>>>> helpful hint. >>>>> >>>>> >>>>> >>>>>> Thank you >>>>>> _______________________________________________ >>>>>> 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/LBVGLQJBWJF3E… >>>>>> >>>>>

3 30

ovirt-engine and host certification is expired in ovirt4.0
by momokch＠yahoo.com.hk 06 Oct '20

06 Oct '20

hello everyone, my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host??? i am using the ovirt 4.0 thank you

5 5

Upgrade Host Compatibility Version
by jb 05 Oct '20

05 Oct '20

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

2 1

oVirt 4.3.10 and ansible default timeouts
by Gianluca Cecchi 05 Oct '20

05 Oct '20

Hello, in the past when I was in 4.3.7 I used this file: /etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf with ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80 to bypass the default of 30 minutes at that time. I updated in steps to 4.3.8 (in February), 4.3.9 (in April) and 4.3.10 (in July). Due to an error on my side I noticed that the task for which I extended the ansible timeout (this task I didn't execute anymore in latest months) fails with timeout after 80 minutes indeed. With the intent to extend again the custom timeout I went to /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf, provided by ovirt-engine-backend-4.3.10.4-1.el7.noarch and actually I see this inside: " # Specify the ansible-playbook command execution timeout in minutes. It's used for any task, which executes # AnsibleExecutor class. To change the value permanentaly create a conf file 99-ansible-playbook-timeout.conf in # /etc/ovirt-engine/engine.conf.d/ ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=120 " and the file seems the original provided, not tampered: [root@ovmgr1 test_backup]# rpm -qvV ovirt-engine-backend-4.3.10.4-1.el7.noarch | grep virt-engine.conf$ ......... /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf [root@ovmgr1 test_backup]# So the question is: has the default intended value passed to 120 in 4.3.10 (or in any version after 4.3.7)? Thanks, Gianluca

2 1

CEPH - Opinions and ROI
by Jeremey Wise 04 Oct '20

04 Oct '20

I have for many years used gluster because..well. 3 nodes.. and so long as I can pull a drive out.. I can get my data.. and with three copies.. I have much higher chance of getting it. Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid MTBF issues ) and with VDO.. and thin provisioning.. not had issue. BUT.... gluster seems to be falling out of favor. Especially as I move towards OCP. So.. CEPH. I have one SSD in each of the three servers. so I have some space to play. I googled around.. and find no clean deployment notes and guides on CEPH + oVirt. Comments or ideas.. -- p <jeremey.wise(a)gmail.com>enguinpages.

7 8

Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way
by Kushagra Agarwal 03 Oct '20

03 Oct '20

I was hoping if i can get some help with the below oVirt scenario: *Problem Statement*:- Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way *Description*:- Do we have any ansible module or any other CLI based approach which can help us to change 'scheduler optimization' settings of cluster in oVIrt. Scheduler optimization settings of cluster can be found under Scheduling Policy tab ( Compute -> Clusters(select the cluster) -> click on edit and then navigate to scheduling policy Any help in this will be highly appreciated. Thanks, Kushagra

3 7

Question mark VMs
by Vrgotic, Marko 02 Oct '20

02 Oct '20

Hi oVIrt wizards, One of my LocalStorage hypervisors dies. VMs do not need to be rescued. As expected I see them in WebUI with question mark state (picture below): What is the step or are steps to clean ovirt engine db from these VMs and its Storage/Hypervisor/Cluster/DC? [Table Description automatically generated] Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

3 3

ovirt-engine and host certification is expired
by momokch＠yahoo.com.hk 02 Oct '20

02 Oct '20

hello everyone, my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host??? i am using the ovirt 4.0 thank you

1 0

Re: CEPH - Opinions and ROI
by Philip Brown 02 Oct '20

02 Oct '20

ceph through an iscsi gateway is very.. very.. slow. ----- Original Message ----- From: "Matthew Stier" <Matthew.Stier(a)fujitsu.com> To: "Jeremey Wise" <jeremey.wise(a)gmail.com>, "users" <users(a)ovirt.org> Sent: Wednesday, September 30, 2020 10:03:34 PM Subject: [ovirt-users] Re: CEPH - Opinions and ROI If you can’t go direct, how about round about, with an iSCSI gateway. From: Jeremey Wise <jeremey.wise(a)gmail.com> Sent: Wednesday, September 30, 2020 11:33 PM To: users <users(a)ovirt.org> Subject: [ovirt-users] CEPH - Opinions and ROI I have for many years used gluster because..well. 3 nodes.. and so long as I can pull a drive out.. I can get my data.. and with three copies.. I have much higher chance of getting it. Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid MTBF issues ) and with VDO.. and thin provisioning.. not had issue. BUT.... gluster seems to be falling out of favor. Especially as I move towards OCP. So.. CEPH. I have one SSD in each of the three servers. so I have some space to play. I googled around.. and find no clean deployment notes and guides on CEPH + oVirt. Comments or ideas.. -- [ mailto:jeremey.wise@gmail.com | p ] enguinpages. _______________________________________________ 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/S4V6NKC62LW42…

3 3

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

01 Oct '20

oVirt 4.4.3 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Third Release Candidate for testing, as of October 1st, 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

VM AutoStart
by Jeremey Wise 01 Oct '20

01 Oct '20

When I have to shut down cluster... ups runs out etc.. I need a sequence set of just a small number of VMs to "autostart" Normally I just use DNS FQND to connect to oVirt engine but as two of my VMs are a DNS HA cluster.. as well as NTP / SMTP /DHCP etc... I need those two infrastructure VMs to be auto boot. I looked at HA settings for those VMs but it seems to be watching for pause /resume.. but it does not imply or state auto start on clean first boot. Options? -- p <jeremey.wise(a)gmail.com>enguinpages

4 12

ovirt-node-4.4.2 grub is not reading new grub.cfg at boot
by Mike Lindsay 01 Oct '20

01 Oct '20

Hey Folks, I've got a bit of a strange one here. I downloaded and installed ovirt-node-ng-installer-4.4.2-2020091810.el8.iso today on an old dev laptop and to get it to install I needed to add acpi=off to the kernel boot param to get the installing to work (known issue with my old laptop). After installation it was still booting with acpi=off, no biggie (seen that happen with Centos 5,6,7 before on occasion) right, just change the line in /etc/defaults/grub and run grub2-mkconfig (ran for both efi and legacy for good measure even knowing EFI isn't used) and reboot...done this hundreds of times without any problems. But this time after rebooting if I hit 'e' to look at the kernel params on boot, acpi=off is still there. Basically any changes to /etc/default/grub are being ignored or over-ridden but I'll be damned if I can't find where. I know I'm missing something simple here, I do this all the time but to be honest this is the first Centos 8 based install I've had time to play with. Any suggestions would be greatly appreciated. The drive layout is a bit weird but had no issues running fedora or centos in the past. boot drive is a mSATA (/dev/sdb) and there is a SSD data drive at /dev/sda...having sda installed or removed makes no difference and /boot is mounted where it should /dev/sdb1....very strange Cheers, Mike [root@ovirt-node01 ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX='crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/ovirt-node-ng-4.4.2-0.20200918.0+1 rd.lvm.lv=onn/swap noapic rhgb quiet' GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true GRUB_DISABLE_OS_PROBER='true' [root@ovirt-node01 ~]# cat /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### set pager=1 if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } terminal_output console if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" set tuned_initrd="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/01_users ### if [ -f ${prefix}/user.cfg ]; then source ${prefix}/user.cfg if [ -n "${GRUB2_PASSWORD}" ]; then set superusers="root" export superusers password_pbkdf2 root ${GRUB2_PASSWORD} fi fi ### END /etc/grub.d/01_users ### ### BEGIN /etc/grub.d/08_fallback_counting ### insmod increment # Check if boot_counter exists and boot_success=0 to activate this behaviour. if [ -n "${boot_counter}" -a "${boot_success}" = "0" ]; then # if countdown has ended, choose to boot rollback deployment, # i.e. default=1 on OSTree-based systems. if [ "${boot_counter}" = "0" -o "${boot_counter}" = "-1" ]; then set default=1 set boot_counter=-1 # otherwise decrement boot_counter else decrement boot_counter fi save_env boot_counter fi ### END /etc/grub.d/08_fallback_counting ### ### BEGIN /etc/grub.d/10_linux ### insmod part_msdos insmod ext2 set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 b6557c59-e11f-471b-8cb1-70c47b0b4b29 else search --no-floppy --fs-uuid --set=root b6557c59-e11f-471b-8cb1-70c47b0b4b29 fi insmod part_msdos insmod ext2 set boot='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=boot --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 b6557c59-e11f-471b-8cb1-70c47b0b4b29 else search --no-floppy --fs-uuid --set=boot b6557c59-e11f-471b-8cb1-70c47b0b4b29 fi # This section was generated by a script. Do not modify the generated file - all changes # will be lost the next time file is regenerated. Instead edit the BootLoaderSpec files. # # The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and # populates the boot menu. Please refer to the Boot Loader Specification documentation # for the files format: https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/. set default_kernelopts="root=/dev/mapper/onn-ovirt--node--ng--4.4.2--0.20200918.0+1 ro crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/ovirt-node-ng-4.4.2-0.20200918.0+1 rd.lvm.lv=onn/swap noapic rhgb quiet " insmod blscfg blscfg ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/10_reset_boot_success ### # Hiding the menu is ok if last boot was ok or if this is a first boot attempt to boot the entry if [ "${boot_success}" = "1" -o "${boot_indeterminate}" = "1" ]; then set menu_hide_ok=1 else set menu_hide_ok=0 fi # Reset boot_indeterminate after a successful boot if [ "${boot_success}" = "1" ] ; then set boot_indeterminate=0 # Avoid boot_indeterminate causing the menu to be hidden more then once elif [ "${boot_indeterminate}" = "1" ]; then set boot_indeterminate=2 fi # Reset boot_success for current boot set boot_success=0 save_env boot_success boot_indeterminate ### END /etc/grub.d/10_reset_boot_success ### ### BEGIN /etc/grub.d/12_menu_auto_hide ### if [ x$feature_timeout_style = xy ] ; then if [ "${menu_show_once}" ]; then unset menu_show_once save_env menu_show_once set timeout_style=menu set timeout=60 elif [ "${menu_auto_hide}" -a "${menu_hide_ok}" = "1" ]; then set orig_timeout_style=${timeout_style} set orig_timeout=${timeout} if [ "${fastboot}" = "1" ]; then # timeout_style=menu + timeout=0 avoids the countdown code keypress check set timeout_style=menu set timeout=0 else set timeout_style=hidden set timeout=1 fi fi fi ### END /etc/grub.d/12_menu_auto_hide ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_ppc_terminfo ### ### END /etc/grub.d/20_ppc_terminfo ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### -- Mike Lindsay Senior Systems Administrator Technological Maintenance and Support CBC/SRC mike.lindsay(a)cbc.ca (o) 416-205-8992 (c) 416-819-2841

3 3

Power on VM - CLI / API
by Jeremey Wise 01 Oct '20

01 Oct '20

Can anyone post link. (with examples.. as most documentation for oVirt lacks this).. where I can power on a VM via CLI or API. As of now I cannot login to oVirt-Engine. No errors when I restart it.. https://lists.ovirt.org/archives/list/users@ovirt.org/thread/45KKF5TN5PRQ3R… BUt... I need to get VMs booted. I tried to follow: http://ovirt.github.io/ovirt-engine-api-model/master/ and my server's API web portal https://ovirte01.penguinpages.local/ovirt-engine/apidoc/#/documents/003_com… And.. even get POSTMAN (real newbie at that tool but ran into how to add exported .pem key from portal to session issues) # failed CLI example: Power on VM "ns01" ########### <<<< DRAFT :: 2020-09-30################ # Get key from oVirt engine and import. Ex: from ovirte01 into server 'thor curl -k ' https://ovirte01.penguinpages.local/ovirt-engine/services/pki-resource?reso…' -o ovirt01_ca.pem sudo cp ovirt01_ca.pem /etc/pki/ca-trust/source/anchors sudo update-ca-trust extract openssl s_client -connect ovirte01.penguinpages.local:443 -showcerts < /dev/null <snip... lots of key info back> # Use key during GET list of VMs ?? <meh? # Power on VM <<fubar still> curl -X POST https://ovirte01.penguinpages.local/post -H /ovirt-engine/api/vms/ns01/start HTTP/1.1 <https://ovirte01.penguinpages.local/post%20-H%20/ovirt-engine/api/vms/ns01/…> ##### I just need to power on VM -- p <jeremey.wise(a)gmail.com>enguinpages

3 2

Re: CEPH - Opinions and ROI
by penguin pages 01 Oct '20

01 Oct '20

These are all storage rich servers. Drives: USB 3 64GB Boot / OS 512GB SSD (Gluster HCI: volumes "engine", "data" , "vmstore" "iso" I added last one to .. well to learn if I could extend with LVM ;) 1TB SSD: (VDO+Gluster Manual build due to brick and fqdn issues in oVirt, It did import once it was created so that is good.. ) 1TB SSD/NVMe: (?? CEPH ?? Goal is I can learn technology and play.. but have several independent volumes where I can move important systems to / from / backup so if my playing around messes things up.. I have a fall back. I would try RedHat Container Storage.. but It is a home lab so my budget is all used up on hardware and so CentOS. I am hoping oVirt had a similar setup process like " yum install -y gluster-ansible-roles " but for CEPH. This video implies something of that ilk exists.. https://www.youtube.com/watch?v=wIw7RjHPhzs but <sigh> jumps right into setup.. and fails to mention "how did you get that plugin in cockpit"... and is their an "oVirt" version.

1 0

java.lang.reflect.UndeclaredThrowableException - oVirt engine UI
by Jeremey Wise 01 Oct '20

01 Oct '20

I tried to post on website but .. it did not seem to work... so sorry if this is double posting. oVirt login this AM. accepted username and password but got java error. Restarted oVirt engine ## hosted-engine --set-maintenance --mode=global hosted-engine --vm-shutdown hosted-engine --vm-status #make sure that the status is shutdown before restarting hosted-engine --vm-start hosted-engine --vm-status #make sure the status is health before leaving maintenance mode hosted-engine --set-maintenance --mode=none ## [root@thor ~]# hosted-engine --vm-status --== Host thor.penguinpages.local (id: 1) status ==-- Host ID : 1 Host timestamp : 65342 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : thor.penguinpages.local Local maintenance : False stopped : False crc32 : 824c29fd conf_on_shared_storage : True local_conf_timestamp : 65342 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=65342 (Wed Sep 30 08:11:45 2020) host-id=1 score=3400 vm_conf_refresh_time=65342 (Wed Sep 30 08:11:45 2020) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host medusa.penguinpages.local (id: 3) status ==-- Host ID : 3 Host timestamp : 87556 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : medusa.penguinpages.local Local maintenance : False stopped : False crc32 : 63296a70 conf_on_shared_storage : True local_conf_timestamp : 87556 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=87556 (Wed Sep 30 08:11:39 2020) host-id=3 score=3400 vm_conf_refresh_time=87556 (Wed Sep 30 08:11:39 2020) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False [root@thor ~]# yum update -y Last metadata expiration check: 0:31:17 ago on Wed 30 Sep 2020 09:17:03 AM EDT. Dependencies resolved. Nothing to do. Complete! [root@thor ~]# Gogled around .. just found this thread. ## https://bugzilla.redhat.com/show_bug.cgi?id=1378045 # pgadmin connect to ovirte01.penguinpages.com as engine to db engine select mac_addr from vm_interface "00:16:3e:57:0d:47" "56:6f:86:41:00:01" "56:6f:86:41:00:00" "56:6f:86:41:00:02" "56:6f:86:41:00:03" "56:6f:86:41:00:04" "56:6f:86:41:00:05" "56:6f:86:41:00:15" "56:6f:86:41:00:16" "56:6f:86:41:00:17" "56:6f:86:41:00:18" "56:6f:86:41:00:19" # Note one field is "null" Question: 1) is this bad? 2) How do I fix? 3) Any idea on root cause? -- p <jeremey.wise(a)gmail.com>enguinpages

3 2

Gluster Volumes - Correct Peer Connection
by Jeremey Wise 01 Oct '20

01 Oct '20

I just noticed when HCI setup bult the gluster engine / data / vmstore volumes... it did use correctly the definition of 10Gb "back end" interfaces / hosts. But.. oVirt Engine is NOT referencing this. it lists bricks as 1Gb "managment / host" interfaces. Is this a GUI issue? I doubt this and how do I correct it? ### Data Volume Example Name: data Volume ID: 0ae7b487-8b87-4192-bd30-621d445902fe Volume Type: Replicate Replica Count: 3 Number of Bricks: 3 Transport Types: TCP Maximum no of snapshots: 256 Capacity: 999.51 GiB total, 269.02 GiB used, 730.49 GiB free, 297.91 GiB Guaranteed free, 78 Deduplication/Compression savings (%) medusa.penguinpages.local medusa.penguinpages.local:/gluster_bricks/data/data 25% OK odin.penguinpages.local odin.penguinpages.local:/gluster_bricks/data/data 25% OK thor.penguinpages.local thor.penguinpages.local:/gluster_bricks/data/data 25% OK # I have storage back end of 172.16.101.x which is 10Gb dedicated for replication. Peers reflect this [root@odin c4918f28-00ce-49f9-91c8-224796a158b9]# gluster peer status Number of Peers: 2 Hostname: thorst.penguinpages.local Uuid: 7726b514-e7c3-4705-bbc9-5a90c8a966c9 State: Peer in Cluster (Connected) Hostname: medusast.penguinpages.local Uuid: 977b2c1d-36a8-4852-b953-f75850ac5031 State: Peer in Cluster (Connected) [root@odin c4918f28-00ce-49f9-91c8-224796a158b9]# -- p <jeremey.wise(a)gmail.com>enguinpages

5 7