Bug 39872 – Incomplete DHCP configuration

Bug 39872 - Incomplete DHCP configuration


Summary:	Incomplete DHCP configuration

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	Docker
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-11-11 10:23 CET by Philipp Hahn
Modified:	2021-04-27 10:32 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
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.006
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

2015-11-11 10:23:01 CET

For proper functioning the DHCP server need to know the complete network topology - otherwise the DHCP server can't detect hosts moved between physical networks.
For docker the bridge "docker0" with IP 172.17.42.1/16 was added.
The dhcpd rightfully complains about that interface not being declared every time the dhcpd is started:

Nov 11 10:19:28 dc0 dhcpd: No subnet declaration for docker0 (172.17.42.1).
Nov 11 10:19:28 dc0 dhcpd: ** Ignoring requests on docker0.  If this is not what
Nov 11 10:19:28 dc0 dhcpd:    you want, please write a subnet declaration
Nov 11 10:19:28 dc0 dhcpd:    in your dhcpd.conf file for the network segment
Nov 11 10:19:28 dc0 dhcpd:    to which interface docker0 is attached. **

Comment 1 Stefan Gohmann

2019-01-03 07:18:49 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.

Comment 2 Philipp Hahn

2019-03-11 05:44:08 CET

Still an issue with UCS-4.4-0

Comment 3 Philipp Hahn

2021-04-27 10:32:47 CEST

Still an issue with UCS-5.0-0