- Users - oVirt List Archives

oVirt Node install with Foreman VG issue
by simon＠justconnect.ie 28 Feb '21

28 Feb '21

Hi All, I have a server with a RAID1 disk for sda and RAID 5 disk for sdb. Following default install, prior to Cockpit Gluster and Engine wizards there is only a single Volume Group which doesn’t allow me to continue. If I manually configure the install and deselect sdb it gives other issues with multipath but at least I can resolve those. Is there a specific kickstart confuguration that should be used? Kind Regards Shimme

2 2

Re: oVirt Node install with Foreman VG issue
by Simon Scott 28 Feb '21

28 Feb '21

Thanks Strahil, Unfortunately changing the filter is done after the initial install. We manually partition sda so that sdb isn’t touched during install. The issues with multipath grabbing sdb are ongoing with a possible manual fix being tested now. Testing has paused at the moment as we have lost gluster on the arbiter node as per https://lists.ovirt.org/archives/list/users@ovirt.org/thread/U64MGWSUCFJRIV… which looks like a full oVirt rebuild again. Any help on that thread would be appreciated. Thanks again Shimme On 28 Feb 2021, at 08:35, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: Most probably there is an LVM filter. As stated in the /etc/multipath.conf , use a special file to blacklist the local disks without modifying /etc/multipath.conf Best Regards, Strahil Nikolov Hi All, I have a server with a RAID1 disk for sda and RAID 5 disk for sdb. Following default install, prior to Cockpit Gluster and Engine wizards there is only a single Volume Group which doesn’t allow me to continue. If I manually configure the install and deselect sdb it gives other issues with multipath but at least I can resolve those. Is there a specific kickstart confuguration that should be used? Kind Regards Shimme _______________________________________________ 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 oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OFZS3XVTVMP5G…

1 0

Add single node to running gluster cluster
by dvx.mellin＠gmail.com 28 Feb '21

28 Feb '21

Hi everyone, I have a working installation of oVirt (4.3.5) with 4 physical servers : 1 for engine and 3 nodes. They work with a distributed gluster fs and i want to add a new physical node in this cluster. Does someone could give me the right way to do this ? Thanks

3 5

Reinstalled Host 4.4.4 bricks failing to start
by simon＠justconnect.ie 27 Feb '21

27 Feb '21

3 Node HCI - Local Storage Replica 2+1 After changing the Cluster 'Default Network Provider' from ovirt-provider-ovn to 'No Default Provider' notification (as expected) to reinstall was flagged against each host. Host 3 (Arbiter) was reinstalled but failed to Activate due to Gluster Bricks not starting. No GlusterFS process for the bricks is listed when checking Status of glusterd. Please can someone help to identify the issue and resolution. Attempted further reinstallation of the Host fails. Kind Regards Shimme

1 1

oVirt fails to update OVF
by Jürgen Walch 26 Feb '21

26 Feb '21

Hi everybody, we are running an oVirt 4.3.10 production cluster with 9 hosts and 5 datastore domains. Since yesterday we get error messages 26.02.2021 02:00:48 VDSM command SetVolumeDescriptionVDS failed: Could not acquire resource. Probably resource factory threw an exception.: () 26.02.2021 02:00:48 Failed to update OVF disks 5aa438e3-8d22-4b6c-bccf-a843151ca0be, OVF data isn't updated on those OVF stores (Data Center datacenter01, Storage Domain vmstore13). 26.02.2021 02:00:48 Failed to update VMs/Templates OVF data for Storage Domain vmstore13 in Data Center datacenter01. every hour. Only one domain (vmstore13) is affected, this domain is (like 3 others in the cluster) based on glusterfs. Trying to update the OVF's manually from the engine web-gui leads to the same result followed by (a misleading) 26.02.2021 02:00:49 OVF_STORE for domain vmstore13 was updated by admin@internal-authz. The vm's with discs on the affected domain are running fine, snapshots are working. So far I have tried to move the SPM role to another host. This succeeded, but the error messages persist. The vdsm log on the SPM host contains something like 2021-02-26 03:00:57,701+0100 INFO (jsonrpc/2) [vdsm.api] START setVolumeDescription(sdUUID=u'9f731135-f5d9-4609-9e3b-fa9cae75e314', spUUID=u'33e8dc9e-8bc8-11ea-bd76-00163e741033', imgUUID=u'5aa438e3-8d22-4b6c-bccf-a843151ca0be', volUUID=u'0795e58c-4960-413a-a0b4-e8a6d547fda5', description=u'{"Updated":false,"Last Updated":"Wed Feb 24 17:48:17 CET 2021","Storage Domains":[{"uuid":"9f731135-f5d9-4609-9e3b-fa9cae75e314"}],"Disk Description":"OVF_STORE"}', options=None) from=::ffff:10.70.1.1,46968, flow_id=1f314676, task_id=9101db01-b4f0-447e-a5a9-b6af76278d55 (api:48) 2021-02-26 03:00:57,712+0100 ERROR (jsonrpc/2) [storage.VolumeManifest] [Errno 116] Stale file handle (fileVolume:155) for each error, I have attached the relevant part of vdsm.log. Has anyone experienced this behaviour before and can provide help ? -- juergen

2 3

oVirt 4.2 cluster upgrade
by Fedele Stabile 26 Feb '21

26 Feb '21

I have a 3 node oVirt 4.2.1 cluster, i'm using a self-hosted engine architecture and storage-engine is on a glusterfs replica 3 of the cluster. The oldest CPU is SandyBridge family (E5-2609) and incidentally I have connectivity problems with IPMI NIC of one node, but Hosted Engine HA is enabled and working. Is it safe to upgrade to the last oVirt 4.4 without a down of vm running on the cluster? May I just click on the button Upgrade that appears on the host page?

2 1

4.3 to 4.4 engine upgrade missing log analyzer tool
by Edward Berger 26 Feb '21

26 Feb '21

I have an oVirt 4.3 to 4.4 engine upgrade upcoming, so I decided to start reading up on the procedure at https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3 I'm stuck at "4.2 Analyzing the environment" which says to install some RPM that isn't found and the closest sounding "ovirt-log-collector" doesn't seem to have the --live option as used there. yum install rhv-log-collector-analyzer

1 0

VDI and ovirt
by cpo cpo 25 Feb '21

25 Feb '21

Is anyone using Ovirt for a Windows 10 VDI deployment? If so are you using a connection broker? If you are what are you using? Thanks for your time

3 2

[ANN] oVirt 4.4.5 Seventh Release Candidate is now available for testing
by Lev Veyde 25 Feb '21

25 Feb '21

oVirt 4.4.5 Seventh Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Seventh Release Candidate for testing, as of February 25th, 2021. This update is the fifth 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 or later 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.5 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.5 (redeploy in case of already being on 4.4.5). 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.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (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 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [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

Starting a defined VM on a different host
by lavi.buchnik＠exlibrisgroup.com 25 Feb '21

25 Feb '21

Hi, I might be missing something here, but I'm looking for the right API way to start a defined VM on a different host. The scenario is this: 1. VM is running under Cluster Affinity Host. and there is a need to cold migrate it to another host on that Affinity. 2. for that I will stop the VM. 3. And now I would like to start the VM on another host, I tried few ways like: vm_service.start( vm=types.Vm( host=types.Host( name='<host name>' ), ) ) But VM keep starting on the current host. Can you please show me the right way to do it. Thanks, Lavi

1 0