Bug #114254 /fail-counter: Read-only file system
Submitted: 7 Mar 2024 6:42 Modified: 13 May 2024 13:40
Reporter: Bing Ma (OCA) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Operator Severity:S2 (Serious)
Version: OS:Linux
Assigned to: MySQL Verification Team CPU Architecture:x86

[7 Mar 2024 6:42] Bing Ma 
Description:
in the livenessprobe.sh, when start failed will write to /fail-counter, but this is a read-only file system.

in the pod's shell, try this manually:

bash-4.4$ echo "1" >/fail-counter
bash: /fail-counter: Read-only file system

in the event:

Startup probe failed: mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysql.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysql.sock' exists! /livenessprobe.sh: line 40: /fail-counter: Read-only file system

How to repeat:
just try the code mannually:

echo "1" >/fail-counter
[7 May 2024 7:35] MySQL Verification Team 
Hi,

I apologize but I am not sure what you are reporting. Can you give me a reproducible test case in bit more details? Thanks
[10 May 2024 2:14] Bing Ma 
This problem occurs occasionally. It occurs during startup. I have no way to reproduce this problem stably.