← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1218123] Re: shared filesystem drivers never disconnect

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


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

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

Title:
  shared filesystem drivers never disconnect

Status in Cinder:
  Invalid
Status in OpenStack Compute (nova):
  Expired

Bug description:
  While refactoring the NFS code and moving the higher level functions
  in to brick it was noticed that the NFS driver doesn't actually "do
  anything" on a disconnect_volume.  Understood that disconnecting NFS
  mounts is tricky, but leaving stale connections around in a large
  scale env like OpenStack seems like pretty bad practice.

  There should probably be some tracking here, eharney had a good
  suggestion of using something like a ref counter of attaches and
  perhaps an audit process could kill them all when none are in use
  anymore (I winged that a bit, he may have a better idea/description
  here).

  Also note that this issues is present in the existing Nova code base
  as well, it was just copied over in to the cinder/brick modules.

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