network-orchestration-for-aws-transit-gateway icon indicating copy to clipboard operation
network-orchestration-for-aws-transit-gateway copied to clipboard

Published 20 hours ago • verified publisher icon aws-solutions

Updated tags in v2.0.0 causes replacement of Transit Gateway and its route tables

Open david-prado opened this issue 4 years ago • 5 comments

Upgrading STNO from v1.0.0 to v2.0.0 causes a replacement of Transit Gateway and its route tables due to changes in the tags, as documented here

This also caused duplicate Transit Gateway and Route tables due to the Retain policy.

david-prado avatar Sep 25 '20 23:09 david-prado

@david-prado Thanks for bringing this to our attention. We have not seen this behavior in our testing. It would be great if you could open a support case via the console to allow us to obtain and review the logs. Thanks.

groverlalit avatar Sep 28 '20 18:09 groverlalit

I have opened a support case with instructions to contact you so you can look at the logs. Thanks

david-prado avatar Sep 28 '20 20:09 david-prado

@david-prado Was your issue resolved?

maykays avatar Nov 03 '20 21:11 maykays

I am facing a similar issue in our customer environment which is preventing us from promoting v2.0.0 to production. Anyone found a workaround for this? @david-prado

kbosco avatar Mar 13 '21 23:03 kbosco

I am facing a similar issue in our customer environment which is preventing us from promoting v2.0.0 to production. Anyone found a workaround for this? @david-prado

We just updated the v2.0.0 template with same tags as previous version. That prevents the replacement

david-prado avatar Apr 16 '21 02:04 david-prado

This issue has been resolved. CFN now supports name replacement as an update without interruption.

groverlalit avatar Mar 21 '23 21:03 groverlalit