Browse Source

Disable auto configuration of new interfaces in NetworkManager

NetworkManager in Centos images configures new network devices as soon
as they appear in the default namespace, it means that we might have
conflicts between the management interface's routes and address and the
new VIP or member interfaces' routes and addresses during a small period
of time before they are moved to the amphora-haproxy namespace.

Now, the "no-auto-default=*" option is enabled in NetworkManager, it
disables the configuration of new interfaces, while the management
interface is still enabled/configured through cloud-init.

Story 2008599
Task 41773

Change-Id: I6dd8e99b07ff557674871cb503dece96a9df3ada
(cherry picked from commit a518cefda1332042d50e5ce2814f0af933c62457)
(cherry picked from commit b9f622b335dd4f95f1a6004bb94159f891ca0980)
(cherry picked from commit 7b2424685e9f29116d48cf2d0922f552fd4c2fdd)
changes/05/776905/1
Gregory Thiemonge 3 months ago
committed by Carlos Goncalves
parent
commit
0288729295
1 changed files with 7 additions and 0 deletions
  1. +7
    -0
      elements/amphora-agent/static/etc/NetworkManager/conf.d/no-auto-default.conf

+ 7
- 0
elements/amphora-agent/static/etc/NetworkManager/conf.d/no-auto-default.conf View File

@ -0,0 +1,7 @@
[main]
# Disable auto configuration for newly detected devices.
# This prevents having temporary addresses and routes in the default namespace
# between the detection of a new devices and its move to the amphora-haproxy
# namespace.
# The management interface configuration is triggered by cloud-init.
no-auto-default=*

Loading…
Cancel
Save