Bug 1700765

Summary:	DHCP Conflict error due to Host entries not cleaned
Product:	Red Hat Satellite	Reporter:	Vatsal Parekh <vparekh>
Component:	Networking	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Roman Plevka <rplevka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	mshira, pkliczew
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-08 13:13:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vatsal Parekh 2019-04-17 10:57:44 UTC

Description of problem:
On the latest nightly foreman, I saw that I tried to create hosts with KubeVirt compute resource, there were some issues with the provisioning parameters and it didn't actually create it, but when going to create those hosts again with the same mac, I was getting this DHCP conflict error, debugging further found out that entries were not cleared dhcpd.leases.
Once I cleared those entries manually from dhcpd.leases and restarted dhcpd, the host creation worked again.

production.log
```
2019-04-17T06:18:19 [W|app|339e4a72] Create DHCP Settings for sally-woodcock.example.com task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::Conflict]: 409 Conflict) for proxy https://host-8-249-193.host.centralci.eng.rdu2.redhat.com:8443/dhcp
ProxyAPI::ProxyException: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::Conflict]: 409 Conflict) for proxy https://host-8-249-193.host.centralci.eng.rdu2.redhat.com:8443/dhcp
```

Version-Release number of selected component (if applicable):
nightly of foreman, master of foreman-kubevirt

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Gives the conflict error for dhcp as the entries were not automatically cleaned by foreman for the hosts that were deleted or creation had failed

Expected results:


Additional info:
Not able to fully reproduce it right now, but saw this more then once, so filed this

Comment 3 Piotr Kliczewski 2019-04-17 13:34:18 UTC

This bug seems to be either foreman or environment issue. Shira please take a look

Comment 5 Bryan Kearney 2020-05-01 14:22:40 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 6 Bryan Kearney 2020-06-08 13:13:56 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.