Description of problem: After a failed deployment I've tried to remove the assignment of the hosts and move it to a new deployment that I've created. The unassaignment of the host fails with the output: Error Validation failed: Conflict DHCP records -a2:54:00:86:80:92/192.168.0.7 already exists ActiveRecord::RecordInvalid Validation failed: Conflict DHCP records -a2:54:00:86:80:92/192.168.0.7 already exists app/models/concerns/foreman/thread_session.rb:33:in `clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in `call' Version-Release number of selected component (if applicable): I'm not sure which log provides additional info, if you need more info, please direct me. How reproducible: unknown Steps to Reproduce: 1. Run a deployment 2. try to unassign the Neutron host Actual results: The unassignment fails Expected results: the action succeeds Additional info:
from the /var/log/foreman/production.log : Started POST "/deployments/1/unassign_host" for 10.35.3.165 at 2014-07-30 04:53:55 -0400 Processing by Staypuft::DeploymentsController#unassign_host as HTML Parameters: {"utf8"=>"✓", "authenticity_token"=>"J8I87X71q4PLvC7eNxBDcPw24QewcYEd7M5OMH/qL5M=", "commit"=>"Unassign Hosts", "hostgroup_id"=>"5", "host_ids"=>["4"], "id"=>"1"} DHCP records -a2:54:00:86:80:92/192.168.0.7 already exists Operation FAILED: Validation failed: Conflict DHCP records -a2:54:00:86:80:92/192.168.0.7 already exists Rendered common/500.html.erb within staypuft/layouts/staypuft (145.9ms) Rendered layouts/base.html.erb (3.2ms) Rendered /opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.1.21/app/views/staypuft/layouts/application.html.erb (5.8ms) Completed 500 Internal Server Error in 3054ms (Views: 310.5ms | ActiveRecord: 46.6ms) Started GET "/assets/staypuft/staypuft-704afdc8a5b25362c6d5cecac9777092.js" for 10.35.3.165 at 2014-07-30 04:53:58 -0400 Started GET "/assets/staypuft/staypuft-d6b29eb43942298baa46ef6a62f53222.css" for 10.35.3.165 at 2014-07-30 04:53:58 -0400
This does not reproduce in current builds