IBM Support

PH58002: PIPELINE EXECUTIONS OF MULTIPLE COMPONENTS IN APPLICATION TEMPLATE PROCESS RESULTS IN NPE.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The execution of a pipeline process results in a NPE when the
    pipeline includes an application template process that contains
    an 'install multiple components' step.
    
    Steps to reproduce:
    
    1. Create TWO components "comp1, comp2" and it should have same
    component process name "testp".
    2. Create an Application Template "App-Temp" with Environment
    Template "PT" (based on any Resource Template) and Application
    process "Deploy".
    [In application process "Deploy" add "Install multiple
    components" step and configure the component process "testp"]
    3. Create an Application "App" based on the Application Template
    "App-temp".
    4. Add TWO components into Application "App".
    5. Create a Pipeline with the below code in Application
    pipelines tab.
    [while executing pipeline script choose component versions of
    both the components]
    pipeline script:
    {
        "name": "PT-pipeline",
        "stages": [
            {
                "name": "Deploy to PT",
                "blocks": [
                    {
                        "environment": "PT",
                        "processes": [
                            "Deploy"
                        ]
                    }
                ]
            }
        ]
    }
    
    Error in deployserver.out
    
    java.lang.NullPointerException: null
    atcom.urbancode.ds.subsys.deploy.workflow.activity.MultiComponen
    tEnvironmentIteratorActivity.getAvailableComponents(MultiCompone
    ntEnvironmentIteratorActivity.java:321)
    ~[ucd.jar:7.3.2.0.1158066]
    atcom.urbancode.ds.subsys.deploy.workflow.activity.RunComponentP
    rocessActivity.getAvailableComponents(RunComponentProcessActivit
    y.java:1082) ~[ucd.jar:7.3.2.0.1158066]
    atcom.urbancode.ds.subsys.deploy.config.application_process.Appl
    icationProcess.getComponentsTakingVersions(ApplicationProcess.ja
    va:524) ~[ucd.jar:7.3.2.0.1158066]
    at
    com.urbancode.ds.subsys.deploy.runtime.pipeline.PipelineStateMac
    hine$ApplicationProcessRunner.start(PipelineStateMachine.java:66
    ) ~[ucd.jar:7.3.2.0.1158066]
    at
    com.urbancode.ds.subsys.deploy.runtime.pipeline.PipelineStateMac
    hine.lambda$startProcess$5(PipelineStateMachine.java:486)
    ~[ucd.jar:7.3.2.0.1158066]
    at
    com.urbancode.ds.security.UserLookup.doAsUser(UserLookup.java:22
    1) ~[ucd.jar:7.3.2.0.1158066]
    at
    com.urbancode.ds.security.UserLookup.doAsSystemUser(UserLookup.j
    ava:246) ~[ucd.jar:7.3.2.0.1158066]
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * UrbanCode Deploy Web UI Users                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Pipeline executions of multiple components in Application    *
    * Template Process results in NPE.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fix is provided in IBM UrbanCode Deploy 8.0.0.1              *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH58002

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-11-05

  • Closed date

    2024-02-16

  • Last modified date

    2024-02-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"732","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
16 February 2024