yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1438027] Re: backing file path isn't relative path for file-based volume drivers using qcow2 snapshots

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 24 Jun 2015 12:21:01 -0000
Reply-to: Bug 1438027 <1438027@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => liberty-1

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

Title:
  backing file path isn't relative path for file-based volume drivers
  using qcow2 snapshots

Status in Cinder:
  Invalid
Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  For file-based volume drivers (eg; GlusterFS) that uses qcow2
  snapshotting mechanism doesn't use relative path post an online snap
  delete operation.

  In my testing with GlusterFS , I see 2 scenarios where the backing file path was using nova mnt instead of relative path.
  eg: /opt/stack/data/nova/mnt/f4c6ad7e3bba4ad1195b3b538efab64a/volume-518a8faa-f264-4c07-80d7-ff691278b5da.838a5847-cb90-4279-b50f-f8f995321665

  This is incorrect since after the volume is detach, the above path is
  invalid on the cinder/storage node.

  The 2 scenarios are blockCommit and blockRebase for file-based volume
  drivers.

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