hclleapforum

Open full view…

Upgrading applications - failure

vstanwyck
Thu, 11 Apr 2019 13:43:01 GMT

Twice now when attempting to upgrade an application from our UAT environment to our Production environment, the application gives a "failed to upgrade" message and then the application becomes completely broken. No further changes can be made and the application cannot ever be redeployed. Even trying to "upgrade" with the backed up file of the original does not work. Even if you enter the editor and validate it there, then try to deploy, it gives an "Application failed to validate" error. The first time it happened, we believe it was because there was a SAS upload happening to load data when the upgrade was initiated. That can certainly be avoided in the future. However, the second time, no one was accessing the application and there are no data uploads or processes running in the background. The only thing we noticed is that there was a service calling to an application that was in UAT but not in Prod. However, since we don't deploy the application while upgrading, I am not sure how this could have broken the application. We run about 45 applications in both environm ents and the upgrade from UAT to Prod is how we do new versions/releases, etc. Any advice on what we can do to avoid these breakages in the future?

celine_hall
Thu, 11 Apr 2019 14:19:35 GMT

I would be interested in looking at the logs that were generated when the issue occurred. Please create a support ticket and attach the logs. https://hclsupport.hcltech.com/csm If you have any issues email the logs [email protected]

christopher_dawes
Thu, 11 Apr 2019 15:07:48 GMT

I have seen this before as well, but have not been able to consistently reproduce it. When this happens I believe there is a record that does not get removed from the FREEDOM.APP_DEPLOYER table which will block all future deployment attempts. You must manually remove this record (indexed by the app id) from that table and then you will be able to deploy the app. In my experience the app does upgrade, it is just the browser side that reports an error (and we have not figured out what is causing it). When you upgrade an application the "deploy" is inherent. If the application is referencing a service that does not exist then that would certainly cause an error.

vstanwyck
Tue, 19 May 2020 14:25:31 GMT

Digging up the past over here! I'm encountering a similar issue again. I just tried to upgrade an application this morning and instead of the "Deployment failed" message, this time I get an "Upgrade failed" message but then it shows the new title anyway (we include a basic version number in our apps). I have a backed up version of the nitro file, which I can import and upgrade with the new version without a problem. But the original one with the data continues throwing this error, even when I try to "upgrade" back to the backed up version. I am concerned that I will not be able to make any changes to this app going forward now since the last time this happened and I entered the editor, it shows validation passes but then throws a deploy error. Unfortunately, I do not have access to the logs as I am not the admin for our Leap. Any thoughts? [Upgrade error](//muut.com/u/hclleapforum/s1/:hclleapforum:8InS:upgradeerror.png.jpg)