Hi!
We just upgraded to 5.12.0.1 and from Debian 9 to Debian10.
We run a k8s cluster with 5 nodes on centos 7.
For some reason one-contextd occasionally restarts the network on my nodes. This leads to a crash of the k8s underlay network (calico).
I can see the following log on one affected node:
Oct 6 14:57:04 node-0 one-contextd: Started for type all to reconfigure
Oct 6 14:57:04 node-0 one-contextd: Processing local scripts
Oct 6 14:57:04 node-0 one-contextd: Script loc-05-grow-rootfs output: NOCHANGE: partition 1 is size 83883999. it cannot be grown
Oct 6 14:57:04 node-0 one-contextd: meta-data=/dev/vda1 isize=512 agcount=21, agsize=524224 blks
Oct 6 14:57:04 node-0 one-contextd: = sectsz=512 attr=2, projid32bit=1
Oct 6 14:57:04 node-0 one-contextd: = crc=1 finobt=0 spinodes=0
Oct 6 14:57:04 node-0 one-contextd: data = bsize=4096 blocks=10485499, imaxpct=25
Oct 6 14:57:04 node-0 one-contextd: = sunit=0 swidth=0 blks
Oct 6 14:57:04 node-0 one-contextd: naming =version 2 bsize=4096 ascii-ci=0 ftype=1
Oct 6 14:57:04 node-0 one-contextd: log =internal bsize=4096 blocks=2560, version=2
Oct 6 14:57:04 node-0 one-contextd: = sectsz=512 sunit=0 blks, lazy-count=1
Oct 6 14:57:04 node-0 one-contextd: realtime =none extsz=4096 blocks=0, rtextents=0
Oct 6 14:57:21 node-0 one-contextd: Script loc-10-network output: RTNETLINK answers: File exists
Oct 6 14:57:21 node-0 one-contextd: Restarting network (via systemctl): [ OK ]
Oct 6 14:57:21 node-0 one-contextd: Script loc-16-gen-env output: cat: /var/run/one-context/mount.lg4M31/token.txt: No such file or directory
Oct 6 14:57:21 node-0 one-contextd: Processing network scripts
Oct 6 14:57:21 node-0 one-contextd: Script net-97-start-script output: Setup already completed
Oct 6 14:57:21 node-0 one-contextd: Done
Why is one-contextd processing these scripts during runtime? Has anybody an idea?
Thanks,
Thomas