Physical restore gets error state when updateStrategy is SmartUpdate
General
Escalation
General
Escalation
Description
Hi,
The physical restore finishes with error state if SmartUpdate strategy is set for cluster. There is panic in operator log after Deleting statefulset during restore. Sometimes cluster eventually starts and gets ready state, sometimes cluster hangs in initializing state with sts num of containers 1.
STR:
Add backup.storage to default cr.
Make physical backup:
Restore from this backup:
Expected result: Restore finishes with ready state
Actual result: restore getserror state. Operator panics. psmdb sometimes recovers and gets ready state and all the pods are up and running, sometimes stays in initializing with 1 container in pods.
Hi,
The physical restore finishes with
error
state ifSmartUpdate
strategy is set for cluster. There ispanic
in operator log afterDeleting statefulset
during restore. Sometimes cluster eventually starts and gets ready state, sometimes cluster hangs in initializing state with sts num of containers 1.STR:
Add
backup.storage
to default cr.Make physical backup:
Restore from this backup:
Expected result: Restore finishes with
ready
stateActual result: restore gets
error
state. Operator panics.psmdb
sometimes recovers and getsready
state and all the pods are up and running, sometimes stays ininitializing
with 1 container in pods.Example of
psmdb
ininitializing
:Attaching full logs