Synopsysctl stop requires you to scale postgres pod before running the start command

[shrewbies]

What happened: When running ./synopsysctl start blackduck hub-eks -n hub-eks the Black Duck Pods will not come back up.

What you expected to happen: I expect that all the pods will start when running the start command is issued after the stop command.

How to reproduce it (as minimally and precisely as possible): Run the stop command on a running Black Duck server that is using synopsysctl and then run the start command and it will hang.

Environment (please complete the following information):

• Kubernetes version: Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"darwin/amd64"}
  Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T18:46:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

• Cloud provider or hardware configuration: EKS

• OS (e.g: cat /etc/os-release): Amazon Linux 2

How to resolve:

Manually run the following:

kubectl -n scale deployment <deployment_name> -blackduck-postgres --replicas=1

Expected that this is handled with the stop/start commands.