Bug 47411 – Wrong DHCP configuration should not stop DHCP service

Bug 47411 - Wrong DHCP configuration should not stop DHCP service


Summary:	Wrong DHCP configuration should not stop DHCP service

Status:	RESOLVED DUPLICATE of bug 36648

Product:	UCS
Classification:	Unclassified
Component:	DHCP
Version:	UCS 4.3
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-07-30 11:48 CEST by Nico Gulden
Modified:	2018-07-30 11:59 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.257
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018071921000273
Bug group (optional):	External feedback
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 Nico Gulden

2018-07-30 11:48:56 CEST

A customer has created a new subnet (192.168.66.0) and a new pool (Pool-Netz-66) in the DHCP module in UMC that only included the IP address 192.168.66.222.

Maybe the error was that the first and the last ip address had already been set to 192.168.66.222.

There was no error message after the configuration has been saved. The configuration resulted in a stopped dhcp service and now user was a assigned an IP address anymore.

Configuration errors in the frontend should be checked and saving them should be prevented so that DHCP is still running.

See the excerpt from the syslog at Ticket#2018071921000273

Comment 1 Philipp Hahn

2018-07-30 11:59:00 CEST


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