[ovirt-users] unlock_entity.sh oVirt 4.2

2018-01-12 Thread Grundmann, Christian
Hi,
i have a VM on oVirt 4.2 which is locked after a snapshot revert.

i unlocked the disk/snapshot and vm with unlock_entity.sh

it now shows no locks

/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all -q
Locked VMs:

Locked templates:

Locked disks:

Locked snapshots:


But the VM still shows "Image Locked"

How can I unlock them?

Thx Christian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] node ng upgrade failed

2017-07-10 Thread Grundmann, Christian
cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Wed Dec 14 15:19:56 2016
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/onn_cs-kvm-001/ovirt-node-ng-4.1.2-0.20170523.0+1 / xfs defaults,discard 0 0
UUID=7899e80f-5066-4eca-a7d6-afa52a512039 /boot   ext4
defaults1 2
UUID=42B1-C1A3  /boot/efi   vfat
umask=0077,shortname=winnt 0 0
/dev/mapper/onn_cs--kvm--001-var /var xfs defaults,discard 0 0
/dev/mapper/onn_cs--kvm--001-swap swapswapdefaults  
  0 0

mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs 
(rw,nosuid,seclabel,size=49382320k,nr_inodes=12345580,mode=755)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,seclabel,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mapper/onn_cs--kvm--001-ovirt--node--ng--4.1.2--0.20170523.0+1 on / type 
xfs 
(rw,relatime,seclabel,attr2,inode64,logbsize=64k,sunit=128,swidth=128,noquota)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=34,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/mapper/3600605b003af3f301666cedd1935887c2 on /boot type ext4 
(rw,relatime,seclabel,data=ordered)
/dev/mapper/onn_cs--kvm--001-var on /var type xfs 
(rw,relatime,seclabel,attr2,discard,inode64,logbsize=64k,sunit=128,swidth=128,noquota)
/dev/mapper/3600605b003af3f301666cedd1935887c1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
tmpfs on /run/user/0 type tmpfs 
(rw,nosuid,nodev,relatime,seclabel,size=9881988k,mode=700)


Von: Ryan Barry [mailto:rba...@redhat.com]
Gesendet: Montag, 10. Juli 2017 14:09
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: Yuval Turgeman <yuv...@redhat.com>; users@ovirt.org
Betreff: Re: [ovirt-users] node ng upgrade failed

What does `mount` look like? I'm wondering whether /var/log is already a 
partition/in fstab or whether os.path.ismount is confused here.

On Mon, Jul 10, 2017 at 7:48 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,
no I did no custom partitioning I used the autopartition from installer
the upgrade did work until some version (don’t know which)

here my nodectl check output

nodectl check
Status: OK
Bootloader ... OK
  Layer boot entries ... OK
  Valid boot entries ... OK
Mount points ... OK
  Separate /var ... OK
  Discard is used ... OK
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK
vdsmd ... OK

Thx Christian


Von: Ryan Barry [mailto:rba...@redhat.com<mailto:rba...@redhat.com>]
Gesendet: Montag, 10. Juli 2017 13:39
An: Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fa

Re: [ovirt-users] node ng upgrade failed

2017-07-10 Thread Grundmann, Christian
Hi,
no I did no custom partitioning I used the autopartition from installer
the upgrade did work until some version (don’t know which)

here my nodectl check output

nodectl check
Status: OK
Bootloader ... OK
  Layer boot entries ... OK
  Valid boot entries ... OK
Mount points ... OK
  Separate /var ... OK
  Discard is used ... OK
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK
vdsmd ... OK

Thx Christian


Von: Ryan Barry [mailto:rba...@redhat.com]
Gesendet: Montag, 10. Juli 2017 13:39
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: Yuval Turgeman <yuv...@redhat.com>; users@ovirt.org
Betreff: Re: [ovirt-users] node ng upgrade failed

Christian -
It looks like perhaps you used custom partitioning. That's ok -- we support 
that. We check for the existence of partitions here:

https://gerrit.ovirt.org/gitweb?p=imgbased.git;a=blob;f=src/imgbased/plugins/osupdater.py;h=032d7e95d475b1085dab7c3f776873f6d6d4a280;hb=HEAD#l180
It's possible that os.path.ismount doesn't think /var/log is a mount for some 
reason. We'll try to reproduce. But can you provide a little more information 
about your environment? Did you use autopartitioning or custom partitioning?

On Mon, Jul 10, 2017 at 7:16 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
attached

Von: Yuval Turgeman [mailto:yuv...@redhat.com<mailto:yuv...@redhat.com>]
Gesendet: Montag, 10. Juli 2017 13:10
An: Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>>
Cc: users@ovirt.org<mailto:users@ovirt.org>
Betreff: Re: [ovirt-users] node ng upgrade failed

Hi,

Can you please attach /tmp/imgbased.log ?

Thanks,
Yuval.


On Mon, Jul 10, 2017 at 11:27 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,
I tried to update to node ng 4.1.3 (from 4.1.1) which failed

Jul 10 10:10:49 imgbased: 2017-07-10 10:10:49,986 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170709.0.el7.squashfs.img'
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] Starting base creation
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170709.0
Jul 10 10:10:51 imgbased: 2017-07-10 10:10:51,539 [INFO] New LV is: 
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,070 [INFO] Creating new 
filesystem on base
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,412 [INFO] Writing tree to base
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,345 [INFO] New layer will be: 

Jul 10 10:12:52 imgbased: 2017-07-10 10:12:52,714 [ERROR] Failed to migrate 
etc#012Traceback (most recent call last):#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 119, in on_new_layer#012check_nist_layout(imgbase, new_lv)#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 173, in check_nist_layout#012v.create(t, paths[t]["size"], 
paths[t]["attach"])#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create#012"Path is already a volume: %s" % where#012AssertionError: 
Path is already a volume: /var/log
Jul 10 10:12:53 python: detected unhandled Python exception in 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:12:53 abrt-server: Executable 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'
Jul 10 10:15:10 imgbased: 2017-07-10 10:15:10,079 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170622.0.el7.squashfs.img'
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] Starting base creation
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170622.0
Jul 10 10:15:11 python: detected unhandled Python exception in 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:15:12 abrt-server: Executable 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'


How can I fix it?

Thx Christian

___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org&

Re: [ovirt-users] node ng upgrade failed

2017-07-10 Thread Grundmann, Christian
attached

Von: Yuval Turgeman [mailto:yuv...@redhat.com]
Gesendet: Montag, 10. Juli 2017 13:10
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] node ng upgrade failed

Hi,

Can you please attach /tmp/imgbased.log ?

Thanks,
Yuval.


On Mon, Jul 10, 2017 at 11:27 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,
I tried to update to node ng 4.1.3 (from 4.1.1) which failed

Jul 10 10:10:49 imgbased: 2017-07-10 10:10:49,986 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170709.0.el7.squashfs.img'
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] Starting base creation
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170709.0
Jul 10 10:10:51 imgbased: 2017-07-10 10:10:51,539 [INFO] New LV is: 
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,070 [INFO] Creating new 
filesystem on base
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,412 [INFO] Writing tree to base
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,345 [INFO] New layer will be: 

Jul 10 10:12:52 imgbased: 2017-07-10 10:12:52,714 [ERROR] Failed to migrate 
etc#012Traceback (most recent call last):#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 119, in on_new_layer#012check_nist_layout(imgbase, new_lv)#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 173, in check_nist_layout#012v.create(t, paths[t]["size"], 
paths[t]["attach"])#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create#012"Path is already a volume: %s" % where#012AssertionError: 
Path is already a volume: /var/log
Jul 10 10:12:53 python: detected unhandled Python exception in 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:12:53 abrt-server: Executable 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'
Jul 10 10:15:10 imgbased: 2017-07-10 10:15:10,079 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170622.0.el7.squashfs.img'
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] Starting base creation
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170622.0
Jul 10 10:15:11 python: detected unhandled Python exception in 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:15:12 abrt-server: Executable 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'


How can I fix it?

Thx Christian

___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users



imgbased.log
Description: imgbased.log
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] node ng upgrade failed

2017-07-10 Thread Grundmann, Christian
Hi,
I tried to update to node ng 4.1.3 (from 4.1.1) which failed

Jul 10 10:10:49 imgbased: 2017-07-10 10:10:49,986 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170709.0.el7.squashfs.img'
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] Starting base creation
Jul 10 10:10:50 imgbased: 2017-07-10 10:10:50,816 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170709.0
Jul 10 10:10:51 imgbased: 2017-07-10 10:10:51,539 [INFO] New LV is: 
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,070 [INFO] Creating new 
filesystem on base
Jul 10 10:10:53 imgbased: 2017-07-10 10:10:53,412 [INFO] Writing tree to base
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer 
after 
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,345 [INFO] New layer will be: 

Jul 10 10:12:52 imgbased: 2017-07-10 10:12:52,714 [ERROR] Failed to migrate 
etc#012Traceback (most recent call last):#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 119, in on_new_layer#012check_nist_layout(imgbase, new_lv)#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/plugins/osupdater.py",
 line 173, in check_nist_layout#012v.create(t, paths[t]["size"], 
paths[t]["attach"])#012  File 
"/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/volume.py", line 
48, in create#012"Path is already a volume: %s" % where#012AssertionError: 
Path is already a volume: /var/log
Jul 10 10:12:53 python: detected unhandled Python exception in 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:12:53 abrt-server: Executable 
'/tmp/tmp.EMsKrrbmZs/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'
Jul 10 10:15:10 imgbased: 2017-07-10 10:15:10,079 [INFO] Extracting image 
'/usr/share/ovirt-node-ng/image//ovirt-node-ng-4.1.3-0.20170622.0.el7.squashfs.img'
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] Starting base creation
Jul 10 10:15:11 imgbased: 2017-07-10 10:15:11,226 [INFO] New base will be: 
ovirt-node-ng-4.1.3-0.20170622.0
Jul 10 10:15:11 python: detected unhandled Python exception in 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py'
Jul 10 10:15:12 abrt-server: Executable 
'/tmp/tmp.pqf2qhifaY/usr/lib/python2.7/site-packages/imgbased/__main__.py' 
doesn't belong to any package and ProcessUnpackaged is set to 'no'


How can I fix it?

Thx Christian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Storage domain experienced a high latency

2017-02-13 Thread Grundmann, Christian
Hi,
I tried around a bit more.

Adding a second Path doesn't change anything

Starting a CentOS 6 VMs works

Starting a CentOS 7.2 (fresh install from release ISO) works
Doing yum update to current 7.2 Mirror (pre 7.3) - reboot - dies shortly after 
boot 


