# Problems upgrading rack from 20190111211123

**URL:** <https://community.convox.com/t/problems-upgrading-rack-from-20190111211123/468>\
**Category:** Rack (Version 2)\
**Created:** [March 25, 2019, 5:46am UTC](https://community.convox.com/t/problems-upgrading-rack-from-20190111211123/468 "2019-03-25T05:46:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rob.sharp](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@rob.sharp](https://community.convox.com/u/rob.sharp)\
**Post date:** [March 25, 2019, 5:46am UTC](https://community.convox.com/t/problems-upgrading-rack-from-20190111211123/468/1 "2019-03-25T05:46:20Z")

</div>

Hi,

I have a rack currently on 20190111211123. After upgrading the rack to 20190126182547 (which is the version offered by `convox rack update` without any other params) I am no longer able to deploy an app. The error I see in CF is this:

19-03-25T05:28:33Z system/aws/cfm integration-digivizer-app-ResourceDatabase-KP903E37IO6Z UPDATE\_FAILED Instance CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename integration-digivizer-app-resourcedatabase-kp903e37io6z and update the stack again.  
2019-03-25T05:28:34Z system/aws/cfm integration-digivizer-app-ResourceDatabase-KP903E37IO6Z UPDATE\_ROLLBACK\_IN\_PROGRESS integration-digivizer-app-ResourceDatabase-KP903E37IO6Z The following resource(s) failed to update: [Instance].

Does another step need to take place before deploying the app?

---

<div class="post-metadata">

**Author:** ![julian](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/julian/32/35_2.png) [@julian](https://community.convox.com/u/julian)\
**Post date:** [December 14, 2019, 1:05am UTC](https://community.convox.com/t/problems-upgrading-rack-from-20190111211123/468/2 "2019-12-14T01:05:17Z")

</div>

We’re seeing this too on a database of ours. Did you find a resolution to this?

EDIT: Turns out we had accidentally changed the `encrypted` option of the database, which Cloudfront interpreted as needing to replace the database.
