Skip to main content

Step 7: Verify the installation

Run these five checks to prove that the parts users depend on work. They take 2 minutes. Load the variables from openlm-install.env, the file you created from the installation worksheet, and set the address:

source ./openlm-install.env
H="https://$DOMAIN"

Run each check and compare its output with the Expected column:

#CheckCommandExpected
1The home page loadscurl -s -o /dev/null -w '%{http_code}\n' $H/200
2Sign-in is upcurl -s -o /dev/null -w '%{http_code}\n' $H/identity/.well-known/openid-configuration200
3The API refuses anonymous callscurl -s -o /dev/null -w '%{http_code}\n' $H/api/licensemanager/bff/user401
4Agents can registercurl -s -o /dev/null -w '%{http_code}\n' $H/api/agents-hub/announce200
5Nothing is failingkubectl -n $NS get pods --no-headers | grep -vE "Running|Completed"no output

Run the curl commands without -k. If they work only with -k, your certificate isn't trusted, and users' browsers and the OpenLM Platform services reject it too. See TLS certificates.

Fix a failed check​

If a check gives a different answer, find it in the following table:

CheckYou gotMeaning and fix
1000 or a timeoutDNS or ingress isn't reaching the cluster. Repeat step 1.4.
1404The ingress controller answers but has no rule for $DOMAIN. Check global.masterIngress.hostname and ingressClassName in your values.
2404, 502 or 503The identity service isn't ready yet, or is failing. Read its log: kubectl -n $NS logs deploy/openlm-identity
3404The services started before identity was healthy and fell back to a mode without security. Restart them once identity is healthy: kubectl -n $NS rollout restart deployment
3502 or 503The API gateway isn't running or isn't reachable. Repeat the check in step 5.
3503 with IdentityUnavailable in the bodyServices can't reach https://$DOMAIN/identity from inside the cluster. See Networking
Check

All five checks give the expected answer.

If services reject tokens after a first installation

On a first installation, services that start after the identity service has finished its setup sometimes keep rejecting tokens. Restart identity once, after all pods are running:

kubectl -n "$NS" rollout restart deployment/openlm-identity
kubectl -n "$NS" rollout status deployment/openlm-identity

The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.