Thx Christian

Von: Nir Soffer [mailto:nsof...@redhat.com] 
Gesendet: Freitag, 10. Februar 2017 21:32
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Storage domain experienced a high latency

On Fri, Feb 10, 2017 at 9:24 PM, Grundmann, Christian 
<mailto:christian.grundm...@fabasoft.com> wrote:
Attached

I don't see anything unusual.

Having one path, your system is very sensitive to 
errors on the single path.

The default ovirt configuration assume that you have several
paths for each device, and is optimized for fast failover when
a path has an error.

This optimization makes your system more fragile when you
have only one path.

I would use this setting:

    no_path_retry 4

This will do 4 retries when all paths are faulty before failing the io.
If you have short outage for some reason, this may hide the issue
on the host.

If you change multipath.conf, you should mark it as private, so 
vdsm will not touch this file on upgrades. To mark the file as
private the second line of the file must be:

# VDSM PRIVATE

To check that your file is considered private, you can run:

# vdsm-tool is-configured
Manual override for multipath.conf detected - preserving current configuration

You should see the message about Manual override.

The real question is why the path failed - did you have anything
in the server logs at that time? did you have issues on other hosts
in the same time?

Nir
 
 
Thx Christian
 
Von: Nir Soffer [mailto:mailto:nsof...@redhat.com] 
Gesendet: Freitag, 10. Februar 2017 17:43

An: Grundmann, Christian <mailto:christian.grundm...@fabasoft.com>
Cc: mailto:users@ovirt.org
Betreff: Re: [ovirt-users] Storage domain experienced a high latency
 
On Thu, Feb 9, 2017 at 10:03 AM, Grundmann, Christian 
<mailto:christian.grundm...@fabasoft.com> wrote:
Hi,

@ Can also be low level issue in kernel, hba, switch, server.
I have the old storage on the same cable so I don’t think its hba or switch 
related
On the same Switch I have a few ESXi Server with same storage setup which are 
working without problems.

@multipath
I use stock ng-node multipath configuration

# VDSM REVISION 1.3

defaults {
    polling_interval            5
    no_path_retry               fail
    user_friendly_names         no
    flush_on_last_del           yes
    fast_io_fail_tmo            5
    dev_loss_tmo                30
    max_fds                     4096
}

# Remove devices entries when overrides section is available.
devices {
    device {
        # These settings overrides built-in devices settings. It does not apply
        # to devices without built-in settings (these use the settings in the
        # "defaults" section), or to devices defined in the "devices" section.
        # Note: This is not available yet on Fedora 21. For more info see
        # https://bugzilla.redhat.com/1253799
        all_devs                yes
        no_path_retry           fail
    }
}

# Enable when this section is available on all supported platforms.
# Options defined here override device specific options embedded into
# multipathd.
#
# overrides {
#      no_path_retry           fail
# }


multipath -r v3
has no output
 
My mistake, the correct command is:
 
multipath -r -v3
 
It creates tons of output, so better redirect to file and attach the file:
 
multipath -r -v3 > multiapth-r-v3.out
 


Thx Christian


Von: Nir Soffer [mailto:mailto:nsof...@redhat.com]
Gesendet: Mittwoch, 08. Februar 2017 20:44
An: Grundmann, Christian <mailto:christian.grundm...@fabasoft.com>
Cc: mailto:users@ovirt.org
Betreff: Re: [ovirt-users] Storage domain experienced a high latency

On Wed, Feb 8, 2017 at 6:11 PM, Grundmann, Christian 
<mailto:mailto:christian.grundm...@fabasoft.com> wrote:
Hi,
got a new FC Storage (EMC Unity 300F) which is seen by my Hosts additional to 
my old Storage for Migration.
New Storage has only on PATH until Migration is done.
I already have a few VMs running on the new Storage without Problem.
But after starting some VMs (don’t really no whats the difference to working 
ones), the Path for new Storage fails.
 
Engine tells me: Storage Domain  experienced a high latency of 
22.4875 seconds from host 
 
Where can I start looking?
 
In /var/log/messages I found:
 
Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: sdd 
- emc_clariion_checker: Active path is healthy.
Feb  8 09:03:53 ovirtnode01 multipathd: 8:48: reinstated
Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: 
remaining active paths: 1
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 8
Feb  8 09:03:53 o

Re: [ovirt-users] Storage domain experienced a high latency

2017-02-09 Thread Grundmann, Christian
Hi,

@ Can also be low level issue in kernel, hba, switch, server.
I have the old storage on the same cable so I don’t think its hba or switch 
related 
On the same Switch I have a few ESXi Server with same storage setup which are 
working without problems.

@multipath
I use stock ng-node multipath configuration

# VDSM REVISION 1.3

defaults {
polling_interval5
no_path_retry   fail
user_friendly_names no
flush_on_last_del   yes
fast_io_fail_tmo5
dev_loss_tmo30
max_fds 4096
}

# Remove devices entries when overrides section is available.
devices {
device {
# These settings overrides built-in devices settings. It does not apply
# to devices without built-in settings (these use the settings in the
# "defaults" section), or to devices defined in the "devices" section.
# Note: This is not available yet on Fedora 21. For more info see
# https://bugzilla.redhat.com/1253799
all_devsyes
no_path_retry   fail
}
}

# Enable when this section is available on all supported platforms.
# Options defined here override device specific options embedded into
# multipathd.
#
# overrides {
#  no_path_retry   fail
# }


multipath -r v3
has no output


Thx Christian


Von: Nir Soffer [mailto:nsof...@redhat.com] 
Gesendet: Mittwoch, 08. Februar 2017 20:44
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Storage domain experienced a high latency

On Wed, Feb 8, 2017 at 6:11 PM, Grundmann, Christian 
<mailto:christian.grundm...@fabasoft.com> wrote:
Hi,
got a new FC Storage (EMC Unity 300F) which is seen by my Hosts additional to 
my old Storage for Migration.
New Storage has only on PATH until Migration is done.
I already have a few VMs running on the new Storage without Problem.
But after starting some VMs (don’t really no whats the difference to working 
ones), the Path for new Storage fails.
 
Engine tells me: Storage Domain  experienced a high latency of 
22.4875 seconds from host 
 
Where can I start looking?
 
In /var/log/messages I found:
 
Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: sdd 
- emc_clariion_checker: Active path is healthy.
Feb  8 09:03:53 ovirtnode01 multipathd: 8:48: reinstated
Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: 
remaining active paths: 1
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 8
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 5833475
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 5833475
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168
Feb  8 09:03:53 ovirtnode01 kernel: Buffer I/O error on dev dm-207, logical 
block 97, async page read
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0
Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168
Feb  8 09:03:53 ovirtnode01 kernel: device-mapper: multipath: Reinstating path 
8:48.
Feb  8 09:03:53 ovirtnode01 kernel: sd 3:0:0:22: alua: port group 01 state A 
preferred supports tolUsNA
Feb  8 09:03:53 ovirtnode01 sanlock[5192]: 2017-02-08 09:03:53+0100 151809 
[11772]: s59 add_lockspace fail result -202
Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)
Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: devmap not registered, can't 
remove
Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)
Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)
Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: devmap not registered, can't 
remove
Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)
Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)
Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: devmap not registered, can't 
remove
Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)
Feb  8 09:04:08 ovirtnode01 kernel: dd: sending ioctl 80306d02 to a partition!
Feb  8 09:04:24 ovirtnode01 sanlock[5192]: 2017-02-08 09:04:24+0100 151840 
[15589]: read_sectors delta_leader offset 2560 rv -202 
/dev/f9b70017-0a34-47bc-bf2f-dfc70200a347/ids
Feb  8 09:04:34 ovirtnode01 sanlock[5192]: 2017-02-08 09:04:34+0100 151850 
[15589]: f9b70017 close_task_aio 0 0x7fd78c0008c0 busy
Feb  8 09:04:39 ovirtnode01 multipathd: 360060

[ovirt-users] Storage domain experienced a high latency

2017-02-08 Thread Grundmann, Christian
Hi,

got a new FC Storage (EMC Unity 300F) which is seen by my Hosts additional to 
my old Storage for Migration.

New Storage has only on PATH until Migration is done.

I already have a few VMs running on the new Storage without Problem.

But after starting some VMs (don't really no whats the difference to working 
ones), the Path for new Storage fails.



Engine tells me: Storage Domain  experienced a high latency of 
22.4875 seconds from host 



Where can I start looking?



In /var/log/messages I found:



Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: sdd 
- emc_clariion_checker: Active path is healthy.

Feb  8 09:03:53 ovirtnode01 multipathd: 8:48: reinstated

Feb  8 09:03:53 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: 
remaining active paths: 1

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 8

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 5833475

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 5833475

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168

Feb  8 09:03:53 ovirtnode01 kernel: Buffer I/O error on dev dm-207, logical 
block 97, async page read

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0

Feb  8 09:03:53 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168

Feb  8 09:03:53 ovirtnode01 kernel: device-mapper: multipath: Reinstating path 
8:48.

Feb  8 09:03:53 ovirtnode01 kernel: sd 3:0:0:22: alua: port group 01 state A 
preferred supports tolUsNA

Feb  8 09:03:53 ovirtnode01 sanlock[5192]: 2017-02-08 09:03:53+0100 151809 
[11772]: s59 add_lockspace fail result -202

Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)

Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: devmap not registered, can't 
remove

Feb  8 09:04:05 ovirtnode01 multipathd: dm-33: remove map (uevent)

Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)

Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: devmap not registered, can't 
remove

Feb  8 09:04:06 ovirtnode01 multipathd: dm-34: remove map (uevent)

Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)

Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: devmap not registered, can't 
remove

Feb  8 09:04:08 ovirtnode01 multipathd: dm-33: remove map (uevent)

Feb  8 09:04:08 ovirtnode01 kernel: dd: sending ioctl 80306d02 to a partition!

Feb  8 09:04:24 ovirtnode01 sanlock[5192]: 2017-02-08 09:04:24+0100 151840 
[15589]: read_sectors delta_leader offset 2560 rv -202 
/dev/f9b70017-0a34-47bc-bf2f-dfc70200a347/ids

Feb  8 09:04:34 ovirtnode01 sanlock[5192]: 2017-02-08 09:04:34+0100 151850 
[15589]: f9b70017 close_task_aio 0 0x7fd78c0008c0 busy

Feb  8 09:04:39 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: sdd 
- emc_clariion_checker: Read error for WWN 60060160422143002a38935800ae2760.  
Sense data are 0x0/0x0/0x0.

Feb  8 09:04:39 ovirtnode01 multipathd: checker failed path 8:48 in map 
360060160422143002a38935800ae2760

