Description:
operator restart, results in mongodb restart
Steps to Reproduce:
If there is OOM on percona operator, for some reason the replicaset also restarts
Version:
1.15
psmdb-operator:
Container ID: containerd://c1b2fc542653657b6481c17d4598c0b6a034d75be2109b4cbd96ecf1edac24e5
Image: nexus-docker-reader.com/percona/percona-server-mongodb-operator:1.15.0
Image ID: nexus-docker-reader.com/percona/percona-server-mongodb-operator@sha256:d8a5b33db1938d42769cb5a87d34a128332a2d0302eaa6d7c860e7c4667ea3b6
Ports: 8080/TCP, 8081/TCP
Host Ports: 0/TCP, 0/TCP
Command:
percona-server-mongodb-operator
State: Running
Started: Wed, 17 Apr 2024 21:52:23 -0400
Last State: Terminated
Reason: OOMKilled
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 42m (x11 over 4d23h) kubelet Container image "nexus-docker-reader.com/percona/percona-server-mongodb-operator:1.15.0" already present on machine
Normal Created 42m (x12 over 5d8h) kubelet Created container psmdb-operator
Normal Started 42m (x12 over 5d8h) kubelet Started container psmdb-operator
$ k get pods -n dbe
NAME READY STATUS RESTARTS AGE
nova-mgdb-rs0-0 3/3 Running 0 17m
nova-mgdb-rs0-1 3/3 Running 0 39m
nova-mgdb-rs0-2 3/3 Running 0 41m