- Users - oVirt List Archives

Gluster remount?
by Christoph Köhler 11 Jun '20

11 Jun '20

Hey, it happens in our ovirt 4.3.9 occasionally that after reboot one of the dedicated gluster nodes (replica3, arbiter 1) some client connections are missing on server side: # gluster volume status gluvol3 clients Client connections for volume gluvol3 ---------------------------------------------- Brick : glusrv01:/gluster/p1/brick1 Clients connected : 17 Hostname . . . -------------------------------------------- Brick : glusrv02:/gluster/p1/brick1 Clients connected : 15 <---- two connections missing Hostname . . . ---------------------------------------------- Brick : glusrv03:/gluster/p1/brick1 Clients connected : 17 Hostname . . . ---------------------------------------------- I don't know why it happes, the log files don't really help. Now: is there a possibility on the missing nodes to reinitiate the gluster mount like 'mount -o remount' or so? The only way I actually know is to set the concerned node to maintenance and reactivate it. But that is really long-moving with many VMs... Any ideas? Thanks Chris

1 0

[ANN] oVirt 4.4.1 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 11 Jun '20

11 Jun '20

oVirt 4.4.1 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.1 Fourth Release Candidate for testing, as of June 11th, 2020. This update is the first in a series of stabilization updates to the 4.4 series. 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. Some of the features included in oVirt 4.4.1 Release Candidate require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer * oVirt Node 4.4.1 based on CentOS Linux 8.1 (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.1 release highlights: http://www.ovirt.org/release/4.4.1/ * 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.1/ [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://mojo.redhat.com/docs/DOC-1199578>*

1 0

teaming vs bonding
by Diggy Mc 10 Jun '20

10 Jun '20

Does 4.4.x support adapter teaming? If yes, which is preferred, teaming or bonding?

7 6

how to test incremental backup in 4.4
by Gianluca Cecchi 10 Jun '20

10 Jun '20

Hello, going to test incremental backup in 4.4. Is this page the updated one to use: https://www.ovirt.org/develop/release-management/features/storage/increment… ? Is there already any ansible module/role ongoing to support it? Thanks, Gianluca

5 17

What happens when shared storage is down?
by Vinícius Ferrão 10 Jun '20

10 Jun '20

Hello, This is a pretty vague and difficult question to answer. But what happens if the shared storage holding the VMs is down or unavailable for a period of time? I’m aware that a longer timeout may put the VMs on pause state, but how this is handled? Is it a time limit? Requests limit? Who manages this? In an event of self recovery of the storage backend what happens next? Manual intervention is required? The VMs may be down or they just continue to run? It depends on the guest OS running like in XenServer where different scenarios may happen? I’ve looked here: https://www.ovirt.org/documentation/admin-guide/chap-Storage.html but there’s nothing that goes about this question. Thanks, Sent from my iPhone

3 4

Ovirt Manager HA
by Vijay Sachdeva 10 Jun '20

10 Jun '20

Hi All, Is there a documentation on creating Ovirt-Manager in HA or is it possible to make the manager to run in HA environment. Since it seems to be a single point of failure..!! Thanks Vijay Sachdeva

4 3

Cannot start ppc64le VM's
by Vinícius Ferrão 10 Jun '20

10 Jun '20

Hello, I’m trying to run ppc64le VM’s on POWER9 but qemu-kvm fails complaining about NUMA issues: VM ppc64le.local.versatushpc.com.br<http://ppc64le.local.versatushpc.com.br> is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2020-06-05T06:16:10.716052Z qemu-kvm: warning: CPU(s) not present in any NUMA nodes: CPU 4 [core-id: 4], CPU 5 [core-id: 5], CPU 6 [core-id: 6], CPU 7 [core-id: 7], CPU 8 [core-id: 8], CPU 9 [core-id: 9], CPU 10 [core-id: 10], CPU 11 [core-id: 11], CPU 12 [core-id: 12], CPU 13 [core-id: 13], CPU 14 [core-id: 14], CPU 15 [core-id: 15] 2020-06-05T06:16:10.716067Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future 2020-06-05T06:16:11.155924Z qemu-kvm: Requested safe indirect branch capability level not supported by kvm, try cap-ibs=fixed-ibs. Any idea of what’s happening? I found some links, but I’m not sure if they are related or not: https://bugzilla.redhat.com/show_bug.cgi?id=1732726 https://bugzilla.redhat.com/show_bug.cgi?id=1592648 Thanks,

2 5

Re: Global Maintenance
by Yedidyah Bar David 10 Jun '20

10 Jun '20

On Tue, Jun 9, 2020 at 8:03 PM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > > Hi Didi, > > I followed the below steps in order to move the HE to a standalone engine: > > Backup and remove Hosted Engine: > > 1. Backup Hosted Engine (engine-backup --scope=all --mode=backup --file=Full --log=Log_Full) > 2. Download the backup files from HE using WinSCP > 3. Enable global Maintenance (hosted-engine --set-maintenance --mode=global) > 4. Power down hosted engine (hosted-engine --vm-shutdown) > > --------------------------------------------------------------------------------------------- > Redeploy Hosted Engine: > > Build new CentOS VM in another environment > *Same IP > *Same name > *Same resources > > 1. sudo yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm > 2. sudo yum install -y ovirt-engine > 3. Copy backup files to newly deployed CentOS VM > 4. engine-backup --mode=restore --file=Full --log=Log_Full --provision-db --provision-dwh-db --restore-permissions > 5. after restore has completed, run engine-setup > > Yes, I get “It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode” error message when running anything to do with engine-setup. In this case, I would like to reconfigure the Websocket proxy. > > How will I go about updating the below: > > update vds_statistics set ha_global_maintenance=f; Please remember that this isn't tested. Please thoroughly test first on a test setup. One way to do that is: /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c 'update vds_statistics set ha_global_maintenance=f;' As I said, it's probably best to do this while the engine is down, to prevent caching issues etc. Best regards, > > Thank you > > Anton Louw > Cloud Engineer: Storage and Virtualization at Vox > ________________________________ > T: 087 805 0000 | D: 087 805 1572 > M: N/A > E: anton.louw(a)voxtelecom.co.za > A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > > > > > > Disclaimer > > The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here. > > > > > -----Original Message----- > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: 09 June 2020 15:19 > To: Anton Louw <Anton.Louw(a)voxtelecom.co.za> > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Global Maintenance > > On Tue, Jun 9, 2020 at 9:39 AM Anton Louw via Users <users(a)ovirt.org> wrote: > > > > > > > > Hi Everybody, > > > > > > > > Just a bit of background. A couple of weeks back I moved my self-hosted engine to a standalone manager. Everything went smooth, my environment is up and running without any issues. > > How exactly did you do that? > > > Just one thing, when I want to reconfigure settings on my self-hosted engine, it says: > > > > “It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode” > > This message is in engine-setup, right? > > engine-setup's code is checking this by: > > /usr/share/ovirt-engine/setup/plugins/ovirt-engine-common/ovirt-engine/system/he.py > > SELECT vm_guid, run_on_vds > FROM vms > WHERE vm_name = %(HostedEngineVmName)s; > > where HostedEngineVmName is either the option of same name from vdc_options, or 'HostedEngine' if missing. Then, where VdsId is 'run_on_vds' column of the result of above: > > SELECT vds_id, ha_global_maintenance > FROM vds_statistics > WHERE vds_id = %(VdsId)s; > > So if this isn't a hosted-engine setup anymore, it should probably be safe to do: > > update vds_statistics set ha_global_maintenance=f; > > and perhaps restart the engine (in case it also does similar checks itself but caches this data). > > Please note that I didn't try this myself. > > > > > > > > > When trying to enable global maintenance from my node, I also get the below: > > > > > > > > “Cannot connect to the HA daemon, please check the logs” > > This is expected, no? You say it's not a hosted-engine setup anymore. > > > > > > > > > Is there something I missed when I moved my self-hosted engine to a standalone manager? > > Either Yes, or the procedure you followed is incomplete. If latter, please file a bug about it. Thanks! > > Best regards, > -- > Didi -- Didi

1 0

Re: Global Maintenance
by Yedidyah Bar David 09 Jun '20

09 Jun '20

On Tue, Jun 9, 2020 at 9:39 AM Anton Louw via Users <users(a)ovirt.org> wrote: > > > > Hi Everybody, > > > > Just a bit of background. A couple of weeks back I moved my self-hosted engine to a standalone manager. Everything went smooth, my environment is up and running without any issues. How exactly did you do that? > Just one thing, when I want to reconfigure settings on my self-hosted engine, it says: > > “It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode” This message is in engine-setup, right? engine-setup's code is checking this by: /usr/share/ovirt-engine/setup/plugins/ovirt-engine-common/ovirt-engine/system/he.py SELECT vm_guid, run_on_vds FROM vms WHERE vm_name = %(HostedEngineVmName)s; where HostedEngineVmName is either the option of same name from vdc_options, or 'HostedEngine' if missing. Then, where VdsId is 'run_on_vds' column of the result of above: SELECT vds_id, ha_global_maintenance FROM vds_statistics WHERE vds_id = %(VdsId)s; So if this isn't a hosted-engine setup anymore, it should probably be safe to do: update vds_statistics set ha_global_maintenance=f; and perhaps restart the engine (in case it also does similar checks itself but caches this data). Please note that I didn't try this myself. > > > > When trying to enable global maintenance from my node, I also get the below: > > > > “Cannot connect to the HA daemon, please check the logs” This is expected, no? You say it's not a hosted-engine setup anymore. > > > > Is there something I missed when I moved my self-hosted engine to a standalone manager? Either Yes, or the procedure you followed is incomplete. If latter, please file a bug about it. Thanks! Best regards, -- Didi

2 1

ovirt vm backup tool
by Ayansh Rocks 09 Jun '20

09 Jun '20

Hi Guys, Can you please suggest a good backup tool for ovirt virtual machines..? Thanks Shashank

4 3