Bug #14874
closed
Path incorrect when using vm_clone method
Description
This is related to the fix for Bug #5630.
The fix for this (http://projects.theforeman.org/projects/foreman/repository/revisions/e7d21bf01f2b9eee19b808c4ea320ddfd9c33b3d) breaks our deployment.
I'm wondering if the path_replace is even required?
So our datacenter is: 'Turitea ITS'
Our original path is '/Datacenters/Turitea/Turitea ITS/vm/Production/Foundation/Infrastructure'
After the path_replace has been done the path is: '/DatacentersProduction/Foundation/Infrastructure' - which obviously doesn't work.
But looking at the original code before the fix for Bug #5630 was applied, after running the original path_replace our path wasn't changed and seemed to deploy via vmware as expected.
Updated by Francois Herbert over 8 years ago
The method is clone_vm not vm_clone.
Updated by Dominic Cleal over 8 years ago
- Related to Bug #5630: VmWare clone from template fails if Network Adator has labels in VmWare added
Updated by Timo Goebel over 8 years ago
Francois, have you tried removing path_replace completely? I believe cloning should work without this, however I can't test it right now unfortunately.
Updated by Francois Herbert over 8 years ago
Timo, I've just tested removing path_replace completely and the VM deploys from template as expected.
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3497 added
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 01fd5003391d043dda0778ee0cf83abf3debb229.
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 155