Bug #4349
Datastore migration does not work with qcow2 drivers
| Status: | Closed | Start date: | 02/19/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | Drivers - Storage | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.14 |
Description
mv action of qcow2 drivers is a noop. This makes migration from system datastores break.
Associated revisions
bug #4349: use relative paths for qcow2 snapshots
This fixes system datastore migrations
bug #4349: use relative path on qcow2 revert
bug #4349: do not use ln -r in qcow2 clone
This ln parameter is not available in CentOS 6
bug #4349: bug in snap_revert
bug #4349: fix bug in qcow2 disk snapshot revert
bug #4349: create relative links in cold snapshot
History
#1
Updated by Ruben S. Montero over 5 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme
TM_MAD = shared for qcow2 configurations, as explained here
http://docs.opennebula.org/4.14/administration/storage/fs_ds.html#configuring-the-system-datastore
#2
Updated by Javi Fontan over 5 years ago
- Status changed from Closed to Pending
- Assignee set to Javi Fontan
- Resolution deleted (
worksforme)
The paths generated for snapshots are absolute, for both symlinks to snaps dir and qcow2 base images. This also breaks machines after they are migrated.
#3
Updated by OpenNebula Systems Support Team over 5 years ago
- Status changed from Pending to Closed
- Resolution set to fixed