'Permission denied' error when it tries to kill k3s PID

[billimek]

The system upgrade controller plan ran on a k3s node and while it successfully upgraded the k3s binary, it failed to kill the k3s PID.

This was on an ubuntu 20.04 based OS with k3s installed on-top.

➜ k -n k3os-system logs -f apply-k3s-agent-on-k3s-pi4-c-with-5822e4c612633d6f88d07e5-mtqxt -c prepare
+ upgrade
+ get_k3s_process_info
+ ps -ef
+ grep -E 'k3s .*(server|agent)'
+ grep -E -v '(init|grep|channelserver)'
+ awk '{print $1}'
+ K3S_PID=1246
+ '[' -z 1246 ]
+ info 'K3S binary is running with pid 1246'
+ echo '[INFO] ' 'K3S binary is running with pid 1246'
[INFO]  K3S binary is running with pid 1246
+ cat /host/proc/1246/cmdline
+ awk '{print $1}'
+ head -n 1
+ K3S_BIN_PATH=/usr/local/bin/k3s
+ '[' 1246 '==' 1 ]
+ '[' -z /usr/local/bin/k3s ]
+ return
+ replace_binary
+ NEW_BINARY=/opt/k3s
+ FULL_BIN_PATH=/host/usr/local/bin/k3s
+ '[' '!' -f /opt/k3s ]
+ info 'Comparing old and new binaries'
+ echo '[INFO] ' 'Comparing old and new binaries'
[INFO]  Comparing old and new binaries
+ sha256sum /opt/k3s /host/usr/local/bin/k3s
+ cut '-d ' -f1
+ uniq
+ wc -l
+ BIN_COUNT=2
+ '[' 2 '==' 1 ]
+ info 'Deploying new k3s binary to /usr/local/bin/k3s'
+ echo '[INFO] ' 'Deploying new k3s binary to /usr/local/bin/k3s'
+ cp /opt/k3s /host/usr/local/bin/k3s
[INFO]  Deploying new k3s binary to /usr/local/bin/k3s
+ info 'K3s binary has been replaced successfully'
+ echo '[INFO] ' 'K3s binary has been replaced successfully'
+ return
+ kill_k3s_process
+ kill -SIGTERM 1246
[INFO]  K3s binary has been replaced successfully
sh: can't kill pid 1246: Permission denied

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.