[pve-devel] [PATCH ifupdown2 2/4] config: keep ifreload_down_changed=0

Alexandre Derumier aderumier at odiso.com
Wed Apr 17 01:25:51 CEST 2019


bug introduce is commit 
https://git.proxmox.com/?p=ifupdown2.git;a=commit;h=b58be4449b3a009ba8324e3f414f2355fcf94c06

We don't stop/start interface on config change,
but only apply changes. (to avoid stop/start bridge as we don't track tap/veth)
---
 debian/patches/pve/0001-config-tuning.patch | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/debian/patches/pve/0001-config-tuning.patch b/debian/patches/pve/0001-config-tuning.patch
index 1633ec4..8e35cba 100644
--- a/debian/patches/pve/0001-config-tuning.patch
+++ b/debian/patches/pve/0001-config-tuning.patch
@@ -38,15 +38,6 @@ index e1035d6..e9264b5 100644
  
  # ifquery check status strings.
  # By default `ifquery --check` prints the check and
-@@ -67,7 +67,7 @@ delay_admin_state_change=0
- # ifreload by default downs: 'all interfaces for which config changed' +
- # 'interfaces that were deleted'. With the below variable set to '0'
- # ifreload will only down 'interfaces that were deleted'
--ifreload_down_changed=0
-+ifreload_down_changed=1
- 
- # squash all addr config when you process the first interface
- addr_config_squash=0
 -- 
 2.11.0
 
-- 
2.11.0




More information about the pve-devel mailing list