Remedy - D2P - Not able to rollback d2p package past 48 hours in 19.02, getting error "Rollback Timeline Validation Failed: Rollback is not allowed 48 hours after successful deployment"

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System Server


    APPLIES TO:

    All Remedy Applications on version 19.02 (9.1.07)



    QUESTION:

    Not able to rollback d2p package past 48 hours in version 19.02 i.e. 9.1.07, getting error "Rollback Timeline Validation Failed: Rollback is not allowed 48 hours after successful deployment".
    Package Status stuck in 'Init Error'.


    ANSWER:

     

    This is an OOB feature introduced in version 19.02
    D2P package has a default ROLLBACK Interval Criteria which is set to 48 hours.

                                

     D2P-Rollback-Timeout-Interval

    Flag indicating timeout for rolling back a deployment package.

    Default value — 48 hours

    Valid values — 48 to 168 hours

      


    Post 48 hours, users won't be able to rollback the package. This Interval can be increased max up-to 7 days i.e. 168 hours.

      

    NOTE: User can increase the Interval only before performing ROLLBACK, else package status will get stuck in 'Init Error' if its over 48 hours.

    Review document for more details:
    https://docs.bmc.com/docs/brid1902/applying-a-deployment-package-841109322.html
    https://docs.bmc.com/docs/ars1902/configuration-settings-c-d-836455160.html

     


    Article Number:

    000168690


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles