PVE 8 continously /var/log/ifupdown2/network_config* folders

[f.cuseo]

Hello.
I have a strange problem with my cluster:
- 6 x dell R730 nodes with 4x10Gbit ethernet
- 2 x Cisco Nexus 3000 series

Networking is with a single 4 port LACP bond, with 2 vlans (for ceph and management), and SDN with VLAN and QinQ zones.
Only with node 4, 802.1q guests can't communicate with other nodes, but guests with ethernet in vlan zones, have no problems at all.

In /var/log/ifupdown2/ folder, I have a new folder every 10 seconds. Is normal or there is something wrong that could explain my network problem ?

root@nodo4-cluster1:/var/log/ifupdown2# ls -lat
total 180
drwxr-xr-x 45 root root 4096 Feb 13 18:04 .
drwxr-xr-x 3 root root 4096 Feb 13 18:04 network_config_ifupdown2_1201047_Feb-13-2024_18:04:23.937996
drwxr-xr-x 3 root root 4096 Feb 13 18:04 network_config_ifupdown2_1201046_Feb-13-2024_18:04:14.544168
drwxr-xr-x 3 root root 4096 Feb 13 18:04 network_config_ifupdown2_1201045_Feb-13-2024_18:04:04.157594
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201044_Feb-13-2024_18:03:54.759458
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201043_Feb-13-2024_18:03:44.353603
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201042_Feb-13-2024_18:03:33.954142
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201041_Feb-13-2024_18:03:24.556569
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201040_Feb-13-2024_18:03:14.161663
drwxr-xr-x 3 root root 4096 Feb 13 18:03 network_config_ifupdown2_1201039_Feb-13-2024_18:03:04.777316
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201038_Feb-13-2024_18:02:54.378639
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201037_Feb-13-2024_18:02:43.927431
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201036_Feb-13-2024_18:02:34.540377
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201035_Feb-13-2024_18:02:24.133232
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201034_Feb-13-2024_18:02:14.686711
drwxr-xr-x 3 root root 4096 Feb 13 18:02 network_config_ifupdown2_1201033_Feb-13-2024_18:02:04.265858
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201032_Feb-13-2024_18:01:53.834823
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201031_Feb-13-2024_18:01:44.385677
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201030_Feb-13-2024_18:01:33.956801
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201029_Feb-13-2024_18:01:24.547927
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201028_Feb-13-2024_18:01:14.160016
drwxr-xr-x 3 root root 4096 Feb 13 18:01 network_config_ifupdown2_1201027_Feb-13-2024_18:01:04.737408
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201026_Feb-13-2024_18:00:54.335252
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201025_Feb-13-2024_18:00:43.938250
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201024_Feb-13-2024_18:00:34.384490
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201023_Feb-13-2024_18:00:23.981543
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201022_Feb-13-2024_18:00:14.584546
drwxr-xr-x 3 root root 4096 Feb 13 18:00 network_config_ifupdown2_1201021_Feb-13-2024_18:00:04.148165
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201020_Feb-13-2024_17:59:54.729523
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201019_Feb-13-2024_17:59:44.330498
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201018_Feb-13-2024_17:59:33.905252
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201017_Feb-13-2024_17:59:24.518908
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201016_Feb-13-2024_17:59:14.180609
drwxr-xr-x 3 root root 4096 Feb 13 17:59 network_config_ifupdown2_1201015_Feb-13-2024_17:59:04.705912
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201014_Feb-13-2024_17:58:54.203846
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201013_Feb-13-2024_17:58:52.443969
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201012_Feb-13-2024_17:58:52.324207
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201011_Feb-13-2024_17:58:44.789491
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201010_Feb-13-2024_17:58:34.395685
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201009_Feb-13-2024_17:58:24.012018
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201008_Feb-13-2024_17:58:14.607480
drwxr-xr-x 3 root root 4096 Feb 13 17:58 network_config_ifupdown2_1201007_Feb-13-2024_17:58:04.202317
drwxr-xr-x 3 root root 4096 Feb 13 17:57 network_config_ifupdown2_1201006_Feb-13-2024_17:57:53.810463
drwxr-xr-x 3 root root 4096 Feb 13 17:57 network_config_ifupdown2_1201005_Feb-13-2024_17:57:44.392538
drwxr-xr-x 17 root root 4096 Feb 13 00:00 ..
root@nodo4-cluster1:/var/log/ifupdown2#


Thank you in advance and have a good evening.

 

[spirit]

do you use sdn ?

if seem that it's generated by ifupfodown2 ifreload when sdn is query configuration status.

(I have same thing of my side)

can you make a bug report on bugzilla.proxmox.com ? I'll try to fix that asap.

 

[f.cuseo]

do you use sdn ?

Yes

if seem that it's generated by ifupfodown2 ifreload when sdn is query configuration status.

(I have same thing of my side)

can you make a bug report on bugzilla.proxmox.com ? I'll try to fix that asap.

Yes, of course, I'll do tomorrow.

 

[f.cuseo]

Yes

Yes, of course, I'll do tomorrow.

Done !

 

[Neobin]

For reference:
https://bugzilla.proxmox.com/show_bug.cgi?id=5242