Bug 50627 - Docker bridge 172.17.42.1/16 conflicts with customer network 172.17.0.0/16
Summary: Docker bridge 172.17.42.1/16 conflicts with customer network 172.17.0.0/16
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: System setup
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 40515 41596 41597
Blocks:
  Show dependency treegraph
 
Reported: 2019-12-11 13:41 CET by Sven Göricke
Modified: 2024-06-27 12:10 CEST (History)
6 users (show)

See Also:
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
Customer ID: 00006
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Göricke univentionstaff 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 univentionstaff 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.
Comment 2 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:04 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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