Bug #10030
closed
Foreman fails to find VMware templates when they're in a folder
Added by David Patterson about 9 years ago.
Updated almost 6 years ago.
Category:
Compute resources - VMware
|
|
Description
Our VMware5.1 DC is setup as: vCenter -> Datacenter -> Folder -> Template_name. When trying to provision a new VM using the template, Foreman fails to find the template, with this error:
Failed to create a compute POD_Dev (VMware) instance dlaxtest500.apolloglobal.int: _Templates/_ESX5x-RHEL6.5-v2 was not found
See the attached file for a full stack trace. The stack trace contains everything from when I hit 'Submit' to when the error showed up in the Foreman web UI.
When I move the template to: vCenter -> Datacenter -> Template_name, Foreman can find and clone the template fine.
Files
That's quite a problem... We can possibly handle this as a VMware fog extension until Fog releases a new version with the fix. If you can come up with a patch or you know some work around please share it so we can publicize it.
Unfortunately, the only thing worse that my coding abilities is my ruby knowledge :(
- translation missing: en.field_release set to 28
- Assignee set to Shlomi Zadok
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2305 added
- Pull request deleted (
Shlomi Zadok wrote:
A patch has been applied to fog gem: https://github.com/fog/fog/pull/3531
Dominic, Would you rather have this patch overridden into Foreman (w/ fog_extension)?
Probably both if we can - a change to fog_extensions for develop and 1.8, and then once the fog fix is merged and release, revert it and use the proper fix.
- translation missing: en.field_release changed from 28 to 50
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Refactor #10371: Revert vSphere templates in folders workaround (#10030) added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by