- Users - oVirt List Archives

Optimizing Gluster
by eevans＠digitaldatatechs.com 26 Oct '20

26 Oct '20

This article provides good information to stabilize gluster. I thought i would pass it along. https://docs.gluster.org/en/latest/Administrator%20Guide/Linux%20Kernel%20T…

2 1

Storage Domain Data (Master)
by suporte＠logicworks.pt 25 Oct '20

25 Oct '20

When data (Master) is down the others Domains data are down too? What is the best practice when a problem ocurres to the Data Master? Thansk -- Jose Ferradeira http://www.logicworks.pt

4 4

Unable to connect to postgres database on oVirt engine
by kushagra2agarwal＠gmail.com 25 Oct '20

25 Oct '20

I am unable to connect to postgres database running on oVirt engine and while troubleshooting found below possible issue. semanage fcontext -a -t postgresql_exec_t /opt/rh/rh-postgresql10/root/usr/bin/psql ValueError: File spec /opt/rh/rh-postgresql10/root/usr/bin/psql conflicts with equivalency rule '/opt/rh/rh-postgresql10/root /'; Try adding '//usr/bin/psql' instead Can someone help to resolve this issue.

3 7

VM has snapshot with disk in illegal status
by Massimo Mad 24 Oct '20

24 Oct '20

Hi, I try to delete a snapshot that i have created in the past, now in the events i have the following error: Failed to delete snapshot And the VM now has the exclamation point with the following message: VM has snapshot with disk in illegal status How i can fix this problem ? Regards Massimo

3 11

ovirt Storage Domain Cluster Filesystem?
by lsc.oraes＠gmail.com 23 Oct '20

23 Oct '20

Hi all I come from Oracle VM x86 world and we are planning from moving Oracle VM to oVirt. I am having hard time understanding Storage Domains in oVirt. All our storage are SAN and I wonder how can we manage SAN LUN in oVirt to create a storage domain such that the VM guests can run in any host in the oVirt Cluster? For example in Oracle VM the Storage Repository (it is the Storage Domain in OVM words) are based on SAN LUNs and on top of that a cluster filesystem is created so all hosts in the cluster have concurrent access to the storage repository and the VM guest can be started in any of the hosts in the cluster. How do we accomplish the same in oVirt with SAN Storage? Which Cluster Filesystem is supported in Storage Domain? Or perhaps in oVirt the mechanism is totally different? Thank you

3 6

Re: Gluster volume not responding
by Strahil Nikolov 23 Oct '20

23 Oct '20

Hi Simon, Usually it is the network, but you need real-world data. I would open screen sessions and run ping continiously . Something like this: while true; do echo -n "$(date) "; timeout -s 9 1 ping -c 1 ovirt2 | grep icmp_seq; sleep 1; done | tee -a /tmp/icmp_log Are all systems in the same network ? What about dns resolution - do you have entries in /etc/hosts ? Best Regards, Strahil Nikolov В неделя, 11 октомври 2020 г., 11:54:47 Гринуич+3, Simon Scott <simon(a)justconnect.ie> написа: Thanks Strahil. I have found between 1 & 4 Gluster peer rpc-clnt-ping timer expired messages in the rhev-data-center-mnt-glusterSD-hostname-strg:_pltfm_data01.log on the storage network IP. Of the 6 Hosts only 1 does not have these timeouts. Fencing has been disabled but can you identify which logs are key to identifying the cause please. It's a bonded (bond1) 10GB ovirt-mgmt logical network and Prod VM VLAN interface AND a bonded (bond2) 10GB Gluster storage network. Dropped packets are seen incrementing in the vdsm.log but neither ethtool -S or kernel logs are showing dropped packets. I am wondering if they are being dropped due to the ring buffers being small. Kind Regards Shimme ________________________________ From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Thursday 8 October 2020 20:40 To: users(a)ovirt.org <users(a)ovirt.org>; Simon Scott <simon(a)justconnect.ie> Subject: Re: [ovirt-users] Gluster volume not responding >Every Monday and Wednesday morning there are gluster connectivity timeouts >but all checks of the network and network configs are ok. Based on this one I make the following conclusions: 1. Issue is reoccuring 2. You most probably have a network issue Have you checked the following: - are there any ping timeouts between fuse clients and gluster nodes - Have you tried to disable fencing and check the logs after the issue reoccurs - Are you sharing Blackup and Prod networks ? Is it possible some backup/other production load in your environment to "black-out" your oVirt ? - Have you check the gluster cluster's logs for anything meaningful ? Best Regards, Strahil Nikolov _______________________________________________ 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/U527TGUQR6RV7…

