From 441667560e23d60f7a9f097cabb5fefad906aa3d Mon Sep 17 00:00:00 2001 From: Till Maas Date: Wed, 25 Jul 2018 22:31:57 +0200 Subject: [PATCH] Update limitations of initscripts and nm provider --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 1ffbd47..998c4b1 100644 --- a/README.md +++ b/README.md @@ -489,6 +489,15 @@ so that the host is connected to a management LAN or VLAN. It strongly depends o via the `up` or `down` [states](#state) -- unless of course, there are other components that watch the ifcfg files and react on changes. +- The initscripts provider requires the different profiles to be in the right + order when they depend on each other, for example the bonding master device + needs to be specified before the slave devices. + +- When removing a profile for NetworkManager it will also take the connection + down and possibly remove virtual interfaces. With the initscripts provider + removing a profile does not change its current runtime state (this is going + to be the case for NetworkManager in the future, too.). + - For NetworkManager, modifying a connection with autoconnect enabled may result in the activation of the new profile on a previously disconnected interface. Also, deleting a NetworkManager connection that is currently active