Automic Continuous Delivery Automation

Expand all | Collapse all

ARA workflow becomes Inactive status even though it has a Deployment Descriptor

  • 1.  ARA workflow becomes Inactive status even though it has a Deployment Descriptor

    Posted 12-21-2017 10:41 AM
    An ARA workflow contains a Deployment Descriptor.  However, it is still getting this error in the Activation report:
    U00007068 Task 'RM.GENERAL.STAGE_BUILD' (Lnr: '0002') has been set to inactive because it cannot be found in the Deployment Descriptor.
    Investigation
    Go to the workflow's History Records.
    (Release Automation tab > Monitoring > highlight the workflow > in the Details pane on the right, click on 'Show History Records')

    av09x3e4d0x8.jpg

    Download the Deployment Descriptor report from the workflow's History Records.

    ezz29on0sijp.png

    Cause
    When another Component ("COM2") is added in to the Workflow ("WF") that's also mapped to the same Target, the new Component ("COM2") becomes inactive because it is using the same Package ("PK") and Profile ("PRO") upon execution.

    Solution
    To correct this issue, a new Package ("PK2") needs to be created whenever there is a new Component ("COM2") because the original Package ("PK") will not have any information about the new Component ("COM2") since the original Package ("PK") only has information about the original Component ("COM").

    cdrqsqn5nts1.jpg



  • 2.  ARA workflow becomes Inactive status even though it has a Deployment Descriptor

    Posted 12-21-2017 02:54 PM
    I believe another solution is if you want to keep the old package (PK) is to use "Assign" option on the Package Details view and relate newly created Component (COM2) so the old package is now aware of it.

    No need to create the new package then.