Troubleshooting
Problem
After upgrading IBM Maximo Application Suite (MAS) to version 9.2.x, users might be unable to access the MAS home page (Navigator). The MAS home route can become incorrectly configured when the Suite Custom Resource (CR) contains the setting:
spec:
settings:
routingMode: path
Symptom
After upgrading to MAS 9.2, one or more of the following symptoms might be observed:
- The MAS Navigator (home page) is inaccessible.
- The MAS landing page URL returns errors or cannot be resolved.
- Application URLs continue redirecting to the previous MAS home URL, but the route no longer exists in OpenShift.
- The Navigator route is recreated using a path-based routing format that is inconsistent with the existing MAS deployment configuration.
- Other MAS application routes may continue functioning normally while only the Navigator route is affected.
Cause
Prior to MAS 9.2, the spec.settings.routingMode setting was not actively used by MAS runtime routing behaviour. As a result, environments could operate normally even when routingMode was configured as path.
With MAS 9.2, the routingMode setting is evaluated when MAS routes are created and managed. During the upgrade process, environments containing:
spec:
settings:
routingMode: path
can have the Navigator route recreated using path-based routing. However, application redirects may continue referencing the original URL structure, resulting in an inaccessible MAS home page and broken routing behaviour.
Certain versions of the MAS DevOps Ansible Collection (29.11.0 through 34.0.0) set the default value of spec.settings.routingMode to path. In addition, MAS CLI releases that bundled these affected Ansible Collection versions—including versions 15.14.0 through 18.2.0—may have updated the Suite custom resource (CR) with routingMode configured as path during MAS 9.1 installation or upgrade activities.
Environment
9.1
Diagnosing The Problem
1.Verify whether the Suite CR contains the following setting:
oc get suite <suite-name> -o yamlLook for:
spec:
settings:
routingMode: path2.Review the MAS Navigator route and compare it with the route configuration that existed before the upgrade.
3.If users cannot access the MAS home page after upgrading to MAS 9.2, examine the OpenShift routes and verify whether the Navigator route was recreated with a path-based configuration.
4.Determine whether the environment was originally installed or updated using affected MAS CLI or MAS DevOps Collection versions that defaulted the routing mode to path.
5.If the Suite CR contains routingMode: path and the Navigator route became inaccessible immediately after the MAS 9.2 upgrade, this technote likely applies.
Resolving The Problem
To restore normal routing behavior:
1.Edit the Suite CR and change the routing mode from path to subdomain.
Example:
spec:
settings:
routingMode: subdomain2.Save and apply the updated configuration.
3.Restore or recreate the Navigator route using the original route URL format that existed prior to the upgrade.
4.Verify that the Navigator route is reachable.
Note: To avoid potential route configuration problems after the upgrade, ensure that spec.settings.routingMode is set to subdomain before upgrading to MAS 9.2.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
22 July 2026
UID
ibm17280506