While testing the history of a pod, I encountered an error after stopping an analysis and then restarting it. The full log (see the bottom) is attached below. It looks like after stopping a pod, the PO gets stuck trying to contact the nginx pod for the stopped analysis and then when a restart is issued, a database conflict occurs. The PO still restarts the analysis but, is unable to get the internal deployment status of the newly deployed nginx container.
logs-from-po-in-flame-node-po-c886fcc8f-ldbvj.log
This also causes the run status for the analysis to get stuck in stopped.
While testing the history of a pod, I encountered an error after stopping an analysis and then restarting it. The full log (see the bottom) is attached below. It looks like after stopping a pod, the PO gets stuck trying to contact the nginx pod for the stopped analysis and then when a restart is issued, a database conflict occurs. The PO still restarts the analysis but, is unable to get the internal deployment status of the newly deployed nginx container.
logs-from-po-in-flame-node-po-c886fcc8f-ldbvj.log
This also causes the run status for the analysis to get stuck in
stopped.