A capability's install is stuck on “Installing”
Install now runs the install right through to the end; the screen returns “Installed” or “Install failed” with its reason. An install stuck on “Installing” was interrupted, and the daily scheduled job continues it from where it stopped.
For: Tenant administrator, Operator
What happened
On the Capabilities screen a capability's row shows “Installing” and the Install button is not shown. In the Install steps section some steps sit at “queued” or “running”.
Why it happens
When you press Install, inlorus runs the steps in order right away and the screen does not return until the install is done; normally “Installing” never appears. If it does, the process running the install was interrupted (for example by a deployment or a timeout), or the install was started before this change: previously the steps were never run and every install stayed on “Installing”.
What inlorus does
- It does not show an interrupted install as failed; pending and failed are different things.
- It continues the interrupted install from the step it stopped at in the daily scheduled job; the install either becomes “Installed” or becomes “Install failed”, stating which step failed and why.
- It does not let two processes run an install at the same time; a new install before the previous one finishes is refused with
RUN_IN_FLIGHT.
What you do
- In the Install steps section, check which step it stopped at.
- If the status has not changed within a day, pass the capability's name and the step it stopped at to the platform operations team.
- If the status became “Install failed”, read the failed step's error code and reason, fix the cause and press Install again.
How to keep it from happening again
- After pressing Install, wait for the screen to return; don't press it a second time for the same capability.