Another workaround: https://confluence.atlassian.com/display/GHKB/License+is+for+an+older+version+and+maintenance+has+expired+message+when+license+expires

This problem has not yet been resolved for me. I have a support case open and support folks are trying to help. My license had expired at GH 5.9.1, but after some fixes came, I upgraded UPM to 2.1.1 and GH to 5.9.3 (as per my current understanding I shouldn't have upgraded GH), later then rolled back to 5.9.1 but still no luck. Have tried clearing cache, removing work directory and all kinds of sequences. If anyone can suggest a fix, that would be great.

As Jason pointed out in his linked issue, I skipped a step in the fix process I described this morning.

Right, I should have added an extra step to my comment on GHS-4887. After updating to UPM 2.1.1+ (either 2.1.1 or 2.1.2 would contain the fix), your GreenHopper may still report itself as having a maintenance-expired license. This is because plugin licenses get cached and are only recomputed once a day.

To refresh your cached GreenHopper license you can do the following:

1. Copy your GreenHopper license in your UPM (Plugin Manager)
2. Remove the GreenHopper license in your UPM such that it says it is unlicensed
3. Paste (re-enter) the GreenHopper license and submit it.

So to resolve this problem, the complete solution should be:

1. Update to UPM 2.1.1+.
2. Do not update to a newer version of GreenHopper, as this may be build after your license's maintenance expiration date.
3. Clear your cached GreenHopper license if needed.

Cheers,
Ben

I posted a workaround for my issue in the linked jira issue.

Jason, Kevin,

To fix the problem, please update your Universal Plugin Manager (UPM) to 2.1.1 and do not update your GreenHopper version. You can update to UPM 2.1.1 from with your JIRA's UPM (Plugin Manager).

UPM 2.1.1 fixes the bug where GreenHopper's maintenance expiration is erroneously reported. However, if you update to a newer version of both the Plugin Manager and GreenHopper then it is possible that your new GreenHopper version will be built after your license maintenance expiration date, which will correctly be reported as a maintenance expiration error.

If this does not resolve your issue, please file a ticket at https://support.atlassian.com.

Cheers,
Ben

I have the same issue. Our maintenance expired yesterday and now get the same screen as reported here.

Sounds like it would be worth raising this with https://support.atlassian.com Jason, they can help you work out what's going on

Could anyone help me out with the versions i would need to fix this bug?
As was the case with Vitaliy Rybin, our licence expired yesterday (12.04.12) at which point we were already running with Greenhopper 5.9.3, Jira 5.0.2 and UPM 2.1.1
We had just upgraded everything on the 02.04.2012, so all the versions are current, however Greenhopper suddenly (12/Apr/12 4:00 PM to be exact) will only redirect us to the plugin manager.
in the log is see "com.atlassian.extras.common.LicenseException: You cannot update to GreenHopper version 5.9.3. Updates are no longer available." --> it was already at version 5.9.3
any ideas?

UPM 2.1.1 has been released with a fix for this issue. You can update to UPM 2.1.1 from within your JIRA's UPM (Plugin Manager).

This will be fixed as part of the new UPM release. There is no more GH work that needs to be done on this issue. The relevant support cases will be updated on how they can auto upgrade to the new UPM

Hello. I have the same Bug. And realy wait for new version of UPM with this fix.

GH and Jira I can't update too because of end maintenance period in license.

@Vishal we are looking to build a new version of UPM to fix this problem. We think that this will fix the problem for existing plugins.

We have fixed the underlying problem in the next version of GH which is due in a week or two but this doesnt help you since your expired maintenance does not allow you the new version either way.

Hey guys, thanks for nailing the problem down. I am the user who faced this issue. The sequence of events was - upgrade JIRA and then upgrade GH right after; the process was completed by 22:15 on Mar 21st. After the upgrade both were working fine, but after Mar 22nd, we started seeing this issue. Let me know if you want any further info or want me to try out something.

OK, I figured out the problem. There are a couple things wrong here.

Atlassian-Build-Date is the value UPM uses to enforce maintenance expiration. It is added to any plugin manifest produced with AMPS version 3.7+. GreenHopper currently uses 3.6 which is why you don't have that entry in your manifest. Resolving GHS-4895 and then having this user bump to that version (5.9.4?) of GreenHopper will resolve the issue for them.

Since we couldn't add the Atlassian-Build-Date entry to released versions of GreenHopper, we hard-coded those build dates into UPM. However, this list only goes as far as 5.9.0-beta2 (as we thought future GreenHopper versions would have the entry), and this user is using 5.9.1 thus the problem. I've filed UPM-1905 so that we can update the hard-coded list to handle 5.9.0-5.9.3.

Brad, while fixing GHS-4895, do you mind commenting on UPM-1905 with the build dates for those four versions? Thanks

Also we didnt bundle GH in JIRA 5.0 or later and we dont depend on its build data that I know of.

I get March 12th for the build date and not March 22. This is in BuildPropertiesImpl class and not the manifest.

We dont use the manifest internally to do maintenance. I am a bit confused here and still trying to get to the bottom of this problem.

What is Atlassian-Build-Date. I cant find it any where in the jar vide a recursive grep??

Thanks Ben. Like I said I havent investigated it yet so thanks for your prompt reply. I will get into the details very soon.

Actually, from looking at the attached screenshot, I'd say that the UPM 2 licensing is working exactly as it is supposed to. From the screenshot it appears that GreenHopper 5.9.1's Atlassian-Build-Date entry in the plugin manifest is March 22 or later (because that is what the license maintenance expiration is). bbaker, can you confirm?

My theory is that the GreenHopper version that comes bundled with JIRA 4.4.4 and JIRA 5.0 both have an Atlassian-Build-Date of something before the license maintenance expiration, whereas the GreenHopper that comes bundled with JIRA 5.0.1 does not.

Our plugin licenses are perpetual - you can keep using a plugin after the license has maintenance expired, however, you cannot update to a version newer than your maintenance expiration date. That is what the UPM plugin management screenshot is displaying.

jkodumal and bwoskow - I havent investigated this yet but I suspect strongly that this is a UPM 2.0 problem.

Can you guys independently look at this please.

Is this s consequence of the UPM 2.0 upgrade in 5.0.1?