May 2019 - Users - oVirt List Archives

VMs import over slow 1gig interface instead of fast 10gig interface?
by Jacob Green 13 May '19

13 May '19

Ok, so I want to try and more thoroughly explain my situation. I want to better understand what is happening, and if there is a way to force import over the faster connection. Today I have two Ovirt environments, one on 4.1 and one on 4.2, on the new environment we have migrated to new VLANs for Management and Data. The export domain is a NFS domain hosted on a Trunas device that has an ip address of X.X.12.100. Our host has multiple Ethernet connections, one Bonded 20Gigabit interface. That is where we have the ovirtmgmt profile. And a secondary 1 Gigabit interface that we call our VLAN12 profile or server VLAN. *The problem.... *When importing a VM from the export domain, the import is happening over the 1Gigabit interface on the VLAN12 profile. Instead of the 20gigabit Bonded interface on VLAN 100. *My understanding.... *So I probably just misunderstand how this works, but here is what I thought should happen, in the *Setup Host Network* screen for this host I have the ovirtmgmt on VLAN100 with the bonded 20Gigabit interface performing the following. "*Management, Display, Migration, VM and Default Route*." Then I have the secondary 1 Gigabit interface just doing "*VM*" on VLAN12. What I thought should happen is that anything Migration related "*/Includes importing from export domain?/*" should happen on the Migration interface, which in my case is the ovritmgmt interface on VLAN100. I have also confirmed that I can ping from the VLAN100 ovirtmgmt interface to the storage on VLAN12. So there is connectivity from that interface to the storage. What I am trying to figure out is there a way to force it to do imports over the 20Gigabit interface that resides on VLAN100 instead of the slower VLAN12 interface, that is just there for general VM connectivity. Thank you for any advice or guidance on this matter. -- Jacob Green Systems Admin American Alloy Steel

7 9

Re: OvfUpdateIntervalInMinutes restored to original value too early?
by Andreas Elvers 12 May '19

12 May '19

I suppose the /var/log/ovirt-hosted-engine-setup/engine-logs-2019-05-10T16:16:14Z/ovirt-engine/engine.log is the bootstrap engine log. It is attached. The bootstrap engine looks quite ok when glancing through the dashboard, datacenter, storage domains,… Although there are two old hosted storage domains.

1 1

Upgrade engine to 4.3.3 or setup a new engine
by Magnus Isaksson 12 May '19

12 May '19

Hello all I'm having trouble upgrading my engine to 4.3.3 from 4.2.8 The upgrade goes well, no errors but webgui wont load, it just says "waiting for engine" I have tried to set up a new machine with engine and import the DB from the old(after upgrade) still the same problem. So after quite a few tries i gave up and set up a fresh new engine 4.3.3 But can i move/migrate the hosts with running VM:s in to the new engine? In vmware vcenter it is just to add the host and all VM:s and stuff comes over, but im guessing from what ive read that it is not that simple with ovirt. Or how should i solve this? //Magnus

2 1

HostedEngine cleaned up
by Sakhi Hadebe 12 May '19

12 May '19

Hi, We have a situation where the HostedEngine was cleaned up and the VMs are no longer running. Looking at the logs we can see the drive files as: 2019-03-26T07:42:46.915838Z qemu-kvm: -drive file=/rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685,format=qcow2,if=none,id=drive-ua-b2b872cd-b468-4f14-ae20-555ed823e84b,serial=b2b872cd-b468-4f14-ae20-555ed823e84b,werror=stop,rerror=stop,cache=none,aio=native: 'serial' is deprecated, please use the corresponding option of '-device' instead I assume this is the disk was writing to before it went down. Trying to list the file gives an error and the file is not there; ls -l /rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685 Is there a way we can recover the VM's disk images ? NOTE: No HostedEngine backups -- Regards, Sakhi Hadebe

7 13

engine-setup failed in upgrade step to 4.3.2 with DNF errors on Centos 7.6
by Oliver Riesener 11 May '19

11 May '19

# engine-setup ``` [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-aio.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20190329154037-huchep.log Version: otopi-1.8.1 (otopi-1.8.1-1.el7) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloaded Extra Packages for Enterprise Linux 7 - x86_64 [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== PRODUCT OPTIONS ==-- Set up Cinderlib integration (Currently in tech preview) (Yes, No) [No]: [ INFO ] ovirt-provider-ovn already installed, skipping. --== PACKAGES ==-- [ INFO ] Checking for product updates... [ ERROR ] DNF 'Base' object has no attribute '_group_persistor' [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': 'Base' object has no attribute '_group_persistor' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190329154037-huchep.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190329154107-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed What can i do ? ```

2 2

[Users] Lifecycle / upgradepath
by Sven Kieske 11 May '19

11 May '19

Hi Community, Currently, there is no single document describing supported (which means: working ) upgrade scenarios. I think the project has matured enough, to have such an supported upgradepath, which should be considered in the development of new releases. As far as I know, currently it is supported to upgrade from x.y.z to x.y.z+1 and from x.y.z to x.y+1.z but not from x.y-1.z to x.y+1.z directly. maybe this should be put together in a wiki page at least. also it would be cool to know how long a single "release" would be supported. In this context I would define a release as a version bump from x.y.z to x.y+1.z or to x+1.y.z a bump in z would be a bugfix release. The question is, how long will we get bugfix releases for a given version? What are your thoughts? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

2 1

Planned restart of production services
by Evgheni Dereveanchin 11 May '19

11 May '19

Hi everyone, I will be restarting several production systems within the following hour to apply updates. The following services may be unreachable for some period of time: - resources.ovirt.org - package repositories - jenkins.ovirt.org - CI master Package repositories will be unreachable for a short period of time. No new CI jobs will be started during this period. I will announce you once maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

[Users] Nested virtualization with Opteron 2nd generation and oVirt 3.1 possible?
by Gianluca Cecchi 11 May '19

11 May '19

