JIRA Agile is Unavailable due to the GhUpgradeTask032 failed

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

The following appears in the atlassian-jira.log and atlassian-greenhopper.log:

2013-03-21 07:45:07,751 http-apr-8080-exec-15 ERROR vkharisma@awesome.com 465x1147x1 12tabsn 172.21.140.111 /rest/plugins/1.0/com.pyxis.greenhopper.jira-key [sal.core.upgrade.DefaultPluginUpgradeManager] Upgrade error: Unexpected exception caught during plugin upgrade: java.lang.NullPointerException
	at com.atlassian.crowd.embedded.impl.IdentifierUtils.toLowerCase(IdentifierUtils.java:42)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032DaoImpl.processCardColor(GhUpgradeTask032DaoImpl.java:67)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032DaoImpl.access$100(GhUpgradeTask032DaoImpl.java:15)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032DaoImpl$2.onRowRead(GhUpgradeTask032DaoImpl.java:55)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032DaoImpl$2.onRowRead(GhUpgradeTask032DaoImpl.java:51)
	at net.java.ao.EntityManager.stream(EntityManager.java:924)
...

OR

2013-08-17 15:04:57,398 localhost-startStop-1 ERROR      [sal.core.upgrade.PluginUpgrader] Upgrade failed: null
java.lang.NullPointerException
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032.upgradeClassicContextAssignees(GhUpgradeTask032.java:174)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032.updateUserPreferencesAndSettings(GhUpgradeTask032.java:162)
	at com.atlassian.greenhopper.upgrade.GhUpgradeTask032.performUpgrade(GhUpgradeTask032.java:83)
	at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:62)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
...

Cause

There are two known causes for this:

  • The upgrade task failed to convert the mix case username hence returning NULL value in database. This is basically a bug that being tracked in GHS-8325 - Getting issue details... STATUS
  • A bug for this is raised under  GHS-9697 - Getting issue details... STATUS

Workaround

  1. Run the following query to check for NULL values in the AO_60DB71_CARDCOLOR table

    SELECT ID FROM "AO_60DB71_CARDCOLOR" WHERE "VAL" is NULL;
  2. Remove the row that contains the NULL value using the following query:

    DELETE "AO_60DB71_CARDCOLOR" WHERE ID IN (<ID RETURN FROM THE SELECT QUERY>);
  3. Restart JIRA.

If this does not resolve the problem, please try the workaround in Jira throws error user exists but has no unique key mapping on login as it fixes the bug tracked under GHS-9697 - Getting issue details... STATUS

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.