Unexpected SIGTERM when using microk8s cli on red hat 8.6

[sean-caruthers]

Summary

After installing snap and microk8s (channel 1.24) on red hat 8.6, microk8s cli commands run with sudo are terminated via SIGINT and exit with status code 143.

What Should Happen Instead?

When running without sudo, commands cli work as expected

Reproduction Steps

1. Install Red hat 8.6 iso on Hyper V or Virtual Box
2. Follow instructions to install snap on red hat (red hat installation of snapd)
3. install microk8s
4. Run the following to view unexpected SIGTERM
   sudo microk8s stop && sudo microk8s start

Introspection Report

inspection-report.tar.gz

[sean-caruthers]

Not sure if anyone is looking into this, but it appears that the command will execute correctly with a greater frequency if the sudo command is run with the preserve environment flag.

sudo -E microk8s stop && sudo -E microk8s start

Also, inserting a sleep between commands increases the odds of success.

sudo -E microk8s stop && sleep 10 && sudo -E microk8s start

It should also be mentioned that the SIGINT issue extends other microk8s cli commands such as

cat my_deployment.yaml | sudo microk8s kubectl apply -f -

Any advice on identifying the determining factor here would be greatly appreciated.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[xbankov]

I have experienced the same issue on AlmaLinux 9.3 with MicroK8s v1.28.7 revision 6541

Command for me were terminating only inside of the bash script, while running them one-by-one there was no problem.

(optional) I confirm that adding sleep increases the chances of success.
Adding -E argument to sudo solved the problem completely.