Project

General

Profile

Actions
Copy link

Bug #1340

closed

can't remove host due to dhcp issue

Added by Corey Osman over 12 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Unable to save
DHCP Settings for puppetdemo1.demo.corp task failed with the following error: 400 Bad Request

I am unable to remove the host or change the IP because foreman cannot remove the reservation from the dhcp server.


Processing HostsController#update (for 192.0.248.104 at 2011-11-17 19:52:12) [PUT]
  Parameters: {"commit"=>"Submit", "action"=>"update", "_method"=>"put", "authenticity_token"=>"/L+9rIwt9kTkNHUXd6uhltKCWPbjEOvLxMC3sMStH24=", "id"=>"puppetdemo1.demo.corp", "controller"=>"hosts", "host"=>{"comment"=>"", "architecture_id"=>"1", "subnet_id"=>"", "managed"=>"1", "puppetproxy_id"=>"3", "name"=>"puppetdemo1", "sp_mac"=>"", "puppetmaster_name"=>"puppetprod1.demo.corp", "sp_name"=>"", "mac"=>"00:50:56:bb:03:5e", "domain_id"=>"1", "enabled"=>"1", "root_pass"=>"[FILTERED]", "medium_id"=>"6", "hostgroup_id"=>"5", "is_owned_by"=>"2-Users", "ptable_id"=>"1", "sp_subnet_id"=>"", "ip"=>"10.20.0.198", "environment_id"=>"1", "model_id"=>"", "disk"=>"", "sp_ip"=>"", "puppetclass_ids"=>[""], "operatingsystem_id"=>"11"}}
Delete DHCP reservation for puppetdemo1.demo.corp-00:50:56:bb:03:5e/192.0.19.198
DHCP Settings for puppetdemo1.demo.corp task failed with the following error: 400 Bad Request
Rolling back due to a problem: DHCP Settings for puppetdemo1.demo.corp     5     failed     puppetdemo1.demo.corpdel_dhcp
Failed to save: DHCP Settings for puppetdemo1.demo.corp task failed with the following error: 400 Bad Request
Rendering template within layouts/application
Rendering hosts/edit
Completed in 3601ms (View: 348, DB: 14) | 200 OK [https://foreman/hosts/puppetdemo1.demo.corp]

Actions
Copy link
 #1

Updated by Ohad Levy over 12 years ago

  • Assignee set to Corey Osman

what is in the proxy log?
can you try with the latest proxy / foreman code and see if you can reproduce this?

Actions
Copy link
 #2

Updated by Ohad Levy over 12 years ago

  • Status changed from New to Need more information
Actions
Copy link
 #3

Updated by Corey Osman over 12 years ago

I actually worked around the issue yesterday. Here is the problem.

1. If the proxy for the dhcp server cannot be reached or is not working it throws that error.

2. If I remove the dhcp proxy server from the subnet that the host belongs to I can then delete the node.

There must be some dependency between the dhcp proxy and the host that is keeping the user from deleting the host.

Actions
Copy link
 #4

Updated by Benjamin Papillon almost 12 years ago

  • Category set to DHCP
Actions
Copy link
 #5

Updated by Benjamin Papillon almost 12 years ago

  • Status changed from Need more information to Assigned
Actions
Copy link
 #6

Updated by Benjamin Papillon almost 12 years ago

  • Status changed from Assigned to New
  • Assignee deleted (Corey Osman)
Actions
Copy link
 #7

Updated by Ohad Levy about 8 years ago

  • Description updated (diff)
  • Status changed from New to Need more information
Actions
Copy link
 #8

Updated by Anonymous almost 7 years ago

  • Status changed from Need more information to Rejected

While the error message could be improved (maybe it was in the meanwhile), the behaviour feels correct

Actions
Copy link

Also available in: Atom PDF