Bug #505
VM Deployment Fails with NFS drivers
Status: | Closed | Start date: | 02/14/2011 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Javi Fontan | % Done: | 0% | |
Category: | Drivers - Auth | Estimated time: | 1.00 hour | |
Target version: | Release 2.2 | |||
Resolution: | duplicate | Pull request: | ||
Affected Versions: |
Description
Symptoms: oned creates the image and the context in /var/lib/one instead of the shared directory /srv/cloud/one/var/images/ after upgrading to 2.1-1
After seeing all my VM failing to boot, I started watching the log wandering under which absurd hypotesis (i.e. "The Vogon already demolished the planet" :) ) an
echo "/one/var/images/[vmid]/images/disk.0" | $SED -e 's/^[^:]*:\(.*\)$/\1/'
(core of arg_path called in tm_clone.sh) would change /srv/cloud/one/var/images/[vmid] into /var/lib/one/[vmid] when I saw a little
fix_paths
about in line 35... This function is defined in tm_common.sh and does that change :) !
Therefore i commented it and did the same to the
fix_dst_path
inline 41 of tm_context.sh and to the
fix_src_path
in line 34 of tm_delete.sh
Could it be that these instructions slipped in from the SSH driver ?
(reopens 484, sorry!)
Associated revisions
History
#1 Updated by Javi Fontan over 10 years ago
- Status changed from New to Closed
- Resolution changed from worksforme to duplicate