Release Automation

Expand all | Collapse all

Release manifest supports only one instance of a process

  • 1.  Release manifest supports only one instance of a process

    Posted 10-30-2014 07:14 PM

    I'm having some difficulties with using the release manifest in the following scenario. I have a deployment plan that repeats a bunch of steps but for different servers in each bunch. e.g. steps A1>B1>C1>A2>B2>C2 where A1 and A2 use the same process but run on different servers (think cluster that needs to stay live during the deployment so we upgrade batches). Same for B1/B2 and C1/C2. The '>' sign implies dependency and A2 cannot run before C1 has completed.

    If the process for the 'A' steps needs a release scope parameter, I can provide only one value in the plan manifest which would hold for both A1 and A2. The release manifest mechanism doesn't seem to support different values for steps that use the same process. I thought of using a collection, but I need only one value in one step (say use X in step A1) and the other in the second step (Y in step A2). Did I misunderstand the feature or is there something missing with the RA logic? Can anyone suggest an alternative way of providing this functionality, preferably using Release scope parameters? (I can implement this logic using a custom xml file and xpath actions, but that's not as cool as the new Release scope feature).



  • 2.  Re: Release manifest supports only one instance of a process

    Posted 11-06-2014 07:00 AM

    When you generate release manifest template from the deployment template you will see that each release parameters will be reside under the relevant release stage and step name so it should  be possible to specify different values per each step even if you use same release parameters.

    e.g

     

    <DeploymentManifest name="DP-1" project="P1" build="1.1">

      <properties></properties>

      <Initialization></Initialization>

      <Deployment>

        <step name="Deploy Group A">

          <Check1>

            <WEB>

              <v2>

                <ReleaseValue templateProperty="false">Value for first step</ReleaseValue>

              </v2>

            </WEB>

          </Check1>

        </step>

        <step name="Deploy Group B">

          <Check1>

            <WEB>

              <v2>

                <ReleaseValue templateProperty="false">Value for second step</ReleaseValue>

              </v2>

            </WEB>

          </Check1>

        </step>

      </Deployment>

      <Post-Deployment></Post-Deployment>

    </DeploymentManifest>

     

    I am not sure what problem you had, but when I tried it I found that the load manifest logic doesn't handle properly situation when same process assign to two steps , in my case the load manifest failed with error message (I opened bug on this problem)

    Until problem solve try use ROC - Update String Parameter action in your init step to set different value per each step.



  • 3.  Re: Release manifest supports only one instance of a process

    Posted 11-06-2014 03:56 PM

    Jacky,

    That's exactly what I meant, only you wrote it clearer.

    I used another solution but AFAIK it's a bug.

    Thanks,

    Elaad



  • 4.  Re: Release manifest supports only one instance of a process

    Broadcom Employee
    Posted 11-26-2014 10:31 AM

    That is correct -- Jacky's example should work, but this is indeed a bug, as we were able to verify. A workaround for the interim would be to give "Deploy Group A" and "Deploy Group B" different revisions, then Jacky's XML example should work.

     

    Jacky, have you logged a defect for this?  I'll be glad to log one if you haven't yet.



  • 5.  Re: Release manifest supports only one instance of a process

    Posted 11-26-2014 10:39 AM

    Yes I opened bug 12889 on this issue

    Thanks

    Jacky



  • 6.  Re: Release manifest supports only one instance of a process

    Posted 11-16-2016 04:40 AM

    Hi,

     

    what is the current status of this above-mentioned bug (12889) - where can I check this?

    We need to keep in release manifest file many processes with the same name but with different values for parameters. 

     

    I prepared manifest e.g.:

     

    <DeploymentManifest name="test_deployment_plan" project="deployment_project" build="1">
      <properties></properties>
      <Initialization></Initialization>
      <Deployment>
        <step name="TEST_DEPLOYMENT">
          <TEST_DEPLOYMENT>
            <Application_Parameters>
              <TEST_RELEASE_PARAM templateProperty="false">1</TEST_RELEASE_PARAM>
            </Application_Parameters>
          </TEST_DEPLOYMENT>
        </step>
         <step name="TEST_DEPLOYMENT">
          <TEST_DEPLOYMENT>
            <Application_Parameters>
              <TEST_RELEASE_PARAM templateProperty="false">2</TEST_RELEASE_PARAM>
            </Application_Parameters>
          </TEST_DEPLOYMENT>
        </step>
      </Deployment>
      <Post-Deployment></Post-Deployment>
    </DeploymentManifest>

     

    After loading this manifest I have got an error message: Failed to load manifest: More than one 'process' tag in one Step

    Do you have any idea how to solve this?

     

    Thank you!



  • 7.  Re: Release manifest supports only one instance of a process

    Broadcom Employee
    Posted 11-16-2016 09:36 AM

    Hi,

    I checked but unable to find the defect/bug id you shared can you give me the case reference for the same. However I am aware that there is a defect been fixed in GA version 6.2.0.3057 and 6.1.0.1109. I think this refer to problem you mentioned above.

     

    DE197415 More than one process tag in one Step error when loading manifest

     

    You can subscribe to our Solution/Patch notification so that you will be notified.

    GA cumulative patch download available @ Download the latest cumulative for all supported RA versions

     

    Let me know if you have any query.

     

    Regards,

    Saurabh



  • 8.  Re: Release manifest supports only one instance of a process

    Posted 11-17-2016 06:02 AM

    Hi,

     

    I do not have any case for this, I just quoted previous post from Jacky Mahadab:

    Yes I opened bug 12889 on this issue

     

    sorry but url to patch you mentioned does not work: ftp://ftp.ca.com/ReleaseAutomation/Fixes/RA_62/RA620cumulativeb3057_40221299429688309.zip - No such file.

     

    And additionally where can I find list of bugs?



  • 9.  Re: Release manifest supports only one instance of a process

    Broadcom Employee
    Posted 11-17-2016 06:47 AM

    Hi,

     It looks like you have some issue accessing the file may be permission related.

     

    It will not be giving you list of bugs, but it will give you list of bugs fixed in particular cumulative GA.

     

    You can follow the Where to download Release Automation official patches?  and it will navigate to specific fix page.

     

    In case if you are looking for related fixes in GA version you can find them here. 

     

    docops.ca.com -> enter product name "Release Automation x.x" under section release notes -> Resolved issue.

     

    For example for 6.2 Resolved Issues - CA Release Automation - 6.2 - CA Technologies Documentation 

     

    Let me know if it helps.

     

    Thanks,

    Saurabh



  • 10.  Re: Release manifest supports only one instance of a process

    Posted 11-17-2016 07:50 AM

    I followed your instruction but still the same, I have got 550 No such file trying to download patch from 

    ftp://ftp.ca.com/ReleaseAutomation/Fixes/RA_62/RA620cumulativeb3057_40221299429688309.zip

     

    I tried to download something else and I am able to get this ftp://ftp.ca.com/pub/releaseautomation/ReleaseAutomation/Fixes/RA_471/RA_471_Cumulative_b360_36929456013782757.zip from FTP, but I cannot download any other patches.

     

    Thank you for your support.



  • 11.  Re: Release manifest supports only one instance of a process

    Broadcom Employee
    Posted 11-17-2016 08:18 AM

    Hi,

     It looks like you are having access problem, please try to reach customer support to resolve access issue. However I am just pasting the fix details from description of 6.2.0.3057 cumulative below for your reference.

     

    src: RA_620_Cumulative_b3057_README

    DESCRIPTION:

    *** “Dear user, please note that the Health Monitoring function will not be available from version 6.3 and above. To monitor the agents and servers please use an application performance management application” ***

    Fixes added with latest cumulative:
    Defect list - DE172266, DE224065, DE130826, DE203197, DE227065, DE207053, DE241406, DE224026, DE197415, DE162780, DE157585
    Cases list - 00421183, 00380684, 00496025, 00319629, 00449448, 00371914, 00480863, 00522250, 00485237, 00435169, 00354366, 00420133, 00285233


    ACTIONS:
    DE207053 - Case 00480863 - FTP Upload and FTP Download actions fail to properly complete while working with zOS FTP servers
    DE157585 - Case 00285233 - Oracle Run SQL File action fails to parse multi-line comment using "/" as delimiter


    ADMINISTRATION:
    DE176028 - DE198300 - Case 00336663 - Case 00331642 - Triggering offline report cause the following error: "ORA-01795: maximum number of expressions in a list is 1000" ..Same errors while generating "Recent Activity" report
    DE198300 - Case 00336663 - Case 00331642- ORA-01795: maximum number of expressions in a list is 1000 - recent activity
    DE198808 - MySQL data migration script for shared component artifacts is not executed
    DE201816 - Case 00451861 - Application Export Fails with error "Error: Runtime Exception during exporting: null"
    DE130956 - Case 00148181 - The "All Groups" filter is missing from the Agent Assignment view preventing the ability to view the list of all the installed agents
    DE227065 - un-Needed verbose error messages are returned to client
    DE162780 - Case 00354366 - Case 00420133 - NES is not automatically reconnected to secondary NAC once fail-over takes place


    EXECUTION:
    DE166025 - Case 00410870 - Cannot use artifact package and assign an environment artifact package within pre-deployment step
    DE130826 - Case 00319629 - Case 00449448 - All servers assigned to environment are participating in a deployment even though explicitly un-selecting the "Assign all servers to environment" checkbox
    DE203197 - Case 00371914 - Potential memory leak on NAC while running deployments


    DESIGN:
    DE200777 - Case 00445344 - Null error when publishing a process that is a copy of process containing parameters of few components (p1 of component A has the concrete value of p2 that is in component B)
    DE136834 - Case 00255724 - The Agent assignment list as appear in the UI does not use the full capable screen
    DE203522 - Duplicate components with assigned artifact types will fail
    DE204833 - Case 00470518 - Case 00411880 - delete process tag generates constraint violation - "The conflict occurred in database "DBNAME", table "process_statistics", column 'process_id'.; SQL [n/a]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: The DELETE statement conflicted with the REFERENCE constraint "FK6AF5DCF3A504013D"."
    DE199758 - Case 00460117 - artifact type was duplicated after importing Shared Component data, causing problems with applications and processes using this artifact. From now on, when trying to import file it will not support creating new artifact type if already exist, but it will use the existing
    DE224065 - Case 00380684 - Case 00496025 - Can not delete flow after some of its actions are removed
    DE241406 - Case 00522250 - The option to override Server Type parameter for the following parameter types is not possible: "Boolean Array", "Number Array", "String Array" and "Collection Element"


    ROC:
    DE186597 - Case 00445444 - The dashboard widget "Total Deployments per Application" does not display results unless selecting all applications
    DE172266 - Case 00421183 - Agent details missing from deployment summary screen when not all assigned servers in server type are selected
    DE224026 - Case 00485237 - Navigating between screens loses previous context/location
    DE197415 - Case 00435169 - Unable to load manifest to a deployment plan when it has same process (with different tags) mapped to multiple steps

     

    Regards,

    Saurabh