Bug #7794
open
order of windows DHCP and DNS deletions causes error
Description
After creating a VM in foreman using a windows DHCP and DNS smart proxy, then attempting to delete the VM, I get the following error:
"Remove Reverse DNS record for foreman-test04.healthmedia.com task failed with the following error: ERF12-1261 [ProxyAPI::ProxyException]: Unable to delete DNS entry ([RestClient::BadRequest]: 400 Bad Request) for proxy https://foreman01.healthmedia.com:8443"
It appears that Foreman doesn't delete the entry in DHCP before DNS, which causes the DNS removal to error out:
- nsupdate -g
server 172.16.0.1
update delete foreman-test04.healthmedia.com
send
server 172.16.0.1
update delete 7.17.16.172.in-addr.arpa PTR
send
; TSIG error with server: tsig verify failure
update failed: REFUSED
(there's no log entries that show Foreman attempted to delete the DHCP record)
If I go onto the windows DHCP smart proxy server and run "delete reservedip 172.16.17.7 00505689587a" then attempt to delete the PTR record again, I can delete it OK.
So it appears that the DHCP smart proxy needs to be called before the DNS smart proxy when deleting entries, at least with the windows side of things.
(obviously, I have a manual workaround right now, but it would be nice to have this working in a future release)
Files
Updated by Anthony Clark over 9 years ago
Additionally, when building a host, the DHCP/DNS order appears to matter too.
The same setup as above has an interesting issue. The DNS entry is created and accessible during the build, but is then deleted once the host is built. There's nothing in the DNS smart proxy log to indicate that a deletion takes place on that side. That leads me to believe that the DHCP smart proxy is somehow removing that DNS entry.
(makes me wish I could use bind and isc dhcpd ;)
Updated by Dominic Cleal over 9 years ago
- translation missing: en.field_release deleted (
22)