Bug #6241
closed
Models allow invalid proxy associations
Added by Stephen Benjamin almost 10 years ago.
Updated almost 6 years ago.
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 open — 0 closed)
- Related to Bug #6240: When a feature is removed from a proxy, the relevant models still keep the association added
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1110383
- Related to Bug #7371: When proxy of wrong type is associated to subnet/domain, it isn't shown when editing added
- Status changed from New to Assigned
- Assignee set to Ondřej Pražák
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3168 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- translation missing: en.field_release set to 71
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by