An install failed, or never started
The status became “Install failed”, or pressing Install gave a dependency error. inlorus states separately which step failed and which ones did not run because of it.
For: Tenant administrator, Builder, Operator
What happened
You pressed Install. Either the status became “Install failed” and a line such as “The validate-config step failed; the 5 steps after it did not run because of it.” appeared on screen, or the install never started and it said NO_DEPENDENCY_SET: … has declared no dependency set ….
Why it happens
When a step fails, the steps that depend on it never run. NO_DEPENDENCY_SET means the person who built the capability did not declare what the version needs (or that it needs nothing): such a version can be published but cannot be installed.
What inlorus does
- It shows the failed step with its own error code.
- It shows steps that never ran because of a failed step not as “failed” but as “did not run because a step failed”, so you don't try to fix the wrong step.
- It stops the install of a version with undeclared dependencies before planning it.
What you do
- In the Install steps section, read the failed step and its error code.
- If the error is
NO_DEPENDENCY_SET, tell the builder who published the capability: in the studio of the capability's owner (Capability Studio for a platform capability, Account Studio for an account capability), Declare no dependencies is needed next to the version. - Once the cause is fixed, press Install again on the Capabilities screen.
How to keep it from happening again
- As a builder, declare a version's dependencies before publishing it; a version marked “dependencies not declared — cannot be installed” in the list cannot be installed.