Project

General

Profile

Bug #10030

Foreman fails to find VMware templates when they're in a folder

Added by David Patterson about 7 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shlomi Zadok
Category:
Compute resources - VMware
Target version:
1.8.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/2305
Fixed in Releases:
Found in Releases:
1.8.0

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.

template_fail.txt template_fail.txt 42.5 KB David Patterson, 04/06/2015 04:58 PM

Related issues

Related to Foreman - Refactor #9107: Update fog to 1.28.xClosed2015-01-26
Related to Foreman - Refactor #10371: Revert vSphere templates in folders workaround (#10030)Resolved2015-05-05

Associated revisions

Revision 0af12f79 (diff)
Added by Shlomi Zadok about 7 years ago

fixes #10030 - use override method to display templates in folders

Revision dc6342d0 (diff)
Added by Shlomi Zadok about 7 years ago

fixes #10030 - use override method to display templates in folders

(cherry picked from commit 0af12f79a6e6c3a3ecf72d39df89a2edd7e9b39b)

History

#1 Updated by David Patterson about 7 years ago

It seems Fog 1.28 is what broke this:

https://github.com/fog/fog/issues/3458

#2 Updated by Daniel Lobato Garcia about 7 years ago

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.

#3 Updated by David Patterson about 7 years ago

Unfortunately, the only thing worse that my coding abilities is my ruby knowledge :(

#4 Updated by Dominic Cleal about 7 years ago

#5 Updated by Dominic Cleal about 7 years ago

  • Legacy Backlogs Release (now unused) set to 28

#6 Updated by Shlomi Zadok about 7 years ago

  • Assignee set to Shlomi Zadok

#7 Updated by Shlomi Zadok about 7 years ago

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)?

#8 Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2305 added
  • Pull request deleted ()

#9 Updated by Dominic Cleal about 7 years ago

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.

#10 Updated by Dominic Cleal about 7 years ago

  • Legacy Backlogs Release (now unused) changed from 28 to 50

#11 Updated by Shlomi Zadok about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#12 Updated by Dominic Cleal about 7 years ago

  • Related to Refactor #10371: Revert vSphere templates in folders workaround (#10030) added

Also available in: Atom PDF