Bug 50627

Summary:	Docker bridge 172.17.42.1/16 conflicts with customer network 172.17.0.0/16
Product:	UCS	Reporter:	Sven Göricke <goericke>
Component:	System setup	Assignee:	UCS maintainers <ucs-maintainers>
Status:	NEW ---	QA Contact:	UCS maintainers <ucs-maintainers>
Severity:	normal
Priority:	P5	CC:	brodersen, damrose, gohmann, grandjean, gulden, requate
Version:	UCS 4.4
Target Milestone:	---
Hardware:	Other
OS:	Linux
What kind of report is it?:	Feature Request	What type of bug is this?:	---
Who will be affected by this bug?:	---	How will those affected feel about the bug?:	---
User Pain:		Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):	Workaround is available
Max CVSS v3 score:
Bug Depends on:	40515, 41596, 41597
Bug Blocks:

Description Sven Göricke

2019-12-11 13:41:22 CET

+++ This bug was initially created as a clone of Bug #40515 +++

See Ticket#2016012621000471

Recently the issue described in #40515 has popped up again at customer site.
If a customer has the network 172.17.0.0/16 it will be in conflict with the default docker bridge with 172.17.42.1/16. The network traffic won't work anymore.

To circumvent the issue we switched to a second console when UCS installation assistant started (just after reboot from base installation) and changed the following two UCR Variables accordingly:

1) docker/daemon/default/opts/bip
2) appcenter/docker/compose/network

Maybe it is also an option to add the docker-network as an configuration item during UCS installation assistant?

Comment 1 Arvid Requate

2019-12-12 21:05:49 CET

> Maybe it is also an option to add the docker-network as an configuration item during UCS installation assistant?

I guess this would have to be added to the system setup, I change the Bug component accordingly.