Project

General

Profile

Feature #17316

Proxy templating needs TFTP feature to be turned on

Added by Lukas Zapletal almost 2 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Category:
Templates
Target version:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

This is super confusing, I have a request every single week. I don't know why we implemented it this way, but this should be properly visible via the UI. For each Subnet, user should be able to associate Templates Smart Proxy.


Related issues

Related to Smart Proxy - Feature #969: Direct Client->Foreman communication shouldn't be needed (and moved to the Proxy)Closed2011-06-09

Associated revisions

Revision 009e7bbd (diff)
Added by Lukas Zapletal 6 months ago

Fixes #17316 - templates feature is subnet association

Revision 0507a622 (diff)
Added by Daniel Lobato Garcia 6 months ago

Refs #17316 - Ensure the proxy exists before assigning tftp

If the subnet.tftp proxy didn't exist, the migration fails with

undefined method `has_feature?' for nil:NilClass'

so we rather make sure it exists before trying to set the template
proxy to nil.

History

#1 Updated by Dominic Cleal almost 2 years ago

  • Related to Feature #969: Direct Client->Foreman communication shouldn't be needed (and moved to the Proxy) added

#2 Updated by The Foreman Bot 6 months ago

  • Assignee set to Lukas Zapletal
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5255 added

#3 Updated by Lukas Zapletal 6 months ago

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

#4 Updated by Marek Hulán 6 months ago

  • Legacy Backlogs Release (now unused) set to 330

#5 Updated by The Foreman Bot 6 months ago

  • Pull request https://github.com/theforeman/foreman/pull/5278 added

#6 Updated by Stephen Benjamin 5 months ago

  • Bugzilla link set to 1347748

Also available in: Atom PDF