Hello, I have 2 physical servers with Opteron 2nd gen cpu. There is CentOS 6.3 installed and some VM already configured on them. Their /proc/cpuinfo contains ... model name : Dual-Core AMD Opteron(tm) Processor 8222 ... kvm_amd kernel module is loaded with its default enabled nested option # systool -m kvm_amd -v Module = "kvm_amd" Attributes: initstate = "live" refcnt = "15" srcversion = "43D8067144E7D8B0D53D46E" Parameters: nested = "1" npt = "1" ... I already configured a fedora 17 VM as a oVirt 3.1 Engine I'm trying to configure another VM as oVirt 3.1 node with ovirt-node-iso-2.5.5-0.1.fc17.iso It seems I'm not able to configure so that ovirt install doesn't complain. After some attempts, I tried this in my vm.xml for the cpu: <cpu mode='custom' match='exact'> <model fallback='allow'>athlon</model> <vendor>AMD</vendor> <feature policy='require' name='pni'/> <feature policy='require' name='rdtscp'/> <feature policy='force' name='svm'/> <feature policy='require' name='clflush'/> <feature policy='require' name='syscall'/> <feature policy='require' name='lm'/> <feature policy='require' name='cr8legacy'/> <feature policy='require' name='ht'/> <feature policy='require' name='lahf_lm'/> <feature policy='require' name='fxsr_opt'/> <feature policy='require' name='cx16'/> <feature policy='require' name='extapic'/> <feature policy='require' name='mca'/> <feature policy='require' name='cmp_legacy'/> </cpu> Inside node /proc/cpuinfo becomes processor : 3 vendor_id : AuthenticAMD cpu family : 6 model : 2 model name : QEMU Virtual CPU version 0.12.1 stepping : 3 microcode : 0x1000065 cpu MHz : 3013.706 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext fxsr_opt lm nopl pni cx16 hypervisor lahf_lm cmp_legacy cr8_legacy bogomips : 6027.41 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: 2 questions: 1) Is there any combination in xml file to give to my VM so that oVirt doesn't complain about missing hardware virtualization with this processor? 2) suppose 1) is not possible in my case and I still want to test the interface and try some config operations to see for example the differences with RHEV 3.0, how can I do? At the moment this complaint about hw virtualization prevents me to activate the node. I get Installing Host f17ovn01. Step: RHEV_INSTALL. Host f17ovn01 was successfully approved. Host f17ovn01 running without virtualization hardware acceleration Detected new Host f17ovn01. Host state was set to Non Operational. Host f17ovn01 moved to Non-Operational state. Host f17ovn01 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : CpuFlags Can I lower the requirements to be able to operate without hw virtualization in 3.1? Thanks in advance, Gianluca

2 1

4.3.3 single node hyperconverged wizard failing because var/log is too small?
by Edward Berger 10 May '19

10 May '19

