- Users - oVirt List Archives

quota_name field length missmatch in db schema
by Pavel Šipoš 11 Jan '19

11 Jan '19

Hi! We have a problem with Quotas whose name has a length grater than 60 characters. Such quotas can be created (or renamed) through oVirt-shell but cannot be managed through the oVirt Engine interface. E.g. VMs in that quota can't be started, created, quota comment can't be added... It turns out that the problem is with the engine database definition of "audit_log" table, that declares "quota_name" column as "character varying(60)". However "quota.quota_name" is defined as "character varying(65)". I think this is a bug and should be fixed in the future. Error example: PL/pgSQL function insertauditlog(integer,timestamp with time zone,integer,character varying,integer,text,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,uuid,character varying,character varying,uuid,uuid,character varying,text,boolean,uuid,text) line 9 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: value too long for type character varying(60) Regards, Pavel

2 1

Datacenter Down Storage error
by ahuser＠web.de 10 Jan '19

10 Jan '19

Hi @all, I have a big problem with my datacenter. After pressing optimization for vm-storage in a active gluster volume are the vms paused. And now, i cant activate the storage in the Data-Center. I have try reboot all Servers. It runs the latest Stable ovirt Version: ovirt-engine-4.2.7.5-1.el7.noarch vdsm-gluster-4.20.43-1.el7.x86_64 glusterfs-3.12.15-1.el7.x86_64 All Servers Up-to Date. Centos 7.6 Gluster Volume Replica 3 with Arbiter /var/log/sanlock.log set scheduler RR|RESET_ON_FORK priority 99 failed: Operation not permitted VDSM ovnode3 command SpmStatusVDS failed: (22, 'Sanlock resource read failure', 'Invalid argument') can anybody help me? thx

2 1

JSON internal error setting bonding using vdsm-client
by Callum Smith 10 Jan '19

10 Jan '19

Dear All, I’m getting the error: “(code=32603, message=Internal JSON-RPC error: {‘reason’: “‘unicode’ object has no attribute ’sort’”}) when trying to apply networking configuration with vdsm-client -f bond.json Host setupNetworks bond.json contains: { “networks”: {}, “bondings”: { “bond0”: { “nics”: “eno1+eno2”, “options”: “mode=4” } }, “options”: {} } Of course python is handling all the arguments as unicode entities rather than strings. Any idea what might be wrong? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

2 1

File level restore of a VM backup located in export domain in Overt
by kevin.doyle＠manchester.ac.uk 10 Jan '19

10 Jan '19

Hi I would like to create backups of VM's using cron. I have installed and ran https://github.com/wefixit-AT/oVirtBackup This works well and saves an image to the export domain I created. I can also carry out a full restore from this by importing from the export domain and selecting the backup. The question I have is how to do a single file recovery from the backup image. I would like to restore /etc/hosts just as an example. What command would I use ? I am not sure of the layout of the export domain directory ── dom_md │ ├── ids │ ├── inbox │ ├── leases │ ├── metadata │ └── outbox ├── images │ └── 622eb98e-f10b-4e96-bec5-8f0a7e7745fe │ ├── b47ce8e1-f552-47f8-af56-33a3b8ce7aed │ └── b47ce8e1-f552-47f8-af56-33a3b8ce7aed.meta └── master ├── tasks └── vms └── c6e6c49c-c9bc-4683-8b19-d18250b5697b └── c6e6c49c-c9bc-4683-8b19-d18250b5697b.ovf The largest file is found is in images folder so I assume this is the backup image ? ./images/622eb98e-f10b-4e96-bec5-8f0a7e7745fe: total 2.7G drwxr-xr-x. 2 vdsm kvm 99 Jan 10 11:48 . drwxr-xr-x. 3 vdsm kvm 50 Jan 10 11:48 .. -rw-rw----. 1 vdsm kvm 50G Jan 10 11:51 b47ce8e1-f552-47f8-af56-33a3b8ce7aed -rw-r--r--. 1 vdsm kvm 269 Jan 10 11:48 b47ce8e1-f552-47f8-af56-33a3b8ce7aed.meta # file b47ce8e1-f552-47f8-af56-33a3b8ce7aed b47ce8e1-f552-47f8-af56-33a3b8ce7aed: x86 boot sector; partition 1: ID=0x83, active, starthead 32, startsector 2048, 2097152 sectors; partition 2: ID=0x8e, starthead 170, startsector 2099200, 102758400 sectors, code offset 0x63 Any help would be appreciated, I am new to Ovirt regards Kevin

