IBM Support

IV36408: DEPLOYMENT REQUEST FOR 2 SERVERS FAILS WITH WORKFLOW PMRDPRBSYP FAILED WHILE REQUEST FOR 1 SERVER AT A TIME SUCCEEDS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DEFINITION:
    
    Execute a request for a deployment of 2 servers (or more), very
    simple request (1 vCPU, 4 GB RAM, 8 GB swap, 35 GB HDISK).
    After pressing the finish button, in a while, the service
    request goes into the status 'New', then after a while goes into
    the 'In-progress' status, then directly into
    failed without starting any TPM workflow and showing the
    following info in the service request log:
    
    
    
    CTJZH8319E - Service request 20077 was closed due to
    errors during processing. Project eeddcc2 may not be
    operational.
    CTJZH8317I - BlueCloud processing has finished for
    project /cloud/rest/projects/xxxx/ with failures returning
    status 3.
    CTJZH8330E - The cloud management subsystem was unable
    to create any of the requested servers.
    CTJZH3405E - Workflow PMRDPRBSYP failed
    CTJZH0074I - Cancel actual and all remaining tasks of
    the management plan.
    CTJZH3411I - Management Plan Create Project completed
    
    
    No problem asking for 1 server at a time, deployment of the same
    exact servers but one at a time works without issues.
    
    STEPS TO REPRODUCE:
    Request to create a project with more than one server.
    
    CURRENT ERROUNEOUS RESULTS: request for multiple servers will
    fail with above mentioned errors. Request for a single server at
    a time succeeds.
    
    EXPECTED RESULTS: request for multiple servers should complete
    successfully.
    
    ENV:
    It is an environment including a TSAM server + a DB2 server
    (both SLES 10 Sp3), installed via ISDM at level 7.2.2 then
    upgraded to 7.2.2.1
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Tivoli Service Automation Manager
    7.2.2.1
    ****************************************************************
    * PROBLEM DESCRIPTION:
    Service request fails asking for more than 1 server
    ****************************************************************
    * RECOMMENDATION:
    A temporary workaround is available through an updated workflow
    "Resource_Master". Contact L2 to get this workflow and
    instructions how to apply it.
    
    For permanent resolution apply Tivoli Service Automation Manager
    7.2.4 Fixpack 1 when available.
    

Problem conclusion

  • The DCM query in the for each loop gives an error that "An array
    value cannot be assigned to a single valuable variable". Having
    this statement written separately solves this error from
    occurring. This APAR solves the problem - after starting the
    product the problem will not occur anymore, there are no
    specific additional actions required for the customer.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | fix pack | 7.2.4-TIV-TSAM-FP0001
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV36408

  • Reported component name

    TSAM (& INSTALL

  • Reported component ID

    5724W7800

  • Reported release

    722

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-06

  • Closed date

    2013-02-12

  • Last modified date

    2013-02-12

  • 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

    TSAM (& INSTALL

  • Fixed component ID

    5724W7800

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFG5E","label":"Tivoli Service Automation Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"722"}]

Document Information

Modified date:
09 November 2020