- Users - oVirt List Archives

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