1 0

ovirt 4.2.7-1 - adding virtual host ( nested virt. )
by paf1＠email.cz 10 Jan '19

10 Jan '19

Hello guys, I've got problem with adding new host (ESX-virtual) to ovirt 4.2.7-1 ( gluster included) Is this feature supported ??? 2019-01-07 19:38:30,168+01 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler1) [15a4029b] Error while refreshing server data for cluster 'MID' from database: null regs. Paul

2 2

Trouble with my first ovirt-engine installation.
by benzianekarim67＠gmail.com 09 Jan '19

09 Jan '19

I'm having a certificate problem when I'm doing a "ym install ovirt-engine" Can someone help me thank you. [ovirt-4.2] name=Latest oVirt 4.2 Release #baseurl=http://resources.ovirt.org/pub/ovirt-4.2/rpm/el$releasever/ mirrorlist=https://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.2-el… enabled=1 skip_if_unavailable=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 Thank's

2 2

VMs Hung On Booting From Hard Disk
by Douglas Duckworth 09 Jan '19

09 Jan '19

Hi I have deployed 10 VMs in our oVirt cluster using Ansible. Thanks everyone for helping get it working. However, I randomly run into issues where the OS won't load after completing kickstart installation. As you can see the disks are attached while we are booting to it however I keep getting a hang at "booting from hard disk." The kickstart, kernel, and everything else for this VM, matches others. I am unsure why this problem occurs. I have attached repeating vdsm errors from the host which has the VM. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690

1 0

Re: move 'ovirtmgmt' bridge to a bonded NIC team
by Dominik Holler 09 Jan '19

09 Jan '19

On Tue, 8 Jan 2019 17:01:38 +0000 Shawn Southern <shawn.southern(a)entegrus.com> wrote: >We've recently added additional NICs to our oVirt nodes, and want to move the ovirtmgmt interface to one of the bonded interfaces, away from the single ethernet port currently used. This is to provide redundant connectivity to the nodes. > >I've not had any luck finding documentation on how to do this. If we change it manually by editing files in /etc/sysconfig/network-scripts, VDSM simply changes everything back. > Please use oVirt Engine to manage the network configuration. >I'm just looking to be pointed in the right direction here. > I see no reason why the usual way of configuring host networking via Compute > Hosts > hostname > Network Interfaces > Setup Host Networks should not work. ovirtmgmt must not be used by a VM on this host during the change, and ovirtmgmt should use a static IP address in Setup Host Networks > Edit management network: ovirtmgmt > IPv4. It might be a good idea to move the host to maintenance before the change, and ensure connectivity from the bond to oVirt Engine, because the change will be rolled back, if connectivity is lost. >Thanks!

1 0

[ANN] oVirt 4.2.8 Third Release Candidate is now available
by Sandro Bonazzola 09 Jan '19

09 Jan '19

The oVirt Project is pleased to announce the availability of the oVirt 4.2.8 Third Release Candidate, as of January 9th, 2019. This update is a release candidate of the eighth in a series of stabilization updates to the 4.2 series. This is pre-release software. This pre-release should not to be used in production. This release is available now for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node is available [2] Additional Resources: * Read more about the oVirt 4.2.8 release highlights: http://www.ovirt.org/release/4.2.8/ * 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.2.8/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

oVirt upgrade 4.1 to 4.2
by p.staniforth＠leedsbeckett.ac.uk 09 Jan '19

09 Jan '19

Hello when we did a live upgrade of our VDC from 4.1 to 4.2 we had a large number of VMs running that had a Custom Compatibility Version set to 4.1 to allow them to keep running while the cluster and VDC were upgraded. Unfortunately there was a large number of snapshots taken be the users before they were restarted their VMs so they have the Custom_Compatibility_Version set to 4.1 and so can't run in the 4.2 VDC, is there a way to search for them in the API or SDK because I can only find them in the events log when they fail to start. Thanks, Paul S.

2 1