I'm trying to bring up a single node hyperconverged with the current node-ng ISO installation, but it ends with this failure message. TASK [gluster.features/roles/gluster_hci : Check if /var/log has enough disk space] *** fatal: [br014.bridges.psc.edu] FAILED! => {"changed": true, "cmd": "df -m /var/log | awk '/[0-9]%/ {print $4}'", "delta": "0:00:00.008513", "end": "2019-05-09 20:09:27.914400", "failed_when_result": true, "rc": 0, "start": "2019-05-09 20:09:27.905887", "stderr": "", "stderr_lines": [], "stdout": "7470", "stdout_lines": ["7470"]} I have what the installer created by default for /var/log, so I don't know why its complaining. [root@br014 ~]# df -kh Filesystem Size Used Avail Use% Mounted on /dev/mapper/onn_br014-ovirt--node--ng--4.3.3.1--0.20190417.0+1 3.5T 2.1G 3.3T 1% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 4.0K 63G 1% /dev/shm tmpfs 63G 18M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/mapper/onn_br014-home 976M 2.6M 907M 1% /home /dev/mapper/onn_br014-tmp 976M 2.8M 906M 1% /tmp /dev/mapper/onn_br014-var 15G 42M 14G 1% /var /dev/sda2 976M 173M 737M 19% /boot /dev/mapper/onn_br014-var_log 7.8G 41M 7.3G 1% /var/log /dev/mapper/onn_br014-var_log_audit 2.0G 7.6M 1.8G 1% /var/log/audit /dev/mapper/onn_br014-var_crash 9.8G 37M 9.2G 1% /var/crash /dev/sda1 200M 12M 189M 6% /boot/efi tmpfs 13G 0 13G 0% /run/user/1000 tmpfs 13G 0 13G 0% /run/user/0 /dev/mapper/gluster_vg_sdb-gluster_lv_engine 3.7T 33M 3.7T 1% /gluster_bricks/engine /dev/mapper/gluster_vg_sdc-gluster_lv_data 3.7T 34M 3.7T 1% /gluster_bricks/data /dev/mapper/gluster_vg_sdd-gluster_lv_vmstore 3.7T 34M 3.7T 1% /gluster_bricks/vmstore The machine had 4 4TB disks, so sda is the installation for oVirt node-ng, the other 3 disks for the gluster volumes. root@br014 ~]# pvs PV VG Fmt Attr PSize PFree /dev/sda3 onn_br014 lvm2 a-- <3.64t 100.00g /dev/sdb gluster_vg_sdb lvm2 a-- <3.64t <26.02g /dev/sdc gluster_vg_sdc lvm2 a-- <3.64t 0 /dev/sdd gluster_vg_sdd lvm2 a-- <3.64t 0 [root@br014 ~]# vgs VG #PV #LV #SN Attr VSize VFree gluster_vg_sdb 1 1 0 wz--n- <3.64t <26.02g gluster_vg_sdc 1 2 0 wz--n- <3.64t 0 gluster_vg_sdd 1 2 0 wz--n- <3.64t 0 onn_br014 1 11 0 wz--n- <3.64t 100.00g [root@br014 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_engine gluster_vg_sdb -wi-ao---- 3.61t gluster_lv_data gluster_vg_sdc Vwi-aot--- 3.61t gluster_thinpool_gluster_vg_sdc 0.05 gluster_thinpool_gluster_vg_sdc gluster_vg_sdc twi-aot--- <3.61t 0.05 0.13 gluster_lv_vmstore gluster_vg_sdd Vwi-aot--- 3.61t gluster_thinpool_gluster_vg_sdd 0.05 gluster_thinpool_gluster_vg_sdd gluster_vg_sdd twi-aot--- <3.61t 0.05 0.13 home onn_br014 Vwi-aotz-- 1.00g pool00 4.79 ovirt-node-ng-4.3.3.1-0.20190417.0 onn_br014 Vwi---tz-k <3.51t pool00 root ovirt-node-ng-4.3.3.1-0.20190417.0+1 onn_br014 Vwi-aotz-- <3.51t pool00 ovirt-node-ng-4.3.3.1-0.20190417.0 0.13 pool00 onn_br014 twi-aotz-- 3.53t 0.19 1.86 root onn_br014 Vri---tz-k <3.51t pool00 swap onn_br014 -wi-ao---- 4.00g tmp onn_br014 Vwi-aotz-- 1.00g pool00 4.84 var onn_br014 Vwi-aotz-- 15.00g pool00 3.67 var_crash onn_br014 Vwi-aotz-- 10.00g pool00 2.86 var_log onn_br014 Vwi-aotz-- 8.00g pool00 3.25 var_log_audit onn_br014 Vwi-aotz-- 2.00g pool00 4.86 Here's the full deploy log from the UI. Let me know if you need specific logs. PLAY [Setup backend] *********************************************************** TASK [Gathering Facts] ********************************************************* ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/firewall_config : Start firewalld if not already started] *** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/firewall_config : check if required variables are set] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/firewall_config : Open/Close firewalld ports] ******** ok: [br014.bridges.psc.edu] => (item=2049/tcp) ok: [br014.bridges.psc.edu] => (item=54321/tcp) ok: [br014.bridges.psc.edu] => (item=5900/tcp) ok: [br014.bridges.psc.edu] => (item=5900-6923/tcp) ok: [br014.bridges.psc.edu] => (item=5666/tcp) ok: [br014.bridges.psc.edu] => (item=16514/tcp) TASK [gluster.infra/roles/firewall_config : Add/Delete services to firewalld rules] *** ok: [br014.bridges.psc.edu] => (item=glusterfs) TASK [gluster.infra/roles/backend_setup : Gather facts to determine the OS distribution] *** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for debian systems.] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for RHEL systems.] *** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Install python-yaml package for Debian systems] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Initialize vdo_devs array] *********** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Record VDO devices (if any)] ********* skipping: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdc', u'pvname': u'/dev/sdc'}) skipping: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdd', u'pvname': u'/dev/sdd'}) TASK [gluster.infra/roles/backend_setup : Enable and start vdo service] ******** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create VDO with specified size] ****** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Check if valid disktype is provided] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for JBOD] ****** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for RAID] ****** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set VG physical extent size for RAID] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** ok: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) ok: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdc', u'pvname': u'/dev/sdc'}) ok: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdd', u'pvname': u'/dev/sdd'}) TASK [gluster.infra/roles/backend_setup : Create thick logical volume] ********* ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'3700G'}) TASK [gluster.infra/roles/backend_setup : Calculate chunksize for RAID6/RAID10/RAID5] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set chunksize for JBOD] ************** ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create a LV thinpool] **************** ok: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdc', u'thinpoolname': u'gluster_thinpool_gluster_vg_sdc', u'poolmetadatasize': u'16G'}) ok: [br014.bridges.psc.edu] => (item={u'vgname': u'gluster_vg_sdd', u'thinpoolname': u'gluster_thinpool_gluster_vg_sdd', u'poolmetadatasize': u'16G'}) TASK [gluster.infra/roles/backend_setup : Create thin logical volume] ********** ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_data', u'vgname': u'gluster_vg_sdc', u'thinpool': u'gluster_thinpool_gluster_vg_sdc', u'lvsize': u'3700G'}) ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_vmstore', u'vgname': u'gluster_vg_sdd', u'thinpool': u'gluster_thinpool_gluster_vg_sdd', u'lvsize': u'3700G'}) TASK [gluster.infra/roles/backend_setup : Extend volume group] ***************** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Change attributes of LV] ************* skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create LV for cache] ***************** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create metadata LV for cache] ******** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Convert logical volume to a cache pool LV] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Convert logical volume to a cache pool LV without cachemetalvname] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Convert an existing logical volume to a cache LV] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set XFS options for JBOD] ************ ok: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Set XFS options for RAID devices] **** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Create filesystem on thin logical vols] *** ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_data', u'vgname': u'gluster_vg_sdc', u'thinpool': u'gluster_thinpool_gluster_vg_sdc', u'lvsize': u'3700G'}) ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_vmstore', u'vgname': u'gluster_vg_sdd', u'thinpool': u'gluster_thinpool_gluster_vg_sdd', u'lvsize': u'3700G'}) TASK [gluster.infra/roles/backend_setup : Create filesystem on thick logical vols] *** ok: [br014.bridges.psc.edu] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'3700G'}) TASK [gluster.infra/roles/backend_setup : Create mount directories if not already present] *** ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/data', u'vgname': u'gluster_vg_sdc', u'lvname': u'gluster_lv_data'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/vmstore', u'vgname': u'gluster_vg_sdd', u'lvname': u'gluster_lv_vmstore'}) TASK [gluster.infra/roles/backend_setup : Set mount options for VDO] *********** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_setup : Mount the vdo devices (If any)] ****** skipping: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) skipping: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/data', u'vgname': u'gluster_vg_sdc', u'lvname': u'gluster_lv_data'}) skipping: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/vmstore', u'vgname': u'gluster_vg_sdd', u'lvname': u'gluster_lv_vmstore'}) TASK [gluster.infra/roles/backend_setup : Mount the devices] ******************* ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/data', u'vgname': u'gluster_vg_sdc', u'lvname': u'gluster_lv_data'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/vmstore', u'vgname': u'gluster_vg_sdd', u'lvname': u'gluster_lv_vmstore'}) TASK [gluster.infra/roles/backend_setup : Set Gluster specific SeLinux context on the bricks] *** ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/data', u'vgname': u'gluster_vg_sdc', u'lvname': u'gluster_lv_data'}) ok: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/vmstore', u'vgname': u'gluster_vg_sdd', u'lvname': u'gluster_lv_vmstore'}) TASK [gluster.infra/roles/backend_setup : restore file(s) default SELinux security contexts] *** changed: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) changed: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/data', u'vgname': u'gluster_vg_sdc', u'lvname': u'gluster_lv_data'}) changed: [br014.bridges.psc.edu] => (item={u'path': u'/gluster_bricks/vmstore', u'vgname': u'gluster_vg_sdd', u'lvname': u'gluster_lv_vmstore'}) TASK [gluster.infra/roles/backend_reset : unmount the directories (if mounted)] *** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_reset : Delete volume groups] **************** skipping: [br014.bridges.psc.edu] TASK [gluster.infra/roles/backend_reset : Remove VDO devices] ****************** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Create temporary storage directory] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Get the name of the directory created] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : check if gluster_features_ganesha_clusternodes is set] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Define service port] **************** skipping: [br014.bridges.psc.edu] => (item=^#(STATD_PORT=.*)) skipping: [br014.bridges.psc.edu] => (item=^#(LOCKD_TCPPORT=.*)) skipping: [br014.bridges.psc.edu] => (item=^#(LOCKD_UDPPORT=.*)) TASK [gluster.features/roles/nfs_ganesha : Check packages installed, if not install] *** skipping: [br014.bridges.psc.edu] => (item=glusterfs-ganesha) skipping: [br014.bridges.psc.edu] => (item=nfs-ganesha) skipping: [br014.bridges.psc.edu] => (item=corosync) skipping: [br014.bridges.psc.edu] => (item=pacemaker) skipping: [br014.bridges.psc.edu] => (item=libntirpc) skipping: [br014.bridges.psc.edu] => (item=pcs) TASK [gluster.features/roles/nfs_ganesha : Restart services] ******************* skipping: [br014.bridges.psc.edu] => (item=nfslock) skipping: [br014.bridges.psc.edu] => (item=nfs-config) skipping: [br014.bridges.psc.edu] => (item=rpc-statd) TASK [gluster.features/roles/nfs_ganesha : Stop services] ********************** skipping: [br014.bridges.psc.edu] => (item=nfs-server) TASK [gluster.features/roles/nfs_ganesha : Disable service] ******************** skipping: [br014.bridges.psc.edu] => (item=nfs-server) TASK [gluster.features/roles/nfs_ganesha : Enable services] ******************** skipping: [br014.bridges.psc.edu] => (item=glusterfssharedstorage) skipping: [br014.bridges.psc.edu] => (item=nfs-ganesha) skipping: [br014.bridges.psc.edu] => (item=network) skipping: [br014.bridges.psc.edu] => (item=pcsd) skipping: [br014.bridges.psc.edu] => (item=pacemaker) TASK [gluster.features/roles/nfs_ganesha : Start services] ********************* skipping: [br014.bridges.psc.edu] => (item=network) skipping: [br014.bridges.psc.edu] => (item=pcsd) TASK [gluster.features/roles/nfs_ganesha : Create a user hacluster if not already present] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Set the password for hacluster] ***** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Set the hacluster user the same password on new nodes] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Pcs cluster authenticate the hacluster on new nodes] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Pause for a few seconds after pcs auth] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Set gluster_use_execmem flag on and keep it persistent] *** skipping: [br014.bridges.psc.edu] => (item=gluster_use_execmem) skipping: [br014.bridges.psc.edu] => (item=ganesha_use_fusefs) TASK [gluster.features/roles/nfs_ganesha : check if gluster_features_ganesha_masternode is set] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the ssh keys to the local machine] *** skipping: [br014.bridges.psc.edu] => (item=secret.pem.pub) skipping: [br014.bridges.psc.edu] => (item=secret.pem) TASK [gluster.features/roles/nfs_ganesha : check if gluster_features_ganesha_newnodes_vip is set] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the public key to remote nodes] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the private key to remote node] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Deploy the pubkey on all nodes] ***** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Make the volume a gluster shared volume] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Generate ssh key in one of the nodes in HA cluster] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the ssh keys to the local machine] *** skipping: [br014.bridges.psc.edu] => (item=secret.pem.pub) skipping: [br014.bridges.psc.edu] => (item=secret.pem) TASK [gluster.features/roles/nfs_ganesha : Create configuration directory for nfs_ganesha] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy ganesha.conf to config directory on shared volume] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Create ganesha-ha.conf file] ******** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Enable NFS Ganesha] ***************** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Pause for 30 seconds (takes a while to enable NFS Ganesha)] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Check NFS Ganesha status] *********** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Report NFS Ganesha status] ********** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Report NFS Ganesha status (If any errors)] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : check if gluster_features_ganesha_volume is set] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Export the NFS Ganesha volume] ****** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the public key to remote nodes] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Copy the private key to remote node] *** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Deploy the pubkey on all nodes] ***** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Adds a node to the cluster] ********* skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Report ganesha add-node status] ***** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/nfs_ganesha : Delete the temporary directory] ***** skipping: [br014.bridges.psc.edu] TASK [gluster.features/roles/gluster_hci : Check if packages are installed, if not install] *** ok: [br014.bridges.psc.edu] => (item=vdsm) ok: [br014.bridges.psc.edu] => (item=vdsm-gluster) ok: [br014.bridges.psc.edu] => (item=ovirt-host) ok: [br014.bridges.psc.edu] => (item=screen) TASK [gluster.features/roles/gluster_hci : Enable and start glusterd and chronyd] *** ok: [br014.bridges.psc.edu] => (item=chronyd) ok: [br014.bridges.psc.edu] => (item=glusterd) ok: [br014.bridges.psc.edu] => (item=firewalld) TASK [gluster.features/roles/gluster_hci : Add user qemu to gluster group] ***** ok: [br014.bridges.psc.edu] TASK [gluster.features/roles/gluster_hci : Disable the hook scripts] *********** changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/set/post/S30samba-set.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/start/post/S30samba-start.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/stop/pre/S30samba-stop.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/reset/post/S31ganesha-reset.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1//start/post/S31ganesha-start.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/start/post/S29CTDBsetup.sh) changed: [br014.bridges.psc.edu] => (item=/var/lib/glusterd/hooks/1/stop/pre/S29CTDB-teardown.sh) TASK [gluster.features/roles/gluster_hci : Check if valid FQDN is provided] **** changed: [br014.bridges.psc.edu -> localhost] => (item=br014.bridges.psc.edu ) TASK [gluster.features/roles/gluster_hci : Check if /var/log has enough disk space] *** fatal: [br014.bridges.psc.edu] FAILED! => {"changed": true, "cmd": "df -m /var/log | awk '/[0-9]%/ {print $4}'", "delta": "0:00:00.008513", "end": "2019-05-09 20:09:27.914400", "failed_when_result": true, "rc": 0, "start": "2019-05-09 20:09:27.905887", "stderr": "", "stderr_lines": [], "stdout": "7470", "stdout_lines": ["7470"]} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* to retry, use: --limit @/usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.retry PLAY RECAP ********************************************************************* br014.bridges.psc.edu : ok=25 changed=3 unreachable=0 failed=1