Feb  8 09:04:39 ovirtnode01 multipathd: 360060160422143002a38935800ae2760: 
remaining active paths: 0

Feb  8 09:04:39 ovirtnode01 kernel: qla2xxx [:11:00.0]-801c:3: Abort 
command issued nexus=3:0:22 --  1 2002.

Feb  8 09:04:39 ovirtnode01 kernel: device-mapper: multipath: Failing path 8:48.

Feb  8 09:04:40 ovirtnode01 kernel: qla2xxx [:11:00.0]-801c:3: Abort 
command issued nexus=3:0:22 --  1 2002.

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: 8 callbacks suppressed

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967168

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 4294967280

Feb  8 09:04:42 ovirtnode01 kernel: blk_update_request: I/O error, dev dm-10, 
sector 0





multipath -ll output for this Domain



360060160422143002a38935800ae2760 dm-10 DGC ,VRAID

size=2.0T features='1 retain_attached_hw_handler' hwhandler='1 alua' wp=rw

`-+- policy='service-time 0' prio=50 status=active

  `- 3:0:0:22 sdd 8:48  active ready  running





Thx Christian





___
Users mailing list
Users@ovirt.org

Re: [ovirt-users] Storage Domain sizing

2017-01-23 Thread Grundmann, Christian
Hi,

thx for you input

both aren’t problems for me, all domains are from the same storage and so can’t 
be maintained independently.



Are there performance problems with only one Domain (like waiting for locks 
etc.) which I don’t have that much with multiple?



Thx Christian





Von: Maor Lipchuk [mailto:mlipc...@redhat.com]
Gesendet: Montag, 23. Jänner 2017 15:32
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Storage Domain sizing



There are many factors that can be discussed on this issue,

two things that pop up on my mind are that many storage domains will make your 
Data Center be more robust and flexible, since you can maintain part of the 
storage domains which could help with upgrading your storage server in the 
future or fixing issues that might occur in your storage, without moving your 
Data Center to a non operational state.



One storage domain is preferrable if you want to use large disks with your VMs 
that small storage domains does not have the capacity to do so



Regards,

Maor



On Mon, Jan 23, 2017 at 9:52 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:

   Hi,

   Ii am about to migrate to a new storage.

   Whats the best practice in sizing?

   1 big Storage Domain or multiple smaller ones?



   My current Setup:

   11 Hosts

   7 FC Storage Domains 1 TB each



   Can anyone tell me the pro and cons of 1 vs. many?





   Thx Christian


   ___
   Users mailing list
   Users@ovirt.org<mailto:Users@ovirt.org>
   http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Storage Domain sizing

2017-01-22 Thread Grundmann, Christian
Hi,

Ii am about to migrate to a new storage.

Whats the best practice in sizing? 

1 big Storage Domain or multiple smaller ones?

 

My current Setup:

11 Hosts

7 FC Storage Domains 1 TB each

 

Can anyone tell me the pro and cons of 1 vs. many?

 

 

Thx Christian



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] WG: High Database Load after updating to oVirt 4.0.4

2017-01-12 Thread Grundmann, Christian
Hi,
ok will write a bug

Setup:
8 Nodes
Around 100 VMs running all the time
100-200 VMs dynamically created and destroyed from template using vagrant
Around 2 disks per VM
7 Storage Domains around 1TB each

Christian





Von: Roy Golan [mailto:rgo...@redhat.com]
Gesendet: Donnerstag, 12. Jänner 2017 13:41
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] WG: High Database Load after updating to oVirt 4.0.4


On 11 January 2017 at 17:16, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
| select * from  getdisksvmguid($1, $2, $3, $4)


At the moment its best that you open a bug and put all the info there.
I can tell that other setups, even big setup, didn't experience that
so I guess some env factor is hiding here. How big is your setup, 
hosts/vm/disks/domains?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] WG: High Database Load after updating to oVirt 4.0.4

2017-01-12 Thread Grundmann, Christian
Hi,

I already did the downgrade again because this is a showstopper. 4.0.3 is the 
last working Version for me

I have attached a full pg_stat_activity output from last try



Thx Christian



Von: Roy Golan [mailto:rgo...@redhat.com]
Gesendet: Donnerstag, 12. Jänner 2017 09:13
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] WG: High Database Load after updating to oVirt 4.0.4







On 11 January 2017 at 17:16, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:

   Hi,

   I updated to 4.0.6 today and again hitting this Problem can anyone plz help?



backend_start |  query_start  | 
state_change  | waiting |state| 
 query

   
---+---+---+-+-+--

   2017-01-11 15:52:41.612942+01 | 2017-01-11 16:14:45.676881+01 | 2017-01-11 
16:14:45.676882+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 15:52:35.526771+01 | 2017-01-11 16:14:45.750546+01 | 2017-01-11 
16:14:45.750547+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 14:48:41.133303+01 | 2017-01-11 16:14:42.89794+01  | 2017-01-11 
16:14:42.897991+01 | f   | idle| SELECT 1

   2017-01-11 14:48:43.504048+01 | 2017-01-11 16:14:46.794742+01 | 2017-01-11 
16:14:46.794813+01 | f   | idle| SELECT option_value FROM 
vdc_options WHERE option_name = 'DisconnectDwh'

   2017-01-11 14:48:43.531955+01 | 2017-01-11 16:14:34.541273+01 | 2017-01-11 
16:14:34.543513+01 | f   | idle| COMMIT

   2017-01-11 14:48:43.564148+01 | 2017-01-11 16:14:34.543635+01 | 2017-01-11 
16:14:34.544145+01 | f   | idle| COMMIT

   2017-01-11 14:48:43.569029+01 | 2017-01-11 16:00:01.86664+01  | 2017-01-11 
16:00:01.866711+01 | f   | idle in transaction | SELECT 'continueAgg', '1'  
 +

  |   | 
  | | | FROM history_configuration  
+

  |   | 
  | | | WHERE var_name = 
'lastHourAggr' +

  |   | 
  | | | AND var_datetime < 
'2017-01-11 15:00:00.00+0100'+

  |   | 
  | | |

   2017-01-11 14:48:43.572644+01 | 2017-01-11 14:48:43.57571+01  | 2017-01-11 
14:48:43.575736+01 | f   | idle| SET extra_float_digits = 3

   2017-01-11 14:48:43.577039+01 | 2017-01-11 14:48:43.580066+01 | 2017-01-11 
14:48:43.58009+01  | f   | idle| SET extra_float_digits = 3

   2017-01-11 14:48:54.308078+01 | 2017-01-11 16:14:46.931422+01 | 2017-01-11 
16:14:46.931423+01 | f   | active  | select * from  
getsnapshotbyleafguid($1)

   2017-01-11 14:48:54.465485+01 | 2017-01-11 16:14:21.113926+01 | 2017-01-11 
16:14:21.113959+01 | f   | idle| COMMIT

   2017-01-11 15:52:41.606561+01 | 2017-01-11 16:14:45.839754+01 | 2017-01-11 
16:14:45.839755+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 14:48:56.477555+01 | 2017-01-11 16:14:45.276255+01 | 2017-01-11 
16:14:45.277038+01 | f   | idle| select * from  
getvdsbyvdsid($1, $2, $3)

   2017-01-11 15:52:41.736304+01 | 2017-01-11 16:14:44.48134+01  | 2017-01-11 
16:14:44.48134+01  | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 14:48:56.489949+01 | 2017-01-11 16:14:46.40924+01  | 2017-01-11 
16:14:46.409241+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 15:52:41.618773+01 | 2017-01-11 16:14:45.732394+01 | 2017-01-11 
16:14:45.732394+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

   2017-01-11 14:48:56.497824+01 | 2017-01-11 16:14:46.827751+01 | 2017-01-11 
16:14:46.827752+01 | f   | active  | select * from  
getsnapshotbyleafguid($1)

   2017-01-11 14:48:56.497732+01 | 2017-01-11 16:09:04.207597+01 | 2017-01-11 
16:09:04.342567+01 | f   | idle| select * from  
getvdsbyvdsid($1, $2, 

[ovirt-users] WG: High Database Load after updating to oVirt 4.0.4

2017-01-11 Thread Grundmann, Christian
-01-11 
16:14:46.074258+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

2017-01-11 16:06:24.660881+01 | 2017-01-11 16:13:39.930702+01 | 2017-01-11 
16:13:39.95559+01  | f   | idle| select * from  
getvdsbyvdsid($1, $2, $3)

2017-01-11 16:06:24.690863+01 | 2017-01-11 16:07:28.763627+01 | 2017-01-11 
16:07:28.763684+01 | f   | idle| select * from  
getqosbyqosid($1)

2017-01-11 16:06:26.244997+01 | 2017-01-11 16:14:45.760047+01 | 2017-01-11 
16:14:45.760048+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

2017-01-11 16:06:26.359194+01 | 2017-01-11 16:14:46.90043+01  | 2017-01-11 
16:14:46.929003+01 | f   | idle| select * from  
getvdsbyvdsid($1, $2, $3)

2017-01-11 16:06:26.377649+01 | 2017-01-11 16:14:45.035936+01 | 2017-01-11 
16:14:45.035937+01 | f   | active  | select * from  
getdisksvmguid($1, $2, $3, $4)

2017-01-11 16:06:40.128282+01 | 2017-01-11 16:12:43.764245+01 | 2017-01-11 
16:12:43.764293+01 | f   | idle| select * from  
getqosbyqosid($1)

2017-01-11 16:06:40.150762+01 | 2017-01-11 16:10:54.629416+01 | 2017-01-11 
16:10:54.629496+01 | f   | idle| select * from  
getstoragedomainidsbystoragepoolidandstatus($1, $2)

2017-01-11 16:14:46.934168+01 | 2017-01-11 16:14:46.964807+01 | 2017-01-11 
16:14:46.964809+01 | f   | active  | select 
backend_start,query_start,state_change,waiting,state,query from 
pg_stat_activity;



top - 16:13:43 up  1:36,  3 users,  load average: 41.62, 37.53, 21.37

Tasks: 286 total,  40 running, 246 sleeping,   0 stopped,   0 zombie

%Cpu(s): 99.3 us,  0.6 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st

KiB Mem : 16432648 total,  3626184 free,  6746368 used,  6060096 buff/cache

KiB Swap:  5242876 total,  5242876 free,0 used.  8104244 avail Mem



  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND

17328 postgres  20   0 3485020  66760  20980 R  21.5  0.4   1:37.27 postgres: 
engine engine 127.0.0.1(35212) SELECT

8269 postgres  20   0 3484796  68200  22780 R  21.2  0.4   2:15.36 postgres: 
engine engine 127.0.0.1(47116) SELECT

9016 postgres  20   0 3520356 279756 199452 R  21.2  1.7   7:24.29 postgres: 
engine engine 127.0.0.1(42992) SELECT

16878 postgres  20   0 3498100  66160  18468 R  21.2  0.4   2:00.82 postgres: 
engine engine 127.0.0.1(34238) SELECT

16751 postgres  20   0 3486388 215784 169404 R  20.9  1.3   1:56.38 postgres: 
engine engine 127.0.0.1(34008) SELECT

17868 postgres  20   0 3487860 215472 167796 R  20.9  1.3   1:07.40 postgres: 
engine engine 127.0.0.1(36312) SELECT

8272 postgres  20   0 3490392  76912  25288 R  20.5  0.5   2:30.15 postgres: 
engine engine 127.0.0.1(47124) SELECT

8274 postgres  20   0 3495800  83144  26100 R  20.5  0.5   2:56.66 postgres: 
engine engine 127.0.0.1(47130) SELECT

9015 postgres  20   0 3523344 283388 198908 R  20.5  1.7   7:19.91 postgres: 
engine engine 127.0.0.1(42990) SELECT

16879 postgres  20   0 3488296  72180  23744 R  20.5  0.4   1:30.01 postgres: 
engine engine 127.0.0.1(34242) SELECT

17241 postgres  20   0 3486540 215716 168024 R  20.5  1.3   1:47.58 postgres: 
engine engine 127.0.0.1(35018) SELECT

17242 postgres  20   0 3495864  69172  20988 R  20.5  0.4   1:54.09 postgres: 
engine engine 127.0.0.1(35022) SELECT

17668 postgres  20   0 3488576  54484  15080 R  20.5  0.3   1:28.91 postgres: 
engine engine 127.0.0.1(35896) SELECT

8266 postgres  20   0 3490688 222344 170852 R  20.2  1.4   2:58.95 postgres: 
engine engine 127.0.0.1(47112) SELECT

8268 postgres  20   0 3503420 241888 177500 R  20.2  1.5   3:10.34 postgres: 
engine engine 127.0.0.1(47117) SELECT

8275 postgres  20   0 3510316 253340 181688 R  20.2  1.5   4:12.02 postgres: 
engine engine 127.0.0.1(47132) SELECT

9014 postgres  20   0 3523872 284636 199424 R  20.2  1.7   7:51.82 postgres: 
engine engine 127.0.0.1(42988) SELECT

9027 postgres  20   0 3514872 265384 189656 R  20.2  1.6   5:21.63 postgres: 
engine engine 127.0.0.1(43012) SELECT

17546 postgres  20   0 3475628  55248  19108 R  20.2  0.3   1:33.40 postgres: 
engine engine 127.0.0.1(35668) SELECT

17669 postgres  20   0 3483284  66920  22488 R  20.2  0.4   1:28.01 postgres: 
engine engine 127.0.0.1(35898) SELECT

17670 postgres  20   0 3504988  78300  22032 R  20.2  0.5   1:18.96 postgres: 
engine engine 127.0.0.1(35900) SELECT

17865 postgres  20   0 3485084  66688  21316 R  20.2  0.4   1:14.00 postgres: 
engine engine 127.0.0.1(36306) SELECT

7869 postgres  20   0 3492780 224272 171620 R  19.9  1.4   2:57.03 postgres: 
engine engine 127.0.0.1(46542) SELECT



Thx Christian







Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Grundmann, Christian
Gesendet: Donnerstag, 29. September 2016 15:29
An: 'users@ovirt.org' <users@ovirt.org>
Betreff: [ovirt-users] WG: High Database Load after updating to oV

Re: [ovirt-users] Max number of api calls per user?

2017-01-11 Thread Grundmann, Christian
200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:30 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:31 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:31 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:32 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:32 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 990370
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:33 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:33 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:34 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:35 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 401 155
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:35 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:36 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:37 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:37 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:37 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:37 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:38 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:38 +0100] "GET
/ovirt-engine/api/vms;case_sensitive=True HTTP/1.1" 200 1012092
2001:67c:1933:c01:faba:c0de:ba5e:4522 - - [11/Jan/2017:14:57:39 +0100] "GET
/ovirt-engine/api HTTP/1.1" 200 4395



Thx Christian

-Ursprüngliche Nachricht-
Von: Juan Hernández [mailto:jhern...@redhat.com] 
Gesendet: Mittwoch, 11. Jänner 2017 15:26
An: Grundmann, Christian <christian.grundm...@fabasoft.com>;
'users@ovirt.org' <users@ovirt.org>
Betreff: Re: [ovirt-users] Max number of api calls per user?

On 01/11/2017 03:16 PM, Grundmann, Christian wrote:
> Hi,
> 
> is there a maximum number of sessions per user?
> 

There is no limit, except the available memory.

>  
> 
> I am doing python-api calls to remove VMs
> 
> If I call my script 30 times simultaneously, one or two get an error.
>

What does 'simultaneously' mean exactly? Are you sending the requests in
parallel from different threads? Or from different processes? Or just
sending them in a loop?

The /var/log/ovirt-engine/server.log, /var/log/ovirt-engine/engine.log and
/var/log/httpd/ssl_access_log files can help determine what is happening.
Can you check and maybe share the relevant part of those files?

>  
> 
> Traceback (most recent call last):
> 
>   File "remove_vm.py", line 24, in 
> 
> if VMNAME in [vm.name for vm in api.vms.list()]:
> 
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
> line 35761, in list
> 
> headers={"All-Content":all_content}
> 
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
> line 46, in get
> 
> return self.request(method='GET', url=url, headers=headers, 
> cls=cls)
> 
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
> line 122, in request
> 
> persistent_auth=self.__persistent_auth
> 
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionsp
> ool.py",
> line 79, in do_request
> 
> persistent_auth)
> 
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionsp
> ool.py",
> line 162, in __do_request
> 
> raise errors.RequestError(response_code, response_reason, 
> response_body)
> 
> ovirtsdk.infrastructure.errors.RequestError:
> 
> status: 401
> 
> reason: Unauthorized
> 
> detail: User is not logged in.
> 
>  
> 
>  
> 
> Is there some setting I can tune?
> 
>  
> 
> Thx Christian
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Max number of api calls per user?

2017-01-11 Thread Grundmann, Christian
Hi,

is there a maximum number of sessions per user?

 

I am doing python-api calls to remove VMs

If I call my script 30 times simultaneously, one or two get an error.

 

Traceback (most recent call last):
  File "remove_vm.py", line 24, in 
if VMNAME in [vm.name for vm in api.vms.list()]:
  File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line
35761, in list
headers={"All-Content":all_content}
  File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 46, in get
return self.request(method='GET', url=url, headers=headers, cls=cls)
  File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 122, in request
persistent_auth=self.__persistent_auth
  File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py
", line 79, in do_request
persistent_auth)
  File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py
", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
ovirtsdk.infrastructure.errors.RequestError: 
status: 401
reason: Unauthorized
detail: User is not logged in.

 

 

Is there some setting I can tune?

 

Thx Christian



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [ANN] oVirt 4.0.6 Release is now available

2017-01-11 Thread Grundmann, Christian
Hi,
Release Nodes showing “BZ 1374988 MOM 
causes Vdsm to slow down, high number of 'vmGetIoTunePolicy' API calls – vdsm “
Bugzilla shows “Target Release:   4.18.16”

yum update ovirt-node-ng-image gave me ovirt-node-ng-image-4.0.6-1.el7
which installs vdsm-4.18.15.3-1

Is it fixed or not?


Thx Christian




Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Sandro Bonazzola
Gesendet: Dienstag, 10. Jänner 2017 13:35
An: annou...@ovirt.org; users 
Betreff: [ovirt-users] [ANN] oVirt 4.0.6 Release is now available

The oVirt Project is pleased to announce the general availability of oVirt 
4.0.6, as of January 10th, 2016.

This release is available now for:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 23 (tech preview)

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0


This update is the sixth in a series of stabilization updates to the 4.0 series.
4.0.6 brings 4 enhancements and 59 bugfixes, including 24 high or urgent
severity fixes, on top of oVirt 4.0 series
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is already available. [2]
* A new oVirt Next Generation Node will be available soon [2]
* A new oVirt Engine Appliance is already available for Red Hat Enterprise 
Linux and CentOS Linux (or similar)
* Mirrors[3] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.6 release 
highlights:http://www.ovirt.org/release/4.0.6/
* 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.0.6/
[2] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
[3] http://www.ovirt.org/Repository_mirrors#Current_mirrors

--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Windows Server Container Support

2016-11-17 Thread Grundmann, Christian
Hi,
@ Probably because containers in Windows actually run inside VMs, therefore 
using nested Virtualization.
that’s not true anymore for Server 2016,
they have “real“ container Support now



Von: Yaniv Kaul [mailto:yk...@redhat.com]
Gesendet: Mittwoch, 16. November 2016 23:13
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: Gal Hammer <gham...@redhat.com>; Dan Kenigsberg <dan...@redhat.com>; 
users@ovirt.org
Betreff: Re: [ovirt-users] Windows Server Container Support


On Nov 16, 2016 7:54 PM, "Grundmann, Christian" 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
>
> Hi,
> i tried a few vnic configurations,
> looks like it works with e1000
> but with virtio i have the problem
>
> @ How did the VM die? Is there an error message in /var/log/vdsm/vdsm.log, or 
> /var/log/libvirt/qemu/*
> The VM dies at OS Level, it boots but most oft he services are not starting, 
> so no network and many other things not working

Probably because containers in Windows actually run inside VMs, therefore using 
nested Virtualization.
Y.

>
>
>
> -Ursprüngliche Nachricht-
> Von: Dan Kenigsberg [mailto:dan...@redhat.com<mailto:dan...@redhat.com>]
> Gesendet: Mittwoch, 16. November 2016 17:48
> An: Grundmann, Christian 
> <christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>>
> Cc: users@ovirt.org<mailto:users@ovirt.org>; 
> gham...@redhat.com<mailto:gham...@redhat.com>
> Betreff: Re: [ovirt-users] Windows Server Container Support
>
> On Wed, Nov 16, 2016 at 12:28:30PM +, Grundmann, Christian wrote:
> > Hi,
> > I tried installing Windows Server 2016 and enabling Container Support
> > and Docker But after enabling Docker, the VM dies.
> > All Network related services are timeouting when booting the Server.
> > If I unplug the NIC the VMs starts normally and Docker works
> >
> > I tried to enable the macspoof vdsm hook but it doesn't help
> >
> > Anything else I can try?
> >
> > Thx Christian
>
> Could you give more details?
>
> How did the VM die? Is there an error message in /var/log/vdsm/vdsm.log, or 
> /var/log/libvirt/qemu/*
>
> How was the VM defined? Which type was the vNIC?
> ___
> Users mailing list
> Users@ovirt.org<mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Windows Server Container Support

2016-11-16 Thread Grundmann, Christian
Hi,
i tried a few vnic configurations,
looks like it works with e1000 
but with virtio i have the problem

@ How did the VM die? Is there an error message in /var/log/vdsm/vdsm.log, or 
/var/log/libvirt/qemu/*
The VM dies at OS Level, it boots but most oft he services are not starting, so 
no network and many other things not working



-Ursprüngliche Nachricht-
Von: Dan Kenigsberg [mailto:dan...@redhat.com] 
Gesendet: Mittwoch, 16. November 2016 17:48
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org; gham...@redhat.com
Betreff: Re: [ovirt-users] Windows Server Container Support

On Wed, Nov 16, 2016 at 12:28:30PM +, Grundmann, Christian wrote:
> Hi,
> I tried installing Windows Server 2016 and enabling Container Support 
> and Docker But after enabling Docker, the VM dies.
> All Network related services are timeouting when booting the Server.
> If I unplug the NIC the VMs starts normally and Docker works
> 
> I tried to enable the macspoof vdsm hook but it doesn't help
> 
> Anything else I can try?
> 
> Thx Christian

Could you give more details?

How did the VM die? Is there an error message in /var/log/vdsm/vdsm.log, or 
/var/log/libvirt/qemu/*

How was the VM defined? Which type was the vNIC?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Windows Server Container Support

2016-11-16 Thread Grundmann, Christian
Hi,
I tried installing Windows Server 2016 and enabling Container Support and Docker
But after enabling Docker, the VM dies.
All Network related services are timeouting when booting the Server.
If I unplug the NIC the VMs starts normally and Docker works

I tried to enable the macspoof vdsm hook but it doesn't help

Anything else I can try?

Thx Christian


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] WG: High Database Load after updating to oVirt 4.0.4

2016-09-29 Thread Grundmann, Christian
Maybe an side effect off this bug?

https://bugzilla.redhat.com/1302752

I did a restore to 4.0.3 and the timeouts are gone

Von: Grundmann, Christian
Gesendet: Dienstag, 27. September 2016 10:33
An: users@ovirt.org
Betreff: High Database Load after updating to oVirt 4.0.4

After 4.0.4 Update we have a very high database load during startup of VMs
So high that the api calls getting timeouts

I attached the output of
select * from pg_stat_activity


is there a way to downgrade to 4.0.3?

Thx Christian



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] High Database Load after updating to oVirt 4.0.4

2016-09-27 Thread Grundmann, Christian
After 4.0.4 Update we have a very high database load during startup of VMs
So high that the api calls getting timeouts

I attached the output of
select * from pg_stat_activity


is there a way to downgrade to 4.0.3?

Thx Christian





queries.csv
Description: queries.csv
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

2016-08-31 Thread Grundmann, Christian
node not updated:
rpm -qa | grep placeholder
ovirt-node-ng-image-update-placeholder-4.0.1-1.el7.noarch
yum info ovirt-node-ng-image-update
Warning: yum operations are not persisted across upgrades!
Loading mirror speeds from cached hostfile
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
Available Packages
Name: ovirt-node-ng-image-update
Arch: noarch
Version : 4.0.3
Release : 1.el7
Size: 3.1 k
Repo: ovirt-4.0/7
Summary : oVirt Node Next Image Update
URL : http://www.ovirt.org/node/
License : GPLv2
Description : This package will update an oVirt Node Next host with the new
: image.
node updated:
rpm -qa | grep placeholder
ovirt-node-ng-image-update-placeholder-4.0.1-1.el7.noarch

yum info ovirt-node-ng-image-update

Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Repository ovirt-4.0-epel is listed more than once in the configuration
Repository ovirt-4.0-centos-gluster37 is listed more than once in the 
configuration
Repository ovirt-4.0-patternfly1-noarch-epel is listed more than once in the 
configuration
Repository virtio-win-stable is listed more than once in the configuration
Repository ovirt-4.0 is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* ovirt-4.0-epel: epel.besthosting.ua
Error: No matching Packages to list



Von: Fabian Deutsch [mailto:fdeut...@redhat.com]
Gesendet: Mittwoch, 31. August 2016 16:18
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: Sandro Bonazzola <sbona...@redhat.com>; users <users@ovirt.org>
Betreff: Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

What do you get for
$ rpm -qa | grep placeholder
$ yum info ovirt-node-ng-image-update

- fabian


On Wed, Aug 31, 2016 at 12:18 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,

node not updated:
rpm -qa |grep ovirt-release
ovirt-release40-4.0.2-2.noarch
ovirt-release-host-node-4.0.2-2.el7.noarch

grep -ri enabled /etc/yum.repos.d/ovirt-4.0*
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0.repo:enabled=1


yum check-update
Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Loading mirror speeds from cached hostfile
* ovirt-4.0: ftp.nluug.nl<http://ftp.nluug.nl>
* ovirt-4.0-epel: epel.besthosting.ua<http://epel.besthosting.ua>
Obsoleting Packages
ovirt-node-ng-image-update.noarch 4.0.3-1.el7  ovirt-4.0
ovirt-node-ng-image-update-placeholder.noarch 4.0.1-1.el7  installed


node updated over engine:
rpm -qa |grep ovirt-release
ovirt-release40-pre-4.0.1-1.noarch
ovirt-release-host-node-4.0.1-1.el7.noarch

  grep -ri enabled /etc/yum.repos.d/ovirt-4.0*
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-pre.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0.repo:enabled=1


yum check-update
Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Repository ovirt-4.0-epel is listed more than once in the configuration
Repository ovirt-4.0-centos-gluster37 is listed more than once in the 
configuration
Repository ovirt-4.0-patternfly1-noarch-epel is listed more than once in the 
configuration
Repository virtio-win-stable is listed more than once in the configuration
Repository ovirt-4.0 is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* ovirt-4.0-epel: epel.besthosting.ua<http://epel.besthosting.ua>



How can I fix it without reinstalling all my nodes?

Thx Christian

Von: Fabian Deutsch [mailto:fdeut...@redhat.com<mailto:fdeut...@red

Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

2016-08-31 Thread Grundmann, Christian
Hi,

node not updated:
rpm -qa |grep ovirt-release
ovirt-release40-4.0.2-2.noarch
ovirt-release-host-node-4.0.2-2.el7.noarch

grep -ri enabled /etc/yum.repos.d/ovirt-4.0*
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0.repo:enabled=1


yum check-update
Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Loading mirror speeds from cached hostfile
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
Obsoleting Packages
ovirt-node-ng-image-update.noarch 4.0.3-1.el7  ovirt-4.0
ovirt-node-ng-image-update-placeholder.noarch 4.0.1-1.el7  installed


node updated over engine:
rpm -qa |grep ovirt-release
ovirt-release40-pre-4.0.1-1.noarch
ovirt-release-host-node-4.0.1-1.el7.noarch

  grep -ri enabled /etc/yum.repos.d/ovirt-4.0*
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-dependencies.repo:enabled=1
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre-dependencies.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0-pre.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0-pre.repo:enabled=0
/etc/yum.repos.d/ovirt-4.0.repo:# imgbased: set-enabled
/etc/yum.repos.d/ovirt-4.0.repo:enabled=1


yum check-update
Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Repository ovirt-4.0-epel is listed more than once in the configuration
Repository ovirt-4.0-centos-gluster37 is listed more than once in the 
configuration
Repository ovirt-4.0-patternfly1-noarch-epel is listed more than once in the 
configuration
Repository virtio-win-stable is listed more than once in the configuration
Repository ovirt-4.0 is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* ovirt-4.0-epel: epel.besthosting.ua



How can I fix it without reinstalling all my nodes?

Thx Christian

Von: Fabian Deutsch [mailto:fdeut...@redhat.com]
Gesendet: Mittwoch, 31. August 2016 12:08
An: Sandro Bonazzola <sbona...@redhat.com>
Cc: Grundmann, Christian <christian.grundm...@fabasoft.com>; users 
<users@ovirt.org>
Betreff: Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

On Wed, Aug 31, 2016 at 11:26 AM, Fabian Deutsch 
<fdeut...@redhat.com<mailto:fdeut...@redhat.com>> wrote:
On Wed, Aug 31, 2016 at 11:23 AM, Sandro Bonazzola 
<sbona...@redhat.com<mailto:sbona...@redhat.com>> wrote:


On Wed, Aug 31, 2016 at 10:15 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,
I used the iso "ovirt-node-ng-installer-ovirt-4.0-2016082904.iso" from 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64/
I attached the nodes in my Engine (4.0.3)
Engine shows, oVirt Node 4.0.2
After a few minutes Engine tells me there is a update for the node
I did the update
And now the Node is  4.0.1!

How can I get the right updates?

Fabian, how can this happen?

Btw, 4.0.3 iso has been published yesterday: 
http://resources.ovirt.org/pub/ovirt-4.0/iso/ovirt-node-ng-installer/ovirt-node-ng-installer-ovirt-4.0-2016083011.iso


Hey Christian and Sandro,
thanks for reporting this.
I'm looking into it.

So - We did have some problems until Monday where the versions were mixde up 
between ovirt-4.0, -pre and -snapshot.
I suppose that this caused the glithc you were seeing, Christian.
I've downloaded
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/ovirt-node-ng-installer-ovirt-4.0-2016083104.iso
and could not reproduce this issue.
- fabian



- fabian




Thx Christian



-Ursprüngliche Nachricht-
Von: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> 
[mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] Im Auftrag von 
Fabian Deutsch
Gesendet: Montag, 29. August 2016 10:52
An: Thomas Klute <kl...@ingenit.com<mailto:kl...@ingenit.com>>
Cc: users <user

Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

2016-08-31 Thread Grundmann, Christian
Hi,
I used the iso "ovirt-node-ng-installer-ovirt-4.0-2016082904.iso" from 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64/
I attached the nodes in my Engine (4.0.3)
Engine shows, oVirt Node 4.0.2
After a few minutes Engine tells me there is a update for the node
I did the update
And now the Node is  4.0.1!

How can I get the right updates?


Thx Christian



-Ursprüngliche Nachricht-
Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Fabian Deutsch
Gesendet: Montag, 29. August 2016 10:52
An: Thomas Klute 
Cc: users 
Betreff: Re: [ovirt-users] Stable Next Generation Node Image for 4.0.2?

On Wed, Aug 24, 2016 at 2:09 PM, Thomas Klute  wrote:
> Dear oVirt community,
>
> what is the correct way to set up a next generation node of the latest 
> stable version (4.0.2)?

Hey Thomas,

let me get back to this question at the end …

> Take the image from
> http://resources.ovirt.org/pub/ovirt-4.0/iso/ovirt-node-ng-installer/ ?
> Seems to be 4.0.0 and then update?

This is the URL yuo want - It contains the builds based on the latest stable 
release.

Tho I see that it wasn't updated lately.
Sandro, can we publish a new ISO for 4.0.3?

In the mean time you can take the iso from 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64/
Which is building the stable isos

> Or take the image from
> http://resources.ovirt.org/pub/ovirt-4.0-snapshot/iso/
> Seems to be 4.0.2 but nightly and thus unstable?

Yep, these are nightly builds, and probably unstable.

- fabian

> Thanks for the clarification,
> best regards,
>  Thomas
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Failed to execute stage 'Setup validation': Setup found legacy kerberos/ldap directory integration in use

2016-08-30 Thread Grundmann, Christian
Hi,
yes there were domains configured (which i used for sysprep but not for login)
I removed it and did a new backup /restore and now it worked,
Would be nice to have these step included in the migration guide?

Thx Christian

Von: Simone Tiraboschi [mailto:stira...@redhat.com]
Gesendet: Dienstag, 30. August 2016 09:42
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Failed to execute stage 'Setup validation': Setup 
found legacy kerberos/ldap directory integration in use


On Tue, Aug 30, 2016 at 9:09 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com<mailto:christian.grundm...@fabasoft.com>> 
wrote:
Hi,
I tried migrating oVirt Engine 3.6 (FC22) to Engine 4.0 (CentOS 7) using the 
guide https://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/

But it fails with

[ ERROR ] Failed to execute stage 'Setup validation': Setup found legacy 
kerberos/ldap directory integration in use (added by engine-manage-domains). 
This provider is no longer supported, please migrate to 
ovirt-engine-extension-aaa-ldap provider or contact support for assistance.

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
_executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaakerbldap.py",
 line 72, in _validation_late
'Setup found legacy kerberos/ldap directory '
RuntimeError: Setup found legacy kerberos/ldap directory integration in use 
(added by engine-manage-domains). This provider is no longer supported, please 
migrate to ovirt-engine-extension-aaa-ldap provider or contact support for 
assistance.
2016-08-30 09:01:58 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Setup validation': Setup found legacy kerberos/ldap directory 
integration in use (added by engine-manage-domains). This provider is no longer 
supported, please migrate to ovirt-engine-extension-aaa-ldap provider or 
contact support for assistance.
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT 
DUMP - BEGIN
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/error=bool:'True'
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/exceptionInfo=list:'[(, 
RuntimeError('Setup found legacy kerberos/ldap directory integration in use 
(added by engine-manage-domains). This provider is no longer supported, please 
migrate to ovirt-engine-extension-aaa-ldap provider or contact support for 
assistance.',), )]'


Hi Christian,
can you please execute
   engine-manage-domains list
on your oVirt Engine 3.6 (FC22) system to see what it founds there?


I never configured ldap or Kerberos

Please help
Thx
Christian

___
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Failed to execute stage 'Setup validation': Setup found legacy kerberos/ldap directory integration in use

2016-08-30 Thread Grundmann, Christian
Hi,
I tried migrating oVirt Engine 3.6 (FC22) to Engine 4.0 (CentOS 7) using the 
guide https://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/

But it fails with

[ ERROR ] Failed to execute stage 'Setup validation': Setup found legacy 
kerberos/ldap directory integration in use (added by engine-manage-domains). 
This provider is no longer supported, please migrate to 
ovirt-engine-extension-aaa-ldap provider or contact support for assistance.

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
_executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaakerbldap.py",
 line 72, in _validation_late
'Setup found legacy kerberos/ldap directory '
RuntimeError: Setup found legacy kerberos/ldap directory integration in use 
(added by engine-manage-domains). This provider is no longer supported, please 
migrate to ovirt-engine-extension-aaa-ldap provider or contact support for 
assistance.
2016-08-30 09:01:58 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Setup validation': Setup found legacy kerberos/ldap directory 
integration in use (added by engine-manage-domains). This provider is no longer 
supported, please migrate to ovirt-engine-extension-aaa-ldap provider or 
contact support for assistance.
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT 
DUMP - BEGIN
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/error=bool:'True'
2016-08-30 09:01:58 DEBUG otopi.context context.dumpEnvironment:770 ENV 
BASE/exceptionInfo=list:'[(, 
RuntimeError('Setup found legacy kerberos/ldap directory integration in use 
(added by engine-manage-domains). This provider is no longer supported, please 
migrate to ovirt-engine-extension-aaa-ldap provider or contact support for 
assistance.',), )]'


I never configured ldap or Kerberos

Please help
Thx
Christian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Problems installing Ovirt 4.02 Node

2016-08-04 Thread Grundmann, Christian
Hi,
I installed ovirt-node-ng-installer-ovirt-4.0-2016080104.iso
with default partitioning Layout
with the result after Installation:

Status: FAILED
Mount points ... FAILED - This can happen if the installation was performed 
incorrectly
  Separate /var ... FAILED - /var got unmounted, or was not setup to use a 
separate volume
  Discard is used ... FAILED - 'discard' mount option was not added or got 
removed
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK

No LV for /var created at all.

What’s the right way installing an working node?

Thx a lot
Christian


Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Fabian Deutsch
Gesendet: Mittwoch, 27. Juli 2016 13:25
An: Peter Michael Calum 
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Problems installing Ovirt 4.02 Node



On Wed, Jul 27, 2016 at 7:59 AM, Peter Michael Calum 
> wrote:
Hi,

I tried the changes in /etc/fstab and rebooted.
Now  imgbase status: OK

But I see this in /var/log/messages after the change :  Starting kdump: [FAILED]

Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: base ***
Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: fs-lib ***
Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: kdumpbase ***
Jul 27 07:44:08 khk9dsk34 kernel: device-mapper: table: 253:8: multipath: error 
getting device
Jul 27 07:44:08 khk9dsk34 kernel: device-mapper: ioctl: error adding target to 
table
Jul 27 07:44:08 khk9dsk34 multipathd: dm-8: remove map (uevent)
Jul 27 07:44:08 khk9dsk34 multipathd: dm-8: remove map (uevent)

Jul 27 07:44:08 khk9dsk34 kdumpctl: Bad kdump location: 
khk9dsg34.ip.tdk.dk
Jul 27 07:44:09 khk9dsk34 kdumpctl: mkdumprd: failed to make kdump initrd
Jul 27 07:44:09 khk9dsk34 kdumpctl: Starting kdump: [FAILED]
Jul 27 07:44:09 khk9dsk34 systemd: kdump.service: main process exited, 
code=exited, status=1/FAILURE
Jul 27 07:44:09 khk9dsk34 systemd: Failed to start Crash recovery kernel arming.

Jul 27 07:44:09 khk9dsk34 systemd: Startup finished in 5.673s (kernel) + 8.024s 
(initrd) + 43.476s (userspace) = 57.173s.
Jul 27 07:44:09 khk9dsk34 systemd: Unit kdump.service entered failed state.
Jul 27 07:44:09 khk9dsk34 systemd: kdump.service failed.
Jul 27 07:44:32 khk9dsk34 systemd: Starting Stop Read-Ahead Data Collection...
Jul 27 07:44:32 khk9dsk34 systemd: Started Stop Read-Ahead Data Collection.
Jul 27 07:44:32 khk9dsk34 systemd-logind: New session 1 of user root.
Jul 27 07:44:32 khk9dsk34 systemd: Created slice user-0.slice.
Jul 27 07:44:32 khk9dsk34 systemd: Starting user-0.slice.
Jul 27 07:44:32 khk9dsk34 systemd: Started Session 1 of user root.
Jul 27 07:44:32 khk9dsk34 systemd: Starting Session 1 of user root.
Jul 27 07:44:45 khk9dsk34 kernel: device-mapper: table: 253:8: multipath: error 
getting device
Jul 27 07:44:45 khk9dsk34 kernel: device-mapper: ioctl: error adding target to 
table
Jul 27 07:44:45 khk9dsk34 multipathd: dm-8: remove map (uevent)
Jul 27 07:44:45 khk9dsk34 multipathd: dm-8: remove map (uevent)

I checked messages in my other hypervisor where /etc/fstab was not modified, 
KDUMP was OK there.

The question about registrating the host in the manager i got solved, it is now 
done from the manager.
(I come from the Redhat 3.5, and are just started on Ovirt 4)

Nice that the status issue could be solved.
For adding Node, you can either add the host by gpoing to Engine and then add 
the host, or you can use vdsm register on the host to register it to Engine.
- fabian

Thanks for helping
Peter

-Oprindelig meddelelse-
Fra: Giorgio Biacchi [mailto:gior...@di.unimi.it]
Sendt: 27. juli 2016 00:05
Til: Peter Michael Calum >; 
users@ovirt.org
Emne: Re: [ovirt-users] Problems installing Ovirt 4.02 Node

On 26/07/2016 08:51, Peter Michael Calum wrote:

>   imgbase status: DEGRADED
>
>   Please check the status manually using `imgbase check`

Got the same problem, add discard option to fstab for / and /var like this:

#
# /etc/fstab
# Created by anaconda on Fri Jul 22 11:08:40 2016 # # Accessible filesystems, 
by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info #
/dev/HostVG/ovirt-node-ng-4.0.2-0.20160721.0+1 / ext4 defaults,discard 1 1
UUID=a96d5a4c-bc4b-481c-bf6e-af47318d8b7b /boot   ext4
  defaults1 2
/dev/mapper/HostVG-var  /varext4defaults,discard 1 2
/dev/mapper/HostVG-swap swapswapdefaults0 0

then remount or reboot.

>
> Another question : Where do I define the Ovirt manager address.

For this one I can't help, but you can add the new host from the manager..

>
>
>
> Venlig hilsen / Kind regards
>
> 

Re: [ovirt-users] volume_utilization_chunk_mb not working

2016-05-13 Thread Grundmann, Christian
Hi,
it works now,

Thx a lot

-Ursprüngliche Nachricht-
Von: Nir Soffer [mailto:nsof...@redhat.com] 
Gesendet: Freitag, 13. Mai 2016 14:00
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working

On Fri, May 13, 2016 at 2:53 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com> wrote:
> Oh, i see
>
> Is there a way to reload the config without going to maintenance mode?

You can restart the service.

On the spm this will abort operations like copying disks and like, this is safe.

Nir

>
> Thx
> Christian
>
> -Ursprüngliche Nachricht-
> Von: Nir Soffer [mailto:nsof...@redhat.com]
> Gesendet: Freitag, 13. Mai 2016 13:52
> An: Grundmann, Christian <christian.grundm...@fabasoft.com>
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working
>
> On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian 
> <christian.grundm...@fabasoft.com> wrote:
>> Hi,
>> @ This looks correct if this is in the [irs] section of the configuration.
>> It is
>>
>> cat /etc/vdsm/vdsm.conf
>> [vars]
>> ssl = true
>>
>> [addresses]
>> management_port = 54321
>>
>> [irs ]
>
> This is the "irs " section, not the "irs" section :-)
>
>> volume_utilization_percent=15
>> volume_utilization_chunk_mb=4048
>>
>> do I need a space before and after the = ?
>
> No, it is just more human friendly this way.
>
>> @ We support initialSize argument when creating volumes - use when importing 
>> external vms (v2v), but it is not exposed in the ui.
>> If you think think exposing it in the ui is a useful feature, you can file a 
>> bug:
>> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>>
>> I don't need it in the ui, but it would be nice to have it as 
>> tuneable
>
> I checked the code, and we actually do use volume_utilization_chunk_mb when 
> we create the initial disk, so getting the configuration to work will solve 
> your issue.
>
> Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] volume_utilization_chunk_mb not working

2016-05-13 Thread Grundmann, Christian
Oh, i see

Is there a way to reload the config without going to maintenance mode?

Thx
Christian

-Ursprüngliche Nachricht-
Von: Nir Soffer [mailto:nsof...@redhat.com] 
Gesendet: Freitag, 13. Mai 2016 13:52
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working

On Fri, May 13, 2016 at 2:32 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com> wrote:
> Hi,
> @ This looks correct if this is in the [irs] section of the configuration.
> It is
>
> cat /etc/vdsm/vdsm.conf
> [vars]
> ssl = true
>
> [addresses]
> management_port = 54321
>
> [irs ]

This is the "irs " section, not the "irs" section :-)

> volume_utilization_percent=15
> volume_utilization_chunk_mb=4048
>
> do I need a space before and after the = ?

No, it is just more human friendly this way.

> @ We support initialSize argument when creating volumes - use when importing 
> external vms (v2v), but it is not exposed in the ui.
> If you think think exposing it in the ui is a useful feature, you can file a 
> bug:
> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> I don't need it in the ui, but it would be nice to have it as tuneable

I checked the code, and we actually do use volume_utilization_chunk_mb when we 
create the initial disk, so getting the configuration to work will solve your 
issue.

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] volume_utilization_chunk_mb not working

2016-05-13 Thread Grundmann, Christian
Hi,
@ This looks correct if this is in the [irs] section of the configuration.
It is 

cat /etc/vdsm/vdsm.conf
[vars]
ssl = true

[addresses]
management_port = 54321

[irs ]
volume_utilization_percent=15
volume_utilization_chunk_mb=4048

do I need a space before and after the = ?

@ We support initialSize argument when creating volumes - use when importing 
external vms (v2v), but it is not exposed in the ui.
If you think think exposing it in the ui is a useful feature, you can file a 
bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

I don't need it in the ui, but it would be nice to have it as tuneable


Thx 
Christian

-Ursprüngliche Nachricht-
Von: Nir Soffer [mailto:nsof...@redhat.com] 
Gesendet: Freitag, 13. Mai 2016 13:24
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] volume_utilization_chunk_mb not working

On Fri, May 13, 2016 at 1:34 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com> wrote:
> Hi
>
> I create a lot of Thin Disk VMs from templates every day, and get 
> „paused due to no storage space error“ and „paused due to unknown 
> storage error“ on a few of them.
>
> Sometimes the VMs are resumed a few seconds later but sometime not, 
> but I can resume them myself.
>
>
>
> I tried to set
>
> volume_utilization_percent=15
>
> volume_utilization_chunk_mb=4048

This looks correct if this is in the [irs] section of the configuration.

[irs]

# Together with volume_utilization_chunk_mb, set the minimal free # space 
before a thin provisioned block volume is extended. Use lower # values to 
extend earlier.
# volume_utilization_percent = 50

# Size of extension chunk in megabytes, and together with # 
volume_utilization_percent, set the free space limit. Use higher # values to 
extend in bigger chunks.
# volume_utilization_chunk_mb = 1024


To get the correct configuration format, you can do:
python /usr/lib/python2.7/site-packages/vdsm/config.py

>
>
>
> in /etc/vdsm/vdsm.conf on every Host
>
>
>
> But the Initial Size of the Disk is always 1GB and then increments to 
> 2GB

Please share the vdsm.conf file with these settings.

>
>
>
> 4GB would be the maximum Size I need before I destroy the VM. So if 
> the initial Size would be 4GB the pausing shouldn’t happen anymore

The initial volume size is always 1GiB, regardless of these settings.

After creating 1GiB lv, we extend the lv volume_utilization_chunk_mb megabytes.

So your setting will result in 1GiB lv, and after you write about 150MiB, it 
will be extended to 5GiB.

So I guess that you want to use
volume_utilization_chunk_mb = 3072

Which will give you 4GiB lv after the first extend.

We support initialSize argument when creating volumes - use when importing 
external vms (v2v), but it is not exposed in the ui.

If you think think exposing it in the ui is a useful feature, you can file a 
bug:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

Nir
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] volume_utilization_chunk_mb not working

2016-05-13 Thread Grundmann, Christian
Hi
I create a lot of Thin Disk VMs from templates every day, and get "paused due 
to no storage space error" and "paused due to unknown storage error" on a few 
of them.
Sometimes the VMs are resumed a few seconds later but sometime not, but I can 
resume them myself.

I tried to set
volume_utilization_percent=15
volume_utilization_chunk_mb=4048

in /etc/vdsm/vdsm.conf on every Host

But the Initial Size of the Disk is always 1GB and then increments to 2GB

4GB would be the maximum Size I need before I destroy the VM. So if the initial 
Size would be 4GB the pausing shouldn't happen anymore

Thx a lot for your help
Christian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Webadmin - disable idle logout

2016-05-10 Thread Grundmann, Christian
Hi,
is there a way to disable the idle logout in webadmin?

Thx a lot
Christian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Reclaim disk space of thin disks

2016-03-31 Thread Grundmann, Christian
Hi,

@ I'm unsure if that size should change - we've allocated blocks, they are 
still allocated from our perspective. From the storage point of view, there's a 
hole that can be used for other purposes.

I'd look on the storage side. 

 

That’s the problem, if the space is still allocated it can’t be used for other 
VMs so it won’t help. Is there a possibility to deallocate the free Blocks of 
the Disk? I think virt-sparsify would do exactly that but can’t be used with 
ovirt?

 

Thx

Christian

 

 

 

 

 

Von: Yaniv Kaul [mailto:yk...@redhat.com] 
Gesendet: Donnerstag, 31. März 2016 14:33
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

On Thu, Mar 31, 2016 at 1:16 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

@1. Did you use the hook?

yes, without the hook fstrim would not start,

@2. Where did you see it's the same size? Should be looked at from the storage 
side (assuming, btw, it supports discard!)

I looked at the “actual Size” under Storage

 

I'm unsure if that size should change - we've allocated blocks, they are still 
allocated from our perspective. From the storage point of view, there's a hole 
that can be used for other purposes.

I'd look on the storage side. 

 

I don’t know how ovirt handles FC storage and if this will allow discard.

 

It doesn't really care - thee discard should be passed to the underlying 
storage. Most should support UNMAP these days. But you can easily check, I 
assume with a small test (use sg3_utils for example).

Y.

 

 

Thx 

Christian

 

 

Von: Yaniv Kaul [mailto:yk...@redhat.com <mailto:yk...@redhat.com> ] 
Gesendet: Donnerstag, 31. März 2016 12:13


An: Grundmann, Christian <christian.grundm...@fabasoft.com 
<mailto:christian.grundm...@fabasoft.com> >
Cc: users@ovirt.org <mailto:users@ovirt.org> 
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

 

 

On Thu, Mar 31, 2016 at 1:05 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

seems not to work with FC Storage,

 

I Zero filled the Disk with dd, removed the file and did a fstrim which told me 
it trimmed the right amount of space,

But the disk Image stays full size.

 

1. Did you use the hook?

2. Where did you see it's the same size? Should be looked at from the storage 
side (assuming, btw, it supports discard!)

Y.

 

 

Thx 

Christian

 

Von: Yaniv Kaul [mailto:yk...@redhat.com <mailto:yk...@redhat.com> ] 
Gesendet: Mittwoch, 30. März 2016 22:29
An: Grundmann, Christian <christian.grundm...@fabasoft.com 
<mailto:christian.grundm...@fabasoft.com> >
Cc: users@ovirt.org <mailto:users@ovirt.org> 
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

 

 

On Wed, Mar 30, 2016 at 10:04 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

is there a way to „shrink“ a thin disk image to reclaim deleted space like 
using virt-sparsify?

 

Yes, if the underlying file system supports it (NFS, for example, might need to 
be 4.2 and above).

 

Or can it be done by making a snapshot and clone the VM to a new one?

 

Another suggestion: use the VDSM hooks for discard ('diskunmap') and run 
'fstrim' from within the guest. 

Y.

 

 

Thanks a lot

Christian


___
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org> 
http://lists.ovirt.org/mailman/listinfo/users

 

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Reclaim disk space of thin disks

2016-03-31 Thread Grundmann, Christian
Hi,

@1. Did you use the hook?

yes, without the hook fstrim would not start,

@2. Where did you see it's the same size? Should be looked at from the storage 
side (assuming, btw, it supports discard!)

I looked at the “actual Size” under Storage

 

I don’t know how ovirt handles FC storage and if this will allow discard.

 

Thx 

Christian

 

 

Von: Yaniv Kaul [mailto:yk...@redhat.com] 
Gesendet: Donnerstag, 31. März 2016 12:13
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

 

 

On Thu, Mar 31, 2016 at 1:05 PM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

seems not to work with FC Storage,

 

I Zero filled the Disk with dd, removed the file and did a fstrim which told me 
it trimmed the right amount of space,

But the disk Image stays full size.

 

1. Did you use the hook?

2. Where did you see it's the same size? Should be looked at from the storage 
side (assuming, btw, it supports discard!)

Y.

 

 

Thx 

Christian

 

Von: Yaniv Kaul [mailto:yk...@redhat.com <mailto:yk...@redhat.com> ] 
Gesendet: Mittwoch, 30. März 2016 22:29
An: Grundmann, Christian <christian.grundm...@fabasoft.com 
<mailto:christian.grundm...@fabasoft.com> >
Cc: users@ovirt.org <mailto:users@ovirt.org> 
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

 

 

On Wed, Mar 30, 2016 at 10:04 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

is there a way to „shrink“ a thin disk image to reclaim deleted space like 
using virt-sparsify?

 

Yes, if the underlying file system supports it (NFS, for example, might need to 
be 4.2 and above).

 

Or can it be done by making a snapshot and clone the VM to a new one?

 

Another suggestion: use the VDSM hooks for discard ('diskunmap') and run 
'fstrim' from within the guest. 

Y.

 

 

Thanks a lot

Christian


___
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org> 
http://lists.ovirt.org/mailman/listinfo/users

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Reclaim disk space of thin disks

2016-03-31 Thread Grundmann, Christian
Hi,

seems not to work with FC Storage,

 

I Zero filled the Disk with dd, removed the file and did a fstrim which told me 
it trimmed the right amount of space,

But the disk Image stays full size.

 

Thx 

Christian

 

Von: Yaniv Kaul [mailto:yk...@redhat.com] 
Gesendet: Mittwoch, 30. März 2016 22:29
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Reclaim disk space of thin disks

 

 

 

On Wed, Mar 30, 2016 at 10:04 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com <mailto:christian.grundm...@fabasoft.com> > 
wrote:

Hi,

is there a way to „shrink“ a thin disk image to reclaim deleted space like 
using virt-sparsify?

 

Yes, if the underlying file system supports it (NFS, for example, might need to 
be 4.2 and above).

 

Or can it be done by making a snapshot and clone the VM to a new one?

 

Another suggestion: use the VDSM hooks for discard ('diskunmap') and run 
'fstrim' from within the guest. 

Y.

 

 

Thanks a lot

Christian


___
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org> 
http://lists.ovirt.org/mailman/listinfo/users

 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Reclaim disk space of thin disks

2016-03-30 Thread Grundmann, Christian
Hi,

is there a way to "shrink" a thin disk image to reclaim deleted space like
using virt-sparsify?

Or can it be done by making a snapshot and clone the VM to a new one?

 

Thanks a lot

Christian



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] New oVirt Node releases?

2015-12-23 Thread Grundmann, Christian
Hi,
then I think release nodes have to be adjusted too.
http://www.ovirt.org/OVirt_3.6_Release_Notes


---
oVirt Node 

An oVirt Node build will be also available soon in: 
http://resources.ovirt.org/pub/ovirt-3.6/iso

Pre-release version is still available here: 
http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node/
---



With one Link without an iso and one with an 404


Greetings 
Christian


-Ursprüngliche Nachricht-
Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Fabian Deutsch
Gesendet: Dienstag, 22. Dezember 2015 09:52
An: Kevin Hung 
Cc: users 
Betreff: Re: [ovirt-users] New oVirt Node releases?

On Mon, Dec 21, 2015 at 6:18 PM, Kevin Hung  wrote:
> Hello,
>
> I have noticed that there have not been any official releases of oVirt 
> Node since 3.5.2 [1]. I have tried looking through the Users and the 
> Announce mailing lists for any information regarding the lack of 
> releases, but I was not able to find anything from the past few 
> months. The official documentation for oVirt seems to indicate that 
> oVirt Node is still supported.
>
> Are there just build problems preventing oVirt Node from being 
> released? Or are we supposed to use either the latest Jenkins build or 
> our own build [2] if we wish to deploy oVirt Node?

Hey Kevin.

In the last months we went over to only release oVirt Node through Jenkins [3].

The main reasons is that the Node team was focused on stabilizing Node, instead 
of improving the release process.

For the old isos in [1] - We should probably remove them and point to the 
continous builds.

I've also updated the links on the main Node landing page:
http://www.ovirt.org/Category:Node

Greetings
- fabian

[3] http://jenkins.ovirt.org/job/ovirt-node_ovirt-3.6_create-iso-el7_merged/

> [1] http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-node/el7-3.5.2/
> [2] http://www.ovirt.org/Node_Building
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Storage over allocation ratio value larger than 125% will pause vms

2015-12-07 Thread Grundmann, Christian
Hi,
I have the same problem with thin provisioned VMs (or VMs with snapshot)
It got a lot better (but not fixed) using this guide 
https://access.redhat.com/solutions/130843 to adjust the tunables

Maybe it helps
Christian

Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von 
Yaniv Kaul
Gesendet: Montag, 07. Dezember 2015 15:49
An: Jan Bernard Wevers 
Cc: users@ovirt.org
Betreff: Re: [ovirt-users] Storage over allocation ratio value larger than 125% 
will pause vms

On Mon, Dec 7, 2015 at 12:38 AM, Jan Bernard Wevers 
> 
wrote:
I’m using ovirt 3.6 and an iscsi storage domain. Almost all vms are using
thin provisioning with a virtual size of 40GB and a typical physical size of
8 GB.
Now I’m facing the fact that ovirt is pausing my vms due to the following
event message:
(Example):  “VM vm_01_16_centos6 has been paused due to no Storage space
error.”

oVirt is not pausing VMs. QEMU/KVM does, when it gets a storage error (in order 
to prevent possible corruption).
Can you please attach VDSM logs from the relevant host where this is happening?
TIA,
Y.


When I look at the iscsi storage domain the over allocation ratio value is
about 127%, but of the 2799GB there is still more than 1500GB available.
My questions:
- Why ovirt is pausing the vms?
- Can I enlarge the over allocation ratio before ovirt is complaining about
storage space?


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] engine-backup fails on FC22 ovirt 3.6

2015-11-16 Thread Grundmann, Christian
Hi,
since upgrade to 3.6 engine-backup fails with the Error

engine-backup --mode=backup --scope=all --file=ovirt-backup_3.6.backup 
--log=ovirt-backup_3.6.log
Backing up:
Notifying engine
- Files
tar: '--same-order' cannot be used with '-c'
Try 'tar --help' or 'tar --usage' for more information.
Notifying engine
FATAL: Failed backing up /etc/ovirt-engine
/etc/ovirt-engine-dwh
/etc/ovirt-engine-reports
/etc/pki/ovirt-engine
/etc/ovirt-engine-setup.conf.d
/var/lib/ovirt-engine-reports/build-conf
/var/lib/ovirt-engine-reports/ovirt-engine-reports.war/WEB-INF/js.quartz.properties
#/var/lib/ovirt-engine-reports
/etc/httpd/conf.d/ovirt-engine-root-redirect.conf
/etc/httpd/conf.d/ssl.conf
/etc/httpd/conf.d/z-ovirt-engine-proxy.conf
/etc/httpd/conf.d/z-ovirt-engine-reports-proxy.conf
/etc/yum/pluginconf.d/versionlock.list
/etc/dnf/plugins/versionlock.list
/etc/firewalld/services/ovirt-https.xml
/etc/firewalld/services/ovirt-http.xml
/etc/firewalld/services/ovirt-postgres.xml
/var/lib/ovirt-engine/content
/var/lib/ovirt-engine/engine.up
/var/lib/ovirt-engine/external_truststore
/var/lib/ovirt-engine/reports.xml
/var/lib/ovirt-engine/setup
/var/lib/ovirt-engine/setup-history.txt
/var/lib/ovirt-engine/timer-service-data
/var/lib/ovirt-engine/tx-object-store

tar version: tar-1.28-6.fc22.x86_64


Thx for your help
Christian

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] engine-backup fails on FC22 ovirt 3.6

2015-11-16 Thread Grundmann, Christian
Hi,
the Patch worked for me.
I created the Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1282397

Thx Christian


-Ursprüngliche Nachricht-
Von: Yedidyah Bar David [mailto:d...@redhat.com] 
Gesendet: Montag, 16. November 2015 10:59
An: Grundmann, Christian <christian.grundm...@fabasoft.com>
Cc: Users@ovirt.org
Betreff: Re: [ovirt-users] engine-backup fails on FC22 ovirt 3.6

On Mon, Nov 16, 2015 at 10:47 AM, Grundmann, Christian 
<christian.grundm...@fabasoft.com> wrote:
> Hi,
> since upgrade to 3.6 engine-backup fails with the Error
>
> engine-backup --mode=backup --scope=all --file=ovirt-backup_3.6.backup 
> --log=ovirt-backup_3.6.log Backing up:
> Notifying engine
> - Files
> tar: '--same-order' cannot be used with '-c'
> Try 'tar --help' or 'tar --usage' for more information.
> Notifying engine
> FATAL: Failed backing up /etc/ovirt-engine /etc/ovirt-engine-dwh 
> /etc/ovirt-engine-reports /etc/pki/ovirt-engine 
> /etc/ovirt-engine-setup.conf.d 
> /var/lib/ovirt-engine-reports/build-conf
> /var/lib/ovirt-engine-reports/ovirt-engine-reports.war/WEB-INF/js.quar
> tz.properties
> #/var/lib/ovirt-engine-reports
> /etc/httpd/conf.d/ovirt-engine-root-redirect.conf
> /etc/httpd/conf.d/ssl.conf
> /etc/httpd/conf.d/z-ovirt-engine-proxy.conf
> /etc/httpd/conf.d/z-ovirt-engine-reports-proxy.conf
> /etc/yum/pluginconf.d/versionlock.list
> /etc/dnf/plugins/versionlock.list
> /etc/firewalld/services/ovirt-https.xml
> /etc/firewalld/services/ovirt-http.xml
> /etc/firewalld/services/ovirt-postgres.xml
> /var/lib/ovirt-engine/content
> /var/lib/ovirt-engine/engine.up
> /var/lib/ovirt-engine/external_truststore
> /var/lib/ovirt-engine/reports.xml
> /var/lib/ovirt-engine/setup
> /var/lib/ovirt-engine/setup-history.txt
> /var/lib/ovirt-engine/timer-service-data
> /var/lib/ovirt-engine/tx-object-store
>
> tar version: tar-1.28-6.fc22.x86_64

Here [1] is a fix. Can you please verify? To get it fixed in 3.6.z, please also 
open a bug. Thanks!

[1] https://gerrit.ovirt.org/48596

Best,
--
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users