Update from 6.2.1 to 6.2.3 failed

aws-solutions / serverless-image-handler

A solution to dynamically handle images on the fly, utilizing SharpJS

Apache License 2.0

1.33k stars 536 forks source link

Update from 6.2.1 to 6.2.3 failed #514

Closed karensg closed 1 year ago

karensg commented 1 year ago

Describe the bug Cannot update to the latest 6.2.3 version.

See screenshot below. Getting the following error: Resource handler returned message: "Application name update feature has been deprecated. (Service: ServiceCatalogAppRegistry, Status Code: 400, Request ID: 1ffef977-7ab7-4e1e-8960-ed169c2a6388)" (RequestToken: 44332275-5136-c845-dddc-b87c8139ff38, HandlerErrorCode: InvalidRequest)

To Reproduce Install 6.2.1 and try to update to 6.2.3

Expected behavior Update works

Please complete the following information about the solution:

[x] Version: 6.2.1
[x] Region: eu-central-1
[x] Was the solution modified from the version published on this repository? No
[x] If the answer to the previous question was yes, are the changes available on GitHub?
[x] Have you checked your service quotas for the sevices this solution uses?
[x] Were there any errors in the CloudWatch Logs?

Screenshots

kamyarz-aws commented 1 year ago

@karensg Hi,

Did you change your stack name when updating ?!

karensg commented 1 year ago

Hi,

There is no question to change the name during the update. I did not change any parameters, neither did I change any of the underlying resources manually.

I had 3 other installations in other regions (all 6.x versions). Two of them updated without a problem, 1 had the same issue (region Cape Town). That one was used only by 1 project, so I just deleted it and recreated it. But the one in Frankfurt is used by too many projects to create it from scratch, would be great to understand what is the actual problem.

Names of existing resources: Application: serverless-image-handler-eu-central-1-390326922282 <-- this name looks wrong? Attribute Group: A30-AppRegistry-ServerlessImageHandlerNew6

karensg commented 1 year ago

I changed the template to the hardcoded name in the template and the update worked. Very strange how this drift could have taken place in two installations.

emrealparslan93 commented 1 year ago

@karensg, I have the exact same issue. Can you tell me where to change in template?

emrealparslan93 commented 1 year ago

@karensg I got it. For those who are looking for the solution:

Open AWS Console and go to Service Catalog > AppRegistry > Applications. Copy your stack's application name. (ex: serverless-image-handler-us-east-2-1234567890000)
Open serverless-image-handler.template in an editor.
Find AppRegistry968496A3 in line 2345.
Change Name value from "Name": { "Fn::Join": [ "-", [ "AppRegistry", { "Ref": "AWS::StackName" }, { "Ref": "AWS::Region" }, { "Ref": "AWS::AccountId" } ] ] }, to "Name": "serverless-image-handler-us-east-2-1234567890000",

Thanks to Karens for saving my time!

jatinvmehta commented 11 months ago

Will this issue be fixed in next version ?

albanx commented 1 month ago

This issue has not been solved in version 6.3.1