IBM Support

Build process fails with error “Insufficient ephemeral-storage” when deploying Manage on Maximo Application Suite

Troubleshooting


Problem

When installing MAS Manage within an Openshift 4.5 on IBM Cloud (ROKS) environment, the build process fails to find available resources to allocate the ephemeral storage request, even if the cluster has ample resources available.

Symptom

After deploying Manage on MAS, the build process hangs for an extended period of time, eventually failing with an error message similar to the following in the Openshift pod record:
“Warning  FailedScheduling  <unknown>  default-scheduler  0/3 nodes are available: 3 Insufficient ephemeral-storage”.  

Environment

Manage on Maximo Application Suite,
IBM Cloud (ROKS) OpenShift 4.5.

Diagnosing The Problem

After deploying Manage on Maximo Application Suite, verify that the pod named "admin-build-config-1-build" stays in Pending state for an extended period of time, and in the Events tab an error similar to is logged:
 
“Warning  FailedScheduling  <unknown>  default-scheduler  0/3 nodes are available: 3 Insufficient ephemeral-storage”.  

Resolving The Problem

By editing the ManageWorkspace Custom Resource, the user can alter the size of the ephemeral-storage allocation request to be 0Gi as a way to circumvent this issue.

Procedure

1. On the Openshift console, navigate to the ManageWorkspace Custom Resource. Under Administration, Custom Resource Definitions, filter for ManageWorkspace.

2. Under the Instances tab, look for the record associated with the user installation. The record name should follow the naming convention of {instanceId}-{workspaceId}.

3. Under the YAML tab, edit or insert the following section for the ephemeral-storage request to be explicitly 0Gi (required change in bold):

apiVersion: apps.mas.ibm.com/v1
kind: ManageWorkspace
metadata:
  namespace: mas-vri-manage
  labels:
    mas.ibm.com/applicationId: manage
    mas.ibm.com/instanceId: vri
    mas.ibm.com/workspaceId: vri1ws
spec:
  bindings:
    jdbc: workspace-application
  components:
    base:
      version: latest
  settings:
    db:
      dbSchema: maximo
      encryptionSecret: vri1ws-manage-db.encryptionsecret
      maxinst:
        bypassUpgradeVersionCheck: false
        db2Vargraphic: true
        demodata: false
        indexSpace: maxindex
        tableSpace: maxdata
    deployment:
      buildTag: latest
      ephemeralStorage:
        adminBuild: 0Gi
        serverBundleBuild: 0Gi

      importedCerts: []
      mode: up
      persistentVolumes: []
      serverBundles:
        - bundleType: all
          isDefault: true
          isUserSyncTarget: true
          name: all
          replica: 1
          routeSubDomain: all
      serverTimezone: GMT
    languages:
      baseLang: EN


4. Save the YAML.

5. Wait for the operator to reconcile.

Document Location

Worldwide

[{"Type":"SW","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->Manage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0"}]

Document Information

Modified date:
18 May 2021

UID

ibm16452425