Troubleshooting
Problem
User can create Manage workspace custom resource directly either through Maximo application suite core API, or OpenShift console or command-line interface. If user creates the custom resource specifying an empty secondary language list, but later applies other changes to the configuration through the Manage Application Suite Manage configuration UI without modifying any setting that related to the image building, rebuilding of the image might still be triggered.
Symptom
Rebuilding of images is triggered after user modifies the configuration on the Maximo Application Suite's Manage configuration UI even when no settings related to the build are modified. It happens only when there is no secondary language is used, after the initial activation, and when the custom resource is originally created without using the Manage UI.
Cause
If the user specifies on the Manage workspace custom resource, then later uses the Maximo Application Suite's Manage configuration UI to modify other settings, the Manage configuration UI overwrites the secondary language setting by removing the empty list specified. Even though the image generated would be identical with or without the empty secondary language list, the Manage operator incorrectly considers them different and triggers the build process.
secondaryLangs: []
Diagnosing The Problem
User checks the Manage workspace custom resource and see the setting
languages:
baseLang: EN
secondaryLangs: []
is replaced by
languages:
baseLang: EN
Resolving The Problem
The problem can be avoided by not specifying the empty secondary language when manually creating the Manage workspace custom resource.
The availability of newly generated image updates deployment immediately only if the buildTag setting for the deployment is set to 'latest'. An option to better control the redeployment due to build change is to not use "latest" as the buildTag on the Manage workspace custom resource. Reference a specific build number for the deployment keeps the deployment and the images it uses untouched when a new build is done and new images are available. You can update the build tag to the new build tag when you are ready for a redeployment. The build tag is the tag of the image in the image stream.
deployment:
buildTag: '20211006T155802'
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite->MAS Applications->Manage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.2.0"}]
Was this topic helpful?
Document Information
Modified date:
25 October 2021
UID
ibm16508715