yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Nova has similar issues with local lvm block storage:

http://logs.openstack.org/80/237480/8/check/gate-tempest-dsvm-
full/96d1bff/logs/screen-n-cpu.txt.gz?level=TRACE

** Also affects: nova
   Importance: Undecided
       Status: New

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
     Assignee: (unassigned) => Matt Riedemann (mriedem)

-- 
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/1191960

Title:
  force-delete of cinder volume errors with Can\'t remove open logical
  volume

Status in Cinder:
  Fix Released
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  As a consequence of Bug #1191431, few volumes were left in
  error_deleting state. Few of the cleared off by issuing cinder delete
  <uuid>, however few of the errored out.

  1.When you try deleting such volume from Horizon > volume > check box > Delete Volumes 
  Error: You do not have permission to delete volume: <Volume: 078cd44b-7b39-4867-a1e9-78bb758ae0a7>  

  2.When you try using 'Force Delete Volume' option against the suspected volume. The request gets submitted successfully, however you will see following error messages in /var/log/cinder/cinder-volume on the controller node: 
  ProcessExecutionError: Unexpected error while running command. Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvremove -f cinder-volumes/volume-078cd44b-7b39-4867-a1e9-78bb758ae0a7 
  Exit code: 5
  Stdout: ''Stderr: '  Can\'t remove open logical volume "volume-078cd44b-7b39-4867-a1e9-78bb758ae0a7"\n' 

  3.When you try delete manually through command line, you get the following error: 
  lvremove -f /dev/cinder-volumes/volume-078cd44b-7b39-4867-a1e9-78bb758ae0a7 Can't remove open logical volume "volume-078cd44b-7b39-4867-a1e9-78bb758ae0a7" 

  
  Workaround
  1.The volume is left in in-use state by tgtd service that causes cinder delete and force-delete not to work. Stop the service that is using it: 
  service tgt stop 
  lvremove /dev/cinder-volumes/volume-078cd44b-7b39-4867-a1e9-78bb758ae0a7  

  2.Now, remove it through cinder-api or cli 
  service tgt start 
  cinder force-delete 078cd44b-7b39-4867-a1e9-78bb758ae0a7  

  Note: lsof /dev/cinder-volumes/volume-078cd44b-
  7b39-4867-a1e9-78bb758ae0a7  reported tgtd using it.

  
  Expected behavior: force-delete option must address such anomalies.

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