2 2

New host: no network interfaces visible
by Richard Chan 23 Oct '20

23 Oct '20

What could cause no Network Interfaces visible in installing a new host? I have added a new host to oVirt 4.3.10, the initial SSH installs all the packages (all with failed=0 in host-deploy/*log). The installation is shown as failed without any meaningful message. However the Network Interfaces page is blank, what could cause this? Host in CentOS 7.8 tried with/without biosdevname. -- Richard Chan

2 3

[ANN] oVirt 4.4.3 Sixth Release Candidate is now available for testing
by Sandro Bonazzola 23 Oct '20

23 Oct '20

oVirt 4.4.3 Sixth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Sixth Release Candidate for testing, as of October 22th, 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. While upgrading from 4.4.2 to 4.4.3 RC6 You can hit: Problem: cannot install the best update candidate for package ovirt-engine-metrics-1.4.1.1-1.el8.noarch - nothing provides rhel-system-roles >= 1.0-19 needed by ovirt-engine-metrics-1.4.2-1.el8.noarch in order to get rhel-system-roles >= 1.0-19 you need https://buildlogs.centos.org/centos/8/virt/x86_64/ovirt-44/ repo since that package can be promoted to release only at 4.4.3 GA. 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/ -- 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: Ovirt 4.4/ Centos 8 issue with nfs?
by Lee Hanel 22 Oct '20

22 Oct '20

sigh. Finally got back around to this. Solved it by creating a subdirectory under the actual share and mounting that. Thanks for the help, Lee

1 0

Q: Hybrid GlusterFS / local storage setup?
by Gilboa Davara 22 Oct '20

22 Oct '20

Hello all, I'm thinking about converting a couple of old dual Xeon V2 workstations into (yet another) oVirt setup. However, the use case for this cluster is somewhat different: While I do want most of the VMs to be highly available (Via 2+1 GFS storage domain), I'd also want pin at least one "desktop" VM to each host (possibly with vGPU) and let this VM access the local storage directly in-order to get near bare metal performance. Now, I am aware that I can simply share an LVM LV over NFS / localhost and pin a specific VM to each specific host, and the performance will be acceptable, I seem to remember that there's a POSIX-FS storage domain that at least in theory should be able to give me per-host private storage. A. Am I barking at the wrong tree here? Is this setup even possible? B. If it is even possible, any documentation / pointers on setting up per-host private storage? I should mention that these workstations are quite beefy (64-128GB RAM, large MDRAID, SSD, etc) so I can spare memory / storage space (I can even split the local storage and GFS to different arrays). - Gilboa

4 10

multiple new networks
by kim.kargaard＠noroff.no 21 Oct '20

21 Oct '20

Hi all, We have Ovirt 4.3, with 11 hosts, and need a bunch of VLANs for our student's to be isolated and do specific things. We have created the VLANs on the switch, but need to create them on the admin portal, with vlan tagging and then add them to the interface on the hosts. We are talking about 400 VLANs. I have done this manually for 4 VLANs and all works fine, but was wondering if there is a way of doing this in one go for all? So I don't have to do it 400 times (at least creating the VLANs on the admin portal). Thanks. Kim

5 4

Hyperconverged Gluster Deployment in cockpit with zfs
by harryo.dk＠gmail.com 21 Oct '20

21 Oct '20

Hi, When I want to use zfs for software raid on my oVirt nodes instead of a hardware raid controller, I don't know what to type in "Device Name" I don't know if this step should be skipped for zfs raid, I don't know the location of my zfs vdev or if thre is anyhing else i should input. If I would set this up via CLI, no "Device Name" is needed in the process, why is it then nedded in the Hyperconverged Gluster Deployment on cockpit? There is plenty of guides for Gluster on top of zfs online, but the porcess differ because of the "Device Name"

2 1

Remove VM that failed being built from template
by Matthew.Stier＠fujitsu.com 21 Oct '20

21 Oct '20

oVirt 4.3.6 Attempted to build 10 VMs from a template, concurrently, and apparently overloaded the 1GB link to the iSCSI storage. I now have four VMs hung in the Locked connection on the display, and no means to cancel, remove them. The all have 'Failed to complete VM **** creation.' log entries, under Events. Any suggestions on how to address?

1 0

Need assistance in migrating between iSCSI arrays.
by Matthew.Stier＠fujitsu.com 21 Oct '20

21 Oct '20

To get a project going, I used an iSCSI SAN array of limited storage, while waiting to obtain, and make operational another iSCSI SAN of considerably more storage. I've attached the new iSCSI array to my cluster of hosts, attached a number of LUNs as additional storage domains, and move my collection of ISO and disk images to the new storage. I also detached and removed the old iSCSI storage domains I no longer need. I'm now down to the last two Storage Domains. The hosted_engine, and the last DATA domain, holding templates. Now the hard part reared its head. I need to completely detach the old iSCSI SAN array, which means I need to migrate the hosted-engine, and my small collection of templates, which I created on the old iSCSI array, to storage domains on the new iSCSI array. I'm looking for recommendations on how to do both. As to the details, I am running Oracle Linux Virtualization Manager 4.3.6, in hosted-engine mode, which means I am running oVirt 4.3.6, in hosted-engine mode. Note: I have configured the first three hosts in the cluster to support hosted-engine, so the hosted-engine can be moved around, for system maintenance.

1 0

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

21 Oct '20

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

3 6

How to clean up Storage Domain manually
by miguel.garcia＠toshibagcs.com 21 Oct '20

21 Oct '20

We have a problem in our cluster where the storage domain was consumed almost totally so we proceed to do a release space by deleting vms and templates that are not longer needed. Despite of removal we got the following eerror message removing some assets "The Storage Domain may be manually cleaned-up from possible leftover". Also this problem is triggered when new vms are created. How can we perform a manual clean-up in the storage domain?

1 1

Add direct lun (Fibre Channel) to VM
by jpedrolima＠gmail.com 20 Oct '20

20 Oct '20

Hi how to add directly to a VM 4 fiber channel luns without losing the data they have, these luns need to be seen directly on the VM as "raw devices". Thks Plima

2 1

Upgrade from ovirt-node-ng 4.4.1 to 4.4.2 fails with "Local storage domains were found on the same filesystem as / ! Please migrate the data to a new LV before upgrading, or you will lose the VMs"
by gantonjo-ovirt＠yahoo.com 20 Oct '20

20 Oct '20

So, we have a cluster of 3 servers running oVirt Node 4.4.1. Now we are attempting to upgrade it to latest version, 4.4.2, but it fails as shown below. Problem is that the Storage domains listed are all located on an external iSCSI SAN. The Storage Domains were created in another cluster we had (oVirt Node 4.3 based) and detached from the old cluster and imported successfully into the new cluster through the oVirt Management interface. As I understand, oVirt itself has created the mount points under /rhev/data-center/mnt/blockSD/ for each of the iSCSI domains, and as such they are not really storaged domains on the / filesystem. I do believe the solution to the mentioned BugZilla bug has caused a new bug, but I may be wrong. I cannot see what we have done wrong when importing these storage domains to the cluster (well, actually, some were freshly created in this cluster, thus fully managed by oVirt 4.4 manager interface). What can we do to proceed in upgrading the hosts to latest oVirt Node? Dependencies resolved. ============================================================================================================================================================================================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================================================================================================================================================================================= Upgrading: ovirt-node-ng-image-update noarch 4.4.2-1.el8 ovirt-4.4 782 M replacing ovirt-node-ng-image-update-placeholder.noarch 4.4.1.5-1.el8 Transaction Summary ============================================================================================================================================================================================================================================================================================================================= Upgrade 1 Package Total download size: 782 M Is this ok [y/N]: y Downloading Packages: ovirt-node-ng-image-update-4.4.2-1.el8.noarch.rpm 8.6 MB/s | 782 MB 01:31 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 8.6 MB/s | 782 MB 01:31 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: ovirt-node-ng-image-update-4.4.2-1.el8.noarch 1/3 Local storage domains were found on the same filesystem as / ! Please migrate the data to a new LV before upgrading, or you will lose the VMs See: https://bugzilla.redhat.com/show_bug.cgi?id=1550205#c3 Storage domains were found in: /rhev/data-center/mnt/blockSD/c3df4c98-ca97-4486-a5d4-d0321a0fb801/dom_md /rhev/data-center/mnt/blockSD/90a52746-e0cb-4884-825d-32a9d94710ff/dom_md /rhev/data-center/mnt/blockSD/74673f68-e1fa-46cf-b0ac-a35f05d42a7a/dom_md /rhev/data-center/mnt/blockSD/f5fe00ba-c899-428f-96a2-e8d5e5707905/dom_md /rhev/data-center/mnt/blockSD/5c3d9aff-66a3-4555-a17d-172fbf043505/dom_md /rhev/data-center/mnt/blockSD/4cc6074b-a5f5-4337-a32f-0ace577e5e47/dom_md /rhev/data-center/mnt/blockSD/a7658abd-e605-455e-9253-69d7e59ff50a/dom_md /rhev/data-center/mnt/blockSD/f18e6e5c-124b-4a66-ae98-2088c87de42b/dom_md /rhev/data-center/mnt/blockSD/f431e29b-77cd-4e51-8f7f-dd73543dfce6/dom_md /rhev/data-center/mnt/blockSD/0f53281c-c756-4171-bcd2-8946956ebbd0/dom_md /rhev/data-center/mnt/blockSD/9fad9f9b-c549-4226-9278-51208411b2ac/dom_md /rhev/data-center/mnt/blockSD/c64006e7-e22c-486f-82a5-20d2b9431299/dom_md /rhev/data-center/mnt/blockSD/509de8b4-bc41-40fa-9354-16c24ae16442/dom_md /rhev/data-center/mnt/blockSD/0d57fcd3-4622-41cc-ab23-744b93d175a0/dom_md error: %prein(ovirt-node-ng-image-update-4.4.2-1.el8.noarch) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package ovirt-node-ng-image-update Verifying : ovirt-node-ng-image-update-4.4.2-1.el8.noarch 1/3 Verifying : ovirt-node-ng-image-update-4.4.1.5-1.el8.noarch 2/3 Verifying : ovirt-node-ng-image-update-placeholder-4.4.1.5-1.el8.noarch 3/3 Unpersisting: ovirt-node-ng-image-update-4.4.1.5-1.el8.noarch.rpm Unpersisting: ovirt-node-ng-image-update-placeholder-4.4.1.5-1.el8.noarch.rpm Thanks in advance for your good help.

4 9

oVirt Survey Autumn 2020 results
by Sandro Bonazzola 19 Oct '20

19 Oct '20

Thanks to the 79 participants to oVirt Survey Autumn 2020! The survey is now closed and results are publicly available at https://docs.google.com/forms/d/1eMYaCoysPkYt2iHZW2RRO1HmSqsD0phrwSTVYFlqLy… We'll analyze collected data in order to improve oVirt thanks to your feedback. 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

Enable Gluster Service
by suporte＠logicworks.pt 18 Oct '20

18 Oct '20

Hello, When I Enable Gluster Service on the cluster, de data center goes to invalid state. Any idea why? -- Jose Ferradeira http://www.logicworks.pt

2 1

How to make oVirt + GlusterFS bulletproof
by Jarosław Prokopowski 16 Oct '20

16 Oct '20

Hi Guys, I had a situation 2 times that due to unexpected power outage something went wrong and VMs on glusterfs where not recoverable. Gluster heal did not help and I could not start the VMs any more. Is there a way to make such setup bulletproof? Does it matter which volume type I choose - raw or qcow2? Or thin provision versus reallocated? Any other advise?

5 16

Latest ManagedBlockDevice documentation
by Michael Thomas 15 Oct '20

15 Oct '20

I'm looking for the latest documentation for setting up a Managed Block Device storage domain so that I can move some of my VM images to ceph rbd. I found this: https://ovirt.org/develop/release-management/features/storage/cinderlib-int… ...but it has a big note at the top that it is "...not user documentation and should not be treated as such." The oVirt administration guide[1] does not talk about managed block devices. I've found a few mailing list threads that discuss people setting up a Managed Block Device with ceph, but didn't see any links to documentation steps that folks were following. Is the Managed Block Storage domain a supported feature in oVirt 4.4.2, and if so, where is the documentation for using it? --Mike [1]ovirt.org/documentation/administration_guide/

4 19

How can I Disable console Single Sign On by default
by Riccardo Brunetti 15 Oct '20

15 Oct '20

Dear all. I'm trying to setup an oVirt environment able to provide VMs to a small number of users. I'm just using the "internal" domain and I defined some users and groups using ovirt-aaa-jdbc-tool. Everything seems to work, the users cal log-in into the VM portal and they can create VM. The problem comes out when I try to access the VM console: in order to be able to open the noVNC console, I need to set Disable Single Sign On on the console settings of the VM. But this is only possible using the Administrator portal and I couldn't find a way to do it "as user". How can I allow users to open the noVNC console from the VM portal? Is there a way to set Disable Single Sign On by default? Thanks a lot Riccardo

1 1

Upgrade from 4.3.9 to 4.3.10 leads to sanlock errors
by mschuler＠bsgtech.com 15 Oct '20

15 Oct '20

After upgrading to 4.3.10 from 4.3.9, when doing VM backups after hours, we started to have VMs freeze/pause during nightly backup runs. We expect the increased load exposes the issue. We reverted the hosts back to 4.3.9 and the problem went away, after some testing using a single host on .10 , I am seeing the below error in sanlock.log: 2020-10-14 16:06:12 2939 [5724]: 95bd5893 aio timeout RD 0x7f7f9c0008c0:0x7f7f9c0008d0:0x7f7fa9efb000 ioto 10 to_count 1 2020-10-14 16:06:12 2939 [5724]: s2 delta_renew read timeout 10 sec offset 0 /dev/95bd5893-83d4-42f2-b333-1c65226f1d09/ids 2020-10-14 16:06:12 2939 [5724]: s2 renewal error -202 delta_length 10 last_success 2908 2020-10-14 16:06:14 2941 [5724]: 95bd5893 aio collect RD 0x7f7f9c0008c0:0x7f7f9c0008d0:0x7f7fa9efb000 result 1048576:0 match reap So engine is still at 4.3.10. We also see the error below in messages: Oct 14 16:09:20 HOSTNAME kernel: perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 I guess my question is two fold, how do I go about troubleshooting this further. Otherwise would it be better/possible to move to 4.4.2 (or 4.4.3 when released.) Do all hosts have to be on 4.3.10, or can the hosts be on 4.3.9 while engine is 4.3.10 to do the migration? Thank you!

1 0

Connection failed
by info＠worldhostess.com 15 Oct '20

15 Oct '20

Messages related to the failure might be found in the journal "journalctl -u cockpit" This is the output node01.xxx.co.za cockpit-tls[8249]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received. Any suggestion will be appreciated as I struggle for days to get oVirt to work and I can see it is still a long way for me to get an operational solution. Henni

2 1