Project

General

Profile

Actions

Bug #6241

closed

Models allow invalid proxy associations

Added by Stephen Benjamin almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Smart Proxy
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

There's no validation on models that have proxies (Domain, Subnet,
puppet, etc) that those proxies actually have those features.

A user can assign a DNS proxy to a Domain using the API, even if
the proxy doesn't support DNS. But, similar to #6240, they can't
even see this invalid association in the UI.


Related issues 2 (2 open0 closed)

Related to Foreman - Bug #6240: When a feature is removed from a proxy, the relevant models still keep the associationNew06/16/2014Actions
Related to Foreman - Bug #7371: When proxy of wrong type is associated to subnet/domain, it isn't shown when editingNew09/08/2014Actions
Actions #1

Updated by Stephen Benjamin almost 10 years ago

  • Related to Bug #6240: When a feature is removed from a proxy, the relevant models still keep the association added
Actions #2

Updated by Dominic Cleal almost 10 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1110383
Actions #3

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #7371: When proxy of wrong type is associated to subnet/domain, it isn't shown when editing added
Actions #4

Updated by Ondřej Pražák about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Ondřej Pražák
Actions #5

Updated by The Foreman Bot about 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3168 added
Actions #6

Updated by Ondřej Pražák about 8 years ago

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

Updated by Dominic Cleal about 8 years ago

  • translation missing: en.field_release set to 71
Actions

Also available in: Atom PDF