IBM Support

Upgrade of FNCM Deployment Failed

Troubleshooting


Problem

The FNCM deployment failed to upgrade from version 5.5.9 to 5.5.12. After the upgrade, only the CSS pod was running, and the CPE, Navigator, and GraphQL pods were not running. Additionally, the CPE service was created without port 9080 TCP.

Symptom

The log shows that the installed pattern list is empty and the optional components list includes css. 
[0;32m        "installed_pattern_list: ['']",[0m
[0;32m        "optional_components_list: ['css']"[0m
And the CR does not include shared_configuration.sc_deployment_patterns. This is likely because it was originally set to content by default, but the requirement has changed to install only a certain component.
  
    shared_configuration:
      external_tls_certificate_secret: null
      image_pull_secrets:
      - admin.registrykey
      root_ca_secret: fncm-root-ca
      sc_content_initialization: false
      sc_content_verification: false
      sc_deployment_context: FNCM
      sc_deployment_platform: OCP
      sc_deployment_profile_size: small
      sc_deployment_type: production
      sc_fncm_license_model: ICF.PVUNonProd
      sc_image_repository: cp.icr.io
      sc_optional_components: css
      sc_run_as_user: null
      storage_configuration:
        sc_fast_file_storage_classname: thin
        sc_medium_file_storage_classname: thin
        sc_slow_file_storage_classname: thin

Cause

The problem was caused by the FNCM deployment configuration not specifying the sc_deployment_patterns option. This option specifies which components to install when the FNCM deployment is upgraded. In this case, the default value of sc_deployment_patterns was content, which means that only the CSS component was installed.

Environment

Product Version: IBM Cloud Pak for Business Automation 23.0.2 
Is this related to a Cloud Pak container: Yes
Component Area: IBM FileNet Content Manager 
Cloud Platform: VSphere
Red Hat OpenShift Version: RHOCP 4.11 

Resolving The Problem

To resolve this problem, you need to add the following line to the FNCM deployment configuration: 
shared_configuration:
  sc_deployment_patterns: content

You can enable FNCM components like this set:

 content_optional_components:
    cpe: true
    graphql: true
    cmis: false
    css: true
    es: false
    tm: false
    ban: true
 

or add:

ecm_configuration:
  cpe:
  graphql:
  css:
navigator_configuration:
This changes ensure that all of the FNCM components are installed when the deployment is upgraded.

Important:

  • As of 22.0.2-IF005, the application no longer uses port 9080. Please ensure that no custom routes or ingresses are configured to use this port. If you have any existing configurations, please update them to use a different port.
    For more details, please refer to the IBM Support article at: https://www.ibm.com/support/pages/node/6991931.

    See section: Ensure no custom route or ingress is configured using port 9080 from service endpoints 

  • For more information, refer to the IBM APAR article at https://www.ibm.com/support/pages/apar/JR65274

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001iUZAAY","label":"Operate-\u003EFNCM Install\\Upgrade\\Setup"}],"ARM Case Number":"TS015106108","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"23.0.2"}]

Product Synonym

IBM FileNet; Cloud Pak for Business Automation; CP4BA; FileNet P8 Platform; Operator

Document Information

Modified date:
15 January 2024

UID

ibm17107337

Page Feedback