2 2

Gluster Snapshot Datepicker Not Working?
by Alex McWhirter 10 May '19

10 May '19

Updated to 4.3.3.7, the date picker for gluster snapshot appears to not be working? It wont register clicks, and manually typing in times doesn't work. Can anyone else confirm?

1 0

Hosted Engine Restore Issues
by Alan G 10 May '19

10 May '19

Hi, Trying to re-deploy Hosted Engine into a new storage domain. "hosted-engine --deploy --noansible" has completed and the engine is up, but I cannot remove the existing hosted_storage domain to allow the new one to be imported. I cannot remove the domain until the old HostedEngine VM is removed, but I cannot remove that as it has Delete Protection enabled. Any attempt to remove delete protection errors with "There was an attempt to change Hosted Engine VM values that are locked". How is this process supposed to work? Thanks, Alan

1 0

OvfUpdateIntervalInMinutes restored to original value too early?
by Andreas Elvers 10 May '19

10 May '19

I'm having a problem with restore. It fails while "Wait for OVF_STORE disk content". Looking at the ansible output and at the bug report https://bugzilla.redhat.com/show_bug.cgi?id=1644748 isn't the original value of 60 minutes for OvfUpdateIntervalInMinutes restored too early? [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host SPM_ID] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Parse host SPM_ID] [ INFO ] ok: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore original DisableFenceAtStartupInSec] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove DisableFenceAtStartupInSec temporary file] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore original OvfUpdateIntervalInMinutes] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove OvfUpdateIntervalInMinutes temporary file] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Removing temporary value] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Restoring original value] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary directory for ansible as postgres user] [ INFO ] changed: [localhost -> engine.infra.solutions.work] [ INFO ] TASK [ovirt.hosted_engine_setup : Fail if he_force_ip4 and he_force_ip6 are set at the same time] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Prepare getent key] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Trigger hosted engine OVF update and enable the serial console] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Wait until OVF update finishes] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Parse OVF_STORE disk list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check OVF_STORE volume status] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Wait for OVF_STORE disk content] [ ERROR ] {u'_ansible_parsed': True, u'stderr_lines': [u'20+0 records in', u'20+0 records out', u'10240 bytes (10 kB) copied, 0.000164261 s, 62.3 MB/s', u'tar: 1e74609b-51e1-45c8-9106-2596ee59ba3a.ovf: Not found in archive', u'tar: Exiting with failure status due to previous errors'], u'changed': True, u'end': u'2019-05-10 12:57:57.610068', u'_ansible_item_label': {u'image_id': u'59d16f28-64ed-4c3f-aaad-7d98e2718f53', u'name': u'OVF_STORE', u'id': u'98bd5cfc-809d-4d40-83e0-98e379af5f97'}, u'stdout': u'', u'failed': True, u'_ansible_item_result': True, u'msg': u'non-zero return code', u'rc': 2, u'start': u'2019-05-10 12:57:56.928294', u'attempts': 12, u'cmd': u"vdsm-client Image prepare storagepoolID=597f329c-0296-03af-0369-000000000139 storagedomainID=8f115ea6-91ec-4e10-9240-bc8eda47b7ff imageID=98bd5cfc-809d-4d40-83e0-98e379af5f97 volumeID=59d16f28-64ed-4c3f-aaad-7d98e2718f53 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 1e74609b-51e1-45c8-9106-259 6ee59ba3a.ovf", u'item': {u'image_id': u'59d16f28-64ed-4c3f-aaad-7d98e2718f53', u'name': u'OVF_STORE', u'id': u'98bd5cfc-809d-4d40-83e0-98e379af5f97'}, u'delta': u'0:00:00.681774', u'invocation': {u'module_args': {u'warn': False, u'executable': None, u'_uses_shell': True, u'_raw_params': u"vdsm-client Image prepare storagepoolID=597f329c-0296-03af-0369-000000000139 storagedomainID=8f115ea6-91ec-4e10-9240-bc8eda47b7ff imageID=98bd5cfc-809d-4d40-83e0-98e379af5f97 volumeID=59d16f28-64ed-4c3f-aaad-7d98e2718f53 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 1e74609b-51e1-45c8-9106-2596ee59ba3a.ovf", u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin': None}}, u'stdout_lines': [], u'stderr': u'20+0 records in\n20+0 records out\n10240 bytes (10 kB) copied, 0.000164261 s, 62.3 MB/s\ntar: 1e74609b-51e1-45c8-9106-2596ee59ba3a.ovf: Not found in archive\ntar: Exiting with failure status due to previous errors', u'_ansible_no_log': False}

2 1

Re: oVirt Open Source Backup solution?
by Derek Atkins 10 May '19

10 May '19

Hi, Michael Blanchard <michael(a)wanderingmad.com> writes: > If you haven't seen my other posts, I'm not a very experienced Linux admin, so > I'm trying to make it as easy as possible to run and maintain. It's hard > enough for me to not break ovirt in crazy ways This has nothing to do with ovirt. You could use rdiff-backup on any running machine, be it virtual or bare metal. It's just a way to use a combination of diff and rsync to backup machines. Indeed, I was using it with my vmware-based systems and, when I migrated them to ovirt, the backups just continued working. > Get Outlook for Android -derek -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

1 0

Re: oVirt and NetApp NFS storage
by Strahil 10 May '19

10 May '19

I know 2 approaches. 1. Use NFS hard mounting option - it will never give error to sanlock and it will be waiting until NFS is recovered (never tries this one, but in theory might work) 2. Change the default sanlock timeout (last time I tried that - it didn't work) . You might need help from Sandro or Sahina for that option. Best Regards, Strahil NikolovOn Apr 18, 2019 11:45, klaasdemter(a)gmail.com wrote: > > Hi, > > I got a question regarding oVirt and the support of NetApp NFS storage. > We have a MetroCluster for our virtual machine disks but a HA-Failover > of that (active IP gets assigned to another node) seems to produce > outages too long for sanlock to handle - that affects all VMs that have > storage leases. NetApp says a "worst case" takeover time is 120 seconds. > That would mean sanlock has already killed all VMs. Is anyone familiar > with how we could setup oVirt to allow such storage outages? Do I need > to use another type of storage for my oVirt VMs because that NFS > implementation is unsuitable for oVirt? > > > Greetings > > Klaas > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TSJJKK5UG57CC…

4 6

Ansible oVirt.image-template role
by Jeremy Tourville 10 May '19

10 May '19

I am trying to run an Ansible playbook that doesn't appear to run correctly. I have followed the example from this blog - https://evaryont.me/blog/2018/09/getting-started-with-vagrant-and-ovirt-fro… The playbook finishes with an ok status but the template never gets built in Ovirt. I have taken logs from three locations hoping to spot the error: * [root@ansible ansible]#ansible-playbook -vvvv runsetup.yml * [root@ansible ansible]# less /var/log/ansible.log * [root@engine ~]# tail -f /var/log/messages (while the playbook is being run. The server Ansible is my control node and Engine is my managed host. Can anyone help me interpret the attached logs in an effort to further troubleshoot? Thanks!

3 2

Re: Ovirt nodeNG RDMA support?
by Strahil 10 May '19

10 May '19

I saw you are using gluster v5.3 . Any reason not to update to 5.5 ? It is quite more stable than 5.3 and some enhancements were done. Best Regards, Strahil NikolovOn May 10, 2019 00:13, michael(a)wanderingmad.com wrote: > > Tried that, get this error: > > > [root@Icarus ~]# gluster volume stop storage_ssd > Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y > volume stop: storage_ssd: success > [root@Icarus ~]# gluster volume set storage_ssd config.transport tcp,rdma > volume set: failed: Commit failed on localhost. Please check the log file for more details. > and here is the glusterd.log > > [2019-05-09 21:10:45.945855] W [MSGID: 101095] [xlator.c:456:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/5.3/xlator/nfs/server.so: cannot open shared object file: No such file or directory > [2019-05-09 21:10:46.041341] I [MSGID: 106521] [glusterd-op-sm.c:2953:glusterd_op_set_volume] 0-management: changing transport-type for volume storage_ssd to tcp,rdma > [2019-05-09 21:10:46.041965] W [MSGID: 101095] [xlator.c:180:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/5.3/xlator/nfs/server.so: cannot open shared object file: No such file or di > rectory > [2019-05-09 21:10:46.059356] E [MSGID: 106068] [glusterd-volgen.c:1025:volgen_write_volfile] 0-management: failed to create volfile > [2019-05-09 21:10:46.059394] E [glusterd-volgen.c:6556:glusterd_create_volfiles] 0-management: Could not generate gfproxy client volfiles > [2019-05-09 21:10:46.059406] E [MSGID: 106068] [glusterd-op-sm.c:3062:glusterd_op_set_volume] 0-management: Unable to create volfile for 'volume set' > [2019-05-09 21:10:46.059420] E [MSGID: 106122] [glusterd-syncop.c:1434:gd_commit_op_phase] 0-management: Commit of operation 'Volume Set' failed on localhost > [2019-05-09 21:10:46.062304] E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler > [root@prometheus ~]# > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HJGBS3DVBUDVN…

1 0

Re: Migrating Domain Storage Gluster
by Strahil 10 May '19

10 May '19

If this is replica 2 arbiter 1 (old name replica 3 arbiter 1) or a plain replica 3 volume - you don't need the downtime. Just stop the bricks on one of the nodes. Mount (and verify) those SSDs on the same location and use the gluster's reset brick option. Wait for the heal to complete and repeat with the other node(s). Best Regards, Strahil NikolovOn May 9, 2019 21:00, Alex McWhirter <alex(a)triadic.us> wrote: > > Basically i want to take out all of the HDD's in the main gluster pool, > and replace with SSD's. > > My thought was to put everything in maintenance, copy the data manually > over to a transient storage server. Destroy the gluster volume, swap in > all the new drives, build a new gluster volume with the same name / > settings, move data back, and be done. > > Any thoughts on this? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TP6V2OYG5ZXPU…

1 0

Re: HostedEngine cleaned up
by Strahil 10 May '19

10 May '19

This is due to sharding. I joined ovirt 6 moths ago and this option was still there. Best Regards, Strahil NikolovOn May 9, 2019 18:04, Dmitry Filonov <filonov(a)hkl.hms.harvard.edu> wrote: > > The data chunks are under .glusterfs folder on bricks now. Not a single huge file you can easily access from a brick. > Not sure when that change was introduced though. > > Fil > > > On Thu, May 9, 2019, 10:43 AM <olaf.buitelaar(a)gmail.com> wrote: >> >> It looks like i've got the exact same issue; >> drwxr-xr-x. 2 vdsm kvm 4.0K Mar 29 16:01 . >> drwxr-xr-x. 22 vdsm kvm 4.0K Mar 29 18:34 .. >> -rw-rw----. 1 vdsm kvm 64M Feb 4 01:32 44781cef-173a-4d84-88c5-18f7310037b4 >> -rw-rw----. 1 vdsm kvm 1.0M Oct 16 2018 44781cef-173a-4d84-88c5-18f7310037b4.lease >> -rw-r--r--. 1 vdsm kvm 311 Mar 29 16:00 44781cef-173a-4d84-88c5-18f7310037b4.meta >> Within the meta file the image is marked legal and reports a size of SIZE=41943040, interestingly the format is mark RAW, while it was a thinly created volume. >> My suspicion is that something went wrong while the volume was being livemigrated, and somehow the merging of the images broke the volume. >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UDPJ2R5XUFNZR…

1 0

Ovirt nodeNG RDMA support?
by michael＠wanderingmad.com 09 May '19

09 May '19

When I was able to load CentosOS as a host OS, Was able to use RDMA, but it seems like the 4.3x branch of nodeNG is missing RDMA support? I enabled rdma and started the service, but gluster refuses to recognize that RDMA is available and always reports RDMA port as 0 and when I try to make a new drive with tcp,rdma transport options, it always fails.

4 6

Need VM run once api
by Chandrahasa S 09 May '19

09 May '19

This is a multipart message in MIME format. --=_alternative 00361B2065257E90_= Content-Type: text/plain; charset="US-ASCII" Hi Experts, We are integrating ovirt with our internal cloud. Here we installed cloudinit in vm and then converted vm to template. We deploy template with initial run parameter Hostname, IP Address, Gateway and DNS. but when we power ON initial, run parameter is not getting pushed to inside the vm. But its working when we power on VM using run once option on Ovirt portal. I believe we need to power ON vm using run once API, but we are not able get this API. Can some one help on this. I got reply on this query last time but unfortunately mail got deleted. Thanks & Regards Chandrahasa S =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 00361B2065257E90_= Content-Type: text/html; charset="US-ASCII" Hi Experts, We are integrating ovirt with our internal cloud. Here we installed cloudinit in vm and then converted vm to template. We deploy template with initial run parameter Hostname, IP Address, Gateway and DNS. but when we power ON initial, run parameter is not getting pushed to inside the vm. But its working when we power on VM using run once option on Ovirt portal. I believe we need to power ON vm using run once API, but we are not able get this API. Can some one help on this. I got reply on this query last time but unfortunately mail got deleted. Thanks & Regards Chandrahasa S =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 00361B2065257E90_=--

5 4

Disk stuck initializing
by Mikael Öhman 09 May '19

09 May '19

I created a extra disk to attach to a VM, which I used for several months. When it was time to remove it (as I intended to replace it) I managed to detach it, but before I could remove it I got it stuck in with status "initializing". I wish to delete this disk, as I'm done using it, but all options are grayed out in the UI. The disk is not attached to any anything. The underlying storage domain, which is running GlusterFS across the 3 oVirt hypervisors is showing no issues. Several other disks are running on with no issues. The only thing I could find in the engine log was 2019-05-09 17:03:39,693+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (ServerService Thread Pool -- 72) [d3615da6-823c-4421-ad00-6d8060b8b291] Lock Acquired to object 'EngineLock:{exclusiveLocks='', sharedLocks='[0498e532-a1de-4281-953d-7dec31271437=DISK]'}' What can I do to clean this up and free the used space? Best regards, Mikael

1 0

LDAP - not able to find members of groups
by Timmi 09 May '19

09 May '19

Hi oVirt List, I manage to connect oVirt to my LDAP and I'm able to search for users and groups. I'm using openLDAP within a ClearOS installation and it looks like this is a bit different to the standard openLDAP. Inside the LDAP groups there is an attribute with is calls "member". Example: member cn=Timmi,ou=Users,ou=Accounts,dc=domain,dc=com Is someone able to help me how to make sure that oVirt is able to join the users to the groups? Best regards Timmi

2 2

Logical interface naming issues
by Tom Edwards 09 May '19

09 May '19

Hello oVirt community, Seems lik a bug. I don't have more than one environment to test on so I can't be 100% sure and didn't want to file a report (but didn't know where else to report this). I have a fresh install self hosted ovirt cluster 4.3.1.1-1.el7. When I build any logical network adapter with a "-" in the name ex "guest-network-01" the network interface names appear on the hosts (using ip addr command) as garbled names like on8cd19bc011414. They still appear to work, but when you try to make a VNic profile based on the broken name the VMs fail to boot, the VM has to be killed via command line on each host afterwards (they try to boot and hang on all hosts in the cluster corrupting the disk of the VM) because it can't find the parent logical network interface by name. Example errors: VM Security-Onion is down with error. Exit message: (1, 'Cannot find device "guest-dmz-ne"\n', ['/sbin/tc', 'qdisc', 'add', 'dev', 'guest-dmz-network', 'ingress']). VDSM ovirt-2 command DestroyVDS failed: General Exception: ('(1, \'Cannot find device "guest-dmz-ne"\\n\', [\'/sbin/tc\', \'filter\', \'show\', \'dev\', \'guest-dmz-network\', \'parent\', \'ffff:\'])',) That took me a very long time to figure out and broke many vms in the process =(

2 1

many 4.2 leftovers after upgrade 4.3.3
by Arman Khalatyan 08 May '19

08 May '19

Hello everybody, after the upgrade of ovirt-engine node I have several packages still pointing from 4.2 repo. Actually everything is working as expected. yum clean all&& yum upgrade does not find any updates, but reinstall bringing same packages from the 4.3 repo for example: *yum reinstall safelease.x86_64 Loaded plugins: changelog, fastestmirror, langpacks, vdsmupgrade, versionlockRepository centos-sclo-rh-release is listed more than once in the configurationLoading mirror speeds from cached hostfile * base: centos.mirrors.as250.net <http://centos.mirrors.as250.net> * centos-qemu-ev: ftp.rz.uni-frankfurt.de <http://ftp.rz.uni-frankfurt.de> * extras: ftp.rrzn.uni-hannover.de <http://ftp.rrzn.uni-hannover.de> * ovirt-4.3: ftp.nluug.nl <http://ftp.nluug.nl> * ovirt-4.3-epel: mirror.infonline.de <http://mirror.infonline.de> * updates: centos.mirrors.as250.net <http://centos.mirrors.as250.net>Resolving Dependencies--> Running transaction check---> Package safelease.x86_64 0:1.0-7.el7 will be reinstalled--> Finished Dependency ResolutionDependencies Resolved============================================================================================================================================================================================== Package Arch Version Repository Size==============================================================================================================================================================================================Reinstalling: safelease x86_64 1.0-7.el7 ovirt-4.3-centos-ovirt43 21 kTransaction Summary==============================================================================================================================================================================================Reinstall 1 PackageTotal download size: 21 kInstalled size: 43 kIs this ok [y/d/N]: * But we have many others, should I reinstall them manually to get right packages? *yum list installed | grep ovirt-4.2Repository centos-sclo-rh-release is listed more than once in the configurationcollectd.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-disk.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-postgresql.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-write_http.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-write_syslog.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolsgdeploy.noarch 2.0.8-1.el7 @ovirt-4.2-centos-gluster312nbdkit.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-python-common.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-python2.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-vddk.x86_64 1.2.7-2.el7 @ovirt-4.2-epelovirt-ansible-disaster-recovery.noarch 1.1.4-1.el7 @ovirt-4.2ovirt-ansible-image-template.noarch 1.1.9-1.el7 @ovirt-4.2ovirt-ansible-manageiq.noarch 1.1.13-1.el7 @ovirt-4.2ovirt-ansible-roles.noarch 1.1.6-1.el7 @ovirt-4.2ovirt-engine-cli.noarch 3.6.9.2-1.el7.centos @ovirt-4.2ovirt-js-dependencies.noarch 1.2.0-3.1.el7.centos @ovirt-4.2python-linecache2.noarch 1.0.0-1.el7 @ovirt-4.2-centos-ovirt42python-testtools.noarch 1.8.0-2.el7 @ovirt-4.2-centos-ovirt42python2-asn1crypto.noarch 0.23.0-2.el7 @ovirt-4.2-centos-ovirt42python2-cffi.x86_64 1.11.2-1.el7 @ovirt-4.2-centos-ovirt42python2-chardet.noarch 3.0.4-7.el7 @ovirt-4.2-centos-opstoolspython2-crypto.x86_64 2.6.1-16.el7 @ovirt-4.2-epelpython2-cryptography.x86_64 2.1.4-2.el7 @ovirt-4.2-centos-ovirt42python2-ecdsa.noarch 0.13-10.el7 @ovirt-4.2-epelpython2-extras.noarch 1.0.0-2.el7 @ovirt-4.2-centos-ovirt42python2-fixtures.noarch 3.0.0-7.el7 @ovirt-4.2-centos-ovirt42python2-idna.noarch 2.5-1.el7 @ovirt-4.2-centos-opstoolspython2-pyOpenSSL.noarch 17.3.0-3.el7 @ovirt-4.2-centos-ovirt42python2-pysocks.noarch 1.5.6-3.el7 @ovirt-4.2-centos-opstoolspython2-requests.noarch 2.19.1-4.el7 @ovirt-4.2-centos-opstoolspython2-traceback2.noarch 1.4.0-14.el7 @ovirt-4.2-centos-ovirt42python2-urllib3.noarch 1.21.1-1.el7 @ovirt-4.2-centos-opstoolssafelease.x86_64 1.0-7.el7 @ovirt-4.2-centos-ovirt42vdsm-jsonrpc-java.noarch 1.4.15-1.el7 @ovirt-4.2* Thanks,Arman.

2 2

EVENT_ID not generated for VM Reboot
by Sigbjorn Lie-Soland 08 May '19

08 May '19

Hi list, When a user powers down a VM from within the VM operating system (poweroff), a "moved from 'Up' --> 'Down'" message is written to engine.log, and a EVENT_ID: VM_DOWN is created -- 2019-05-08 20:53:03,495+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'Down' 2019-05-08 20:53:03,550+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: VM_DOWN(61), VM vmname1 is down. Exit message: User shut down from within the guest -- When a user starts a VM from the webadmin, a "moved from 'WaitForLaunch' --> 'PoweringUp'" and "'PoweringUp' --> 'Up'" is written to engine.log, and the events EVENT_ID: USER_STARTED_VM and EVENT_ID: USER_RUN_VM is created. -- 2019-05-08 20:53:20,976+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1388598) [xxxxxxxx-da2d-452d-a604-xxxxxxxxxxxx] EVENT_ID: USER_STARTED_VM(153), VM vmname1 was started by adminuser@ipadomain (Host: hypervisor1). 2019-05-08 20:53:24,091+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'WaitForLaunch' --> 'PoweringUp' 2019-05-08 20:53:45,140+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'PoweringUp' --> 'Up' 2019-05-08 20:53:45,238+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: USER_RUN_VM(32), VM vmname1 started on Host hypervisor1 -- However when a user reboots a VM from within the VM operating system, the messages "moved from 'Up' --> 'RebootInProgress'" and "moved from 'RebootInProgress' --> 'Up'" is written to the engine.log, but no EVENT_ID is generated. -- -- 2019-05-08 20:52:27,367+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'RebootInProgress' 2019-05-08 20:52:49,926+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'RebootInProgress' --> 'Up' -- So systems like CloudForms/ManageIQ which reads the manager event log via the manager REST API is not notified when a VM is rebooted, and is therefore unable to perform any EmsEvent when the VM reboots. Why is there no EVENT_ID generated when a VM reboots? Is it possible to enable EVENT_ID's to be created for VM reboot events? Regards, Siggi

1 0