Background
While following the OpenShift deployment guide (deploying_on_openshift.md) to set up hosting on Rahti, I noticed a minor issue regarding the execution order of the steps. For (special) users following the commands strictly top-to-bottom in-order, a step fails because a resource hasn't been created yet.
Description
In Step 4: Trigger first builds, immediately after the oc start-build instructions, the guide tells the user to verify the solvers inside the running pod:
oc exec deployment/desdeo-api -- which bonmin ipopt cbc
However, if the guide is followed chronologically (specially), the API deployment has not actually been created on the cluster yet. That happens in Step 5: Deploy API and web UI.
Running the exec command in Step 4 results in the following error:
Error from server (NotFound): deployments.apps "desdeo-api" not found
Suggested fix is to move the solver verification down to Step 5 or not let special people to read the docs specially (probably more difficult).
Background
While following the OpenShift deployment guide (deploying_on_openshift.md) to set up hosting on Rahti, I noticed a minor issue regarding the execution order of the steps. For (special) users following the commands strictly top-to-bottom in-order, a step fails because a resource hasn't been created yet.
Description
In Step 4: Trigger first builds, immediately after the oc start-build instructions, the guide tells the user to verify the solvers inside the running pod:
oc exec deployment/desdeo-api -- which bonmin ipopt cbcHowever, if the guide is followed chronologically (specially), the API deployment has not actually been created on the cluster yet. That happens in Step 5: Deploy API and web UI.
Running the exec command in Step 4 results in the following error:
Error from server (NotFound): deployments.apps "desdeo-api" not foundSuggested fix is to move the solver verification down to Step 5 or not let special people to read the docs specially (probably more difficult).