bamboo exception occurred inside setter of com.atlassian.bamboo.plan.AbstractPlan when trying to upgrade

[William Wells]

Recently our SA's increased the memory allocation on the Bamboo instance. When try attempted to bring Bamboo back up (v4.0), Bamboo no longer worked and we started getting errors stating that it could not upgrade to the current version from a release prior to v2.7.4. While I didn't know why memory increase would make it look as though our previous upgrade had never been done, we attempted to perform the incremental upgrade to v3.2.2, then we would attempt the v4.0 upgrade again.

Now while attempting to upgrade to the v3.2.2, we are receiving the error seen in the question I am submitting. It looks as though it is going through the upgrade just fine until it gets to upgrade task 2022. This is our production instance of Bamboo and our automated builds are at a stand still until we can get this working again.

[William Wells · Accepted solution]

Unfortunately, I was unable to resolve the initial problem where it seems to have identified version differences. However, and thankfully, we have a pretty solid backup process and were able to restore our database and the Bamboo Home directory from image snapshots on the server from the day prior to the issue. We were able to maintain the memory allocation increase and Bamboo was able to start up and run successful builds once again.

As a side note, I am extremely disappointed with Atlassian tech support. The methodology that is currently in place is lacking. We pay for maintenance in order to contact someone in case there's an issue we cannot resolve. I attempted to contact support via phone and the automated message states that you can use it for critical issues for Crowd, Confluence, or JIRA. If you have more tools, provide critical phone support for them as well. Try to realize that providing log files or attempting screen shares is not acceptable for all of your customers. In our case, it is near impossible to get any kind authorization to provide these actions due to our customer policies. I'm sure there are quite a few others out there that have the same situation.