Bamboo startup fails on pre-bootstrap validation task 51110 with Invalid column name 'id' after Import

XMLWordPrintable

    • Severity 2 - Major

      Summary

      After importing an export zip from an older version of Bamboo (e.g. 5.9.7) into Bamboo 5.14 using a Microsoft SQL Server database and restarting – Bamboo fails to start with java.sql.SQLException: Invalid column name 'id'.

      Note this does not occur if the import is performed as a step from the setup wizard instead of importing into an already running instance via Bamboo Administration > Overview > Import

      Environment

      • Microsoft SQL Server

      Steps to Reproduce

      1. Create an export of a Bamboo instance from an older version of Bamboo e.g. 5.9.7
      2. Install a new Bamboo 5.14.3.1 instance pointed to a Microsoft SQL Server database with the recommended collation Latin1_General_CS_AS.
      3. Bamboo Administration > Overview > Import and import the export zip from Bamboo 5.9.7.
      4. Restart Bamboo once import finishes.

      Expected Results

      Bamboo starts-up successfully.

      Actual Results

      The below exception is thrown in the atlassian-bamboo.log file:

      2017-01-03 11:00:04,912 INFO [localhost-startStop-1] [AbstractUpgradeManager] -----------------------------------------------------------
2017-01-03 11:00:04,912 INFO [localhost-startStop-1] [AbstractUpgradeManager] 51110 : Disallow duplicate trusted keys - remove duplicates
2017-01-03 11:00:04,912 INFO [localhost-startStop-1] [AbstractUpgradeManager] -----------------------------------------------------------
2017-01-03 11:00:04,921 ERROR [localhost-startStop-1] [AbstractUpgradeManager] java.sql.SQLException: Invalid column name 'id'.
java.sql.SQLException: Invalid column name 'id'.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
	at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)
	at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:613)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:572)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:809)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1288)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1241)
	at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:410)
	at com.atlassian.bamboo.upgrade.tasks.v5_11.UpgradeTask51110DisallowDuplicateTrustedKeys.lambda$doUpgrade$1(UpgradeTask51110DisallowDuplicateTrustedKeys.java:46)
	at com.atlassian.bamboo.upgrade.AbstractBootstrapUpgradeTask.withDatabaseConnection(AbstractBootstrapUpgradeTask.java:83)
	at com.atlassian.bamboo.upgrade.tasks.v5_11.UpgradeTask51110DisallowDuplicateTrustedKeys.doUpgrade(UpgradeTask51110DisallowDuplicateTrustedKeys.java:42)

      Workaround

      1. Import the export zip during the installation wizard rather than into a running instance of Bamboo
        or
      2. Do an in-place upgrade of Bamboo instead of export / import method.

              Assignee:
              Marcin Gardias
              Reporter:
              Jeremy Owen
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: