Comment 1 for bug 2051915

Using a quick and dirty 'kubectl edit statefulset' on the mysql config to bump the limit from 2g to 4g clears the OOM restarts with exit code 137's, however general instability continues

e.g:-
openstack cinder-mysql-0 2/2 Running 0 32m
openstack placement-mysql-0 2/2 Running 2 (6m50s ago) 32m
openstack horizon-mysql-0 2/2 Running 1 (6m49s ago) 31m
openstack nova-mysql-0 2/2 Running 1 (2m1s ago) 32m
openstack neutron-mysql-0 2/2 Running 2 (118s ago) 30m
openstack keystone-mysql-0 2/2 Running 1 (118s ago) 35m
openstack glance-mysql-0 2/2 Running 2 (117s ago) 31m

Querying placement-mysql-0 shows an exist code of 0 and 2 restarts, so still something else triggering this.

    State: Running
      Started: Fri, 08 Feb 2024 18:51:13 +0000
    Last State: Terminated
      Reason: Completed
      Exit Code: 0
      Started: Fri, 08 Feb 2024 18:45:05 +0000
      Finished: Fri, 08 Feb 2024 18:51:13 +0000
    Ready: True
    Restart Count: 2
    Limits:
      memory: 4Gi
    Requests:
      memory: 4Gi