Symptoms

K3S went down and failed to come up when OMD restarted due to memory corruption.

Impact

When K3S goes down, the cluster is down, which results in service down.

Conditions

This is caused by not having essential flags in the system. The appliance OMD is dependent on the flags inside /var/omd directory.

Workaround

When the cluster goes down due to missing flags, it can be brought back up by clearing the stale flags and tokens. Please contact F5 Support. Follow instructions in https://my.f5.com/manage/s/article/K08061420

Fix Information

1. Logs are in place if the /var/omd/ flags gets deleted or added. 2. Cluster will come up even if it is going to a bad state.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips