yahoo-eng-team team mailing list archive

[Evgeny Antyshev <eantyshev@xxxxxxxxx>]

Public bug reported:

Occasionally, Virtuozzo Storage CI fails 1 testcase, with following error in nova-compute:
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Command: pstorage-mount -c testcluster_uypcf0k16f -u stack -g root -m 0770 -l /var/log/vstorage/testcluster_uypcf0k16f/nova.log.gz /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Exit code: 255
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stdout: u''
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stderr: u'20-09-17 09:40:55.782 vstorage-mount: mounting vstorage://testcluster_uypcf0k16f at /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4 with flags: 0xc06, params: fd=3,rootmode=40000,user_id=0,group_id=0,allow_other,default_permissions,writeback_enable,direct_enable,umount_wait,\nvstorage-mount: failed to initialize log file\n20-09-17 09:40:55.832 fuse_umount: /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4\n' {{(pid=75667) loop /usr/lib/python2.7/site-packages/oslo_privsep/daemon.py:449}}

full log:
http://paste.openstack.org/show/621549/
http://openstack-3rd-party-storage-ci-logs.virtuozzo.com/44/504944/3/check/dsvm-tempest-kvm/eed2bd5/console.html

This is a consequence of simultaneously connecting 2 volumes, since
connect_volume() is not synchronized, like f.e. in Quobyte driver. BTW,
many other drivers should suffer from this mistake.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1718474

Title:
  Vzstorage driver doesn't lock when connecting volume

Status in OpenStack Compute (nova):
  New

Bug description:
  Occasionally, Virtuozzo Storage CI fails 1 testcase, with following error in nova-compute:
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Command: pstorage-mount -c testcluster_uypcf0k16f -u stack -g root -m 0770 -l /var/log/vstorage/testcluster_uypcf0k16f/nova.log.gz /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Exit code: 255
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stdout: u''
  Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Stderr: u'20-09-17 09:40:55.782 vstorage-mount: mounting vstorage://testcluster_uypcf0k16f at /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4 with flags: 0xc06, params: fd=3,rootmode=40000,user_id=0,group_id=0,allow_other,default_permissions,writeback_enable,direct_enable,umount_wait,\nvstorage-mount: failed to initialize log file\n20-09-17 09:40:55.832 fuse_umount: /opt/stack/data/nova/mnt/0d5556ed3994ee64ccc877564e48b2a4\n' {{(pid=75667) loop /usr/lib/python2.7/site-packages/oslo_privsep/daemon.py:449}}

  full log:
  http://paste.openstack.org/show/621549/
  http://openstack-3rd-party-storage-ci-logs.virtuozzo.com/44/504944/3/check/dsvm-tempest-kvm/eed2bd5/console.html

  This is a consequence of simultaneously connecting 2 volumes, since
  connect_volume() is not synchronized, like f.e. in Quobyte driver.
  BTW, many other drivers should suffer from this mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1718474/+subscriptions