holland-coredev team mailing list archive

[Andrew Garner <715426@xxxxxxxxxxxxxxxxxx>]

Backported fix from issue5117 and added an additional test for this case
to the holland.lib.lvm test suite.

Fixed in https://github.com/holland-
backup/holland/commit/ebd17d2bb43f88bf69e519802f510675bc74cca8

** Changed in: holland-backup
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Holland
Discuss, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/715426

Title:
  mysql-lvm does not calculate paths relative to / correctly

Status in Holland Backup Framework:
  Fix Committed

Bug description:
  If a mysql datadir  is on a LVM enabled / and we attempt to determine
  the datadir relative to its (root) mountpoint, we get a bad relative
  path:

  >>> from holland.lib.lvm.util import relpath
  >>> relpath('/var/lib/mysql', '/')
  '../var/lib/mysql'

  This causes $snapshot_mountpoint/$relpath to be an non-existent
  directory  for instance /tmp/XXXXX/../var/lib/mysql =>
  /tmp/var/lib/mysql/ which is invalid.

  This is actually a python bug with os.path.relpath:

  http://bugs.python.org/issue5117