Feature #17316
Proxy templating needs TFTP feature to be turned on
Pull request:
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
Associated revisions
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 over 5 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 over 4 years 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 over 4 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 009e7bbd29f31c3750a8be47b4aecf5278c0db95.
#4
Updated by Marek Hulán over 4 years ago
- Legacy Backlogs Release (now unused) set to 330
#5
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/5278 added
#6
Updated by Stephen Benjamin over 4 years ago
- Bugzilla link set to 1347748
#7
Updated by Lukas Zapletal almost 4 years ago
- Related to Bug #24787: Templates subnet association renders to Capsule URL and not template_url added
Fixes #17316 - templates feature is subnet association