Actions
Bug #6241
closed
Models allow invalid proxy associations
Difficulty:
Triaged:
Bugzilla link:
Pull request:
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.
Updated by Stephen Benjamin over 10 years ago
- Related to Bug #6240: When a feature is removed from a proxy, the relevant models still keep the association added
Updated by Dominic Cleal over 10 years ago
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1110383
Updated by Dominic Cleal over 10 years ago
- Related to Bug #7371: When proxy of wrong type is associated to subnet/domain, it isn't shown when editing added
Updated by Ondřej Pražák about 9 years ago
- Status changed from New to Assigned
- Assignee set to Ondřej Pražák
Updated by The Foreman Bot about 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3168 added
Updated by Ondřej Pražák about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 4693fe5f86d75a3fbcc37596e7171594ebca6384.
Updated by Dominic Cleal about 9 years ago
- Translation missing: en.field_release set to 71
Actions