Bug 1713214

Summary:	Editing subnet for an existing host creates 409 DHCP conflict
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	DHCP & DNS	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED WONTFIX	QA Contact:	Radovan Drazny <rdrazny>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.5	CC:	aruzicka, logank, mkalyat, mshira, roarora, sadas
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:	2021-01-19 21:33:52 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 Lukas Zapletal 2019-05-23 07:43:44 UTC

This is a known issue/limitation of our DHCP orchestration framework.

WORKAROUND: Delete and create a new host.

Comment 3 Logan Kuhn 2019-05-23 11:54:15 UTC

Support case with logs: https://access.redhat.com/support/cases/#/case/02153260

Comment 6 Lukas Zapletal 2020-01-16 11:06:00 UTC

We recognize this as a valid bug, it needs to get priorized and fixed.

Comment 8 Lukas Zapletal 2020-09-30 12:16:30 UTC

I have reproduced this on Satellite 6.8, this is still a valid issue for both DNS and DHCP.

Comment 9 Mike McCune 2020-12-09 22:17:22 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 10 Mike McCune 2021-01-19 21:25:38 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 your Red Hat Account Team. Thank you.