Bug 44136 – Difference in handling of "range" property between dhcp/sharedsubnet and dhcp/subnet

Bug 44136 - Difference in handling of "range" property between dhcp/sharedsubnet and dhcp/subnet


Summary:	Difference in handling of "range" property between dhcp/sharedsubnet and dhcp...

Status:	RESOLVED DUPLICATE of bug 33211

Product:	UCS
Classification:	Unclassified
Component:	UMC - DHCP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-29 15:25 CEST by Philipp Hahn
Modified:	2021-04-27 11:21 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.017
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2017-03-29 15:25:56 CEST

dhcp/subnet implements overlap checking for the ranges, while dhcp/sharedsubnet does not.
As the only difference is that the later has the additional objectClass "univentionDhcpSharedSubnet", the implementations should be merged and the later should inherit the improved implementation of the former.

Even better would be to get rid of dhcp/dharedsubnet completely and to detect automatically, if the parent container is objectClass=dhcpSharedNetwork (there could be intermediate dc/ou/... containers!)

Comment 1 Philipp Hahn

2021-04-27 11:21:53 CEST

Fixed with git:e99bd11dee6dce995581d2759bfe5543c8df3da7 for Bug #33211 since Nov 2016

*** This bug has been marked as a duplicate of bug 33211 ***