Bug 1399443

Summary:	[RFE] Forcing dhcpd to delete the lease through foreman-proxy/omapi shell
Product:	Red Hat Satellite	Reporter:	Selim Jahangir <mjahangi>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.4	CC:	aperotti, dmitri, fgarciad, inecas, mjahangi, mmithaiw
Target Milestone:	Unspecified	Keywords:	FutureFeature
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:	2018-09-04 19:11:48 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:

Description Selim Jahangir 2016-11-29 05:01:46 UTC

Description of problem:

Customer used capsule servers to provision via DHCP. Customer provisioned VM on management network(e.g. 10.13.x.x) and then customer assigned a static IP as part of the build process from different subnet. It has been noticed that the original dynamic build IP reservations are never getting deleted from /var/lib/dhcpd/dhcpd.leases. This has caused issues for customer when trying to rebuild hosts and also customer will potentially run out of leases in the future.

So this RFE is to force dhcpd to delete the lease through foreman-proxy/omapi shell

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
After the lease expired satellite server suppose to delete the IP and it is not happening in this case.

Expected results:
The IP lease should expire after the expiry date.

Additional info:

Comment 6 Ivan Necas 2017-12-13 12:19:03 UTC

Dmitri: thoughts on achievability of the request + looking over the customer case to understand better what the root cause of the issue might be?

Comment 8 Dmitri Dolguikh 2017-12-13 18:56:04 UTC

Whatever the fix is going to be, the action has to be initiated from Foreman -- smart-proxy's dhcp module isn't aware of host address changes and it will keep the reservation around until the host (and therefore the reservation) is deleted. 

Probably means that an additional orchestration associated with host address change is required?

Comment 12 Dmitri Dolguikh 2017-12-15 20:13:07 UTC

Selim: How does the customer change host's ip address, step-by-step if possible, please?
Are there any errors in the log related to ip address change (or around the same time), particularly from smart-proxy's dhcp module?

Comment 15 Dmitri Dolguikh 2018-01-22 18:36:06 UTC

I don't think this is going to work -- the ip address is being changed outside of Satellite and it continues to track the host using the ip address initially assigned to it.

They should be able to assign static ip addresses using a provisioning template (please refer to https://access.redhat.com/documentation/en-us/red_hat_satellite/6.1/html/provisioning_guide/sect-red_hat_satellite-provisioning_guide-provisioning_hosts_with_static_ip_addresses for details).

Alternatively, if the client isn't interested in managing servers after they have been provisioned (as they cannot manage them atm), they could delete them from Satellite -- their ip addresses will be released then.

Comment 16 Bryan Kearney 2018-09-04 18:59:46 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 17 Bryan Kearney 2018-09-04 19:11:48 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.