[ovirt-users] node ng upgrade failed

Mon Jul 10 12:10:51 UTC 2017

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    defaults        1 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 swap                    swap    defaults        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:rbarry at redhat.com]
Gesendet: Montag, 10. Juli 2017 14:09
An: Grundmann, Christian <Christian.Grundmann at fabasoft.com>
Cc: Yuval Turgeman <yuvalt at redhat.com>; users at 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.Grundmann at fabasoft.com<mailto:Christian.Grundmann at 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:rbarry at redhat.com<mailto:rbarry at redhat.com>]
Gesendet: Montag, 10. Juli 2017 13:39
An: Grundmann, Christian <Christian.Grundmann at fabasoft.com<mailto:Christian.Grundmann at fabasoft.com>>
Cc: Yuval Turgeman <yuvalt at redhat.com<mailto:yuvalt at redhat.com>>; users at ovirt.org<mailto:users at 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.Grundmann at fabasoft.com<mailto:Christian.Grundmann at fabasoft.com>> wrote:
attached

Von: Yuval Turgeman [mailto:yuvalt at redhat.com<mailto:yuvalt at redhat.com>]
Gesendet: Montag, 10. Juli 2017 13:10
An: Grundmann, Christian <Christian.Grundmann at fabasoft.com<mailto:Christian.Grundmann at fabasoft.com>>
Cc: users at ovirt.org<mailto:users at 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.Grundmann at fabasoft.com<mailto:Christian.Grundmann at 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: <LV 'onn_cs-kvm-001/ovirt-node-ng-4.1.3-0.20170709.0' />
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 <Base ovirt-node-ng-4.1.3-0.20170709.0 [] />
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,344 [INFO] Adding a new layer after <Base ovirt-node-ng-4.1.3-0.20170709.0 [] />
Jul 10 10:12:04 imgbased: 2017-07-10 10:12:04,345 [INFO] New layer will be: <Layer ovirt-node-ng-4.1.3-0.20170709.0+1 />
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#012    check_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#012    v.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 at ovirt.org<mailto:Users at ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users

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

--

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA<https://www.redhat.com/>

rbarry at redhat.com<mailto:rbarry at redhat.com>    M: +1-651-815-9306<tel:+1-651-815-9306>     IM: rbarry
[https://www.redhat.com/files/brand/email/sig-redhat.png]<https://red.ht/sig>

--

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA<https://www.redhat.com/>

rbarry at redhat.com<mailto:rbarry at redhat.com>    M: +1-651-815-9306<tel:+1-651-815-9306>     IM: rbarry
[https://www.redhat.com/files/brand/email/sig-redhat.png]<https://red.ht/sig>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170710/63ce72c7/attachment-0001.html>