Actions
Bug #5903
closed
Deleting smart proxy from GUI fails
Status:
Duplicate
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Description
A proper error message should be generated instead, saying that an existing hostgroup is using the proxy.
Oops, we're sorry but something went wrong
Warning! ERROR: update or delete on table "smart_proxies" violates foreign key constraint "hostgroups_puppet_ca_proxy_id_fk" on table "hostgroups" DETAIL: Key (id)=(2) is still referenced from table "hostgroups".
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.
PG::ForeignKeyViolation ERROR: update or delete on table "smart_proxies" violates foreign key constraint "hostgroups_puppet_ca_proxy_id_fk" on table "hostgroups" DETAIL: Key (id)=(2) is still referenced from table "hostgroups". app/controllers/smart_proxies_controller.rb:51:in `destroy' app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call'
Updated by Jon Skarpeteig almost 10 years ago
Or better yet, remove the proxy from the hostgroup
Updated by Dominic Cleal almost 10 years ago
- Is duplicate of Bug #5788: before_destroy missing from EnsureNotUsedBy.new in SmartProxy model added
Updated by Dominic Cleal almost 10 years ago
- Status changed from New to Duplicate
We've just made a change in #5788 which will show a proper error message indicating which other resources rely on that smart proxy. This'll be in 1.5.1.
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #5904: Deleting a smart proxy should be easier due to number of associations added
Actions