Hi Kamil, 

No, We have upgraded from Jira 7.2.3. I don't think it's too older. 

Hi pragallapati_venkata_vara_prasad,
I've verified that Jira Software is properly included in 7.13.1 tar.gz package. Your problem might be related with the fact that you were upgrading from older Jira version. In this case I'd recommend raising a request in our Atlassian Support contact page  or in the Atlassian Community forum.

Hi Andrew,

We are also facing this problem after upgrading to 7.13.1. Do we have any fix? 

alex.comerford1204081651 This bug ticket is not really an appropriate place for your specific upgrade problem.   I'm certain that you are not actually seeing the same source problem in this bug, but rather another source cause that is preventing Jira Software from starting when Jira loads.   Instead I would invite you to create a post on Community, you can also go to https://support.atlassian.com/contact/

I can see that you appear to have a starter license for Jira, so support for those starter licenses are provided through our Community site at this time.

I am having this issue after updating to 7.9.0. Please can you help? I have attached the logs here 

Hello helder.tavares.silva287858558

In order to upgrade to 7.2.6 you need to have a license valid at least until the 7th of Dec (7.2.6 was released then)
However, I'm sure that something can be arranged. Can you send me your licence number, my email is: pfarid@atlassian.com

Hi Pawel,

Can I safely install the 7.2.6 version, despite our license expired at 30 November?

I am still having this problem in my dev environment with JIRA Core 7.2.6. I am not able to upgrade it from 7.2.1

Hi all,

We have reached out to all the affected customers via email.
All customers that downloaded 7.2.5 and had license issues that didn't allow them to upgrade to 7.2.6 can now do so.

If you are still witnessing any problems please let us know.

Thank you for your patience.

-
Cheers,
Pawel Farid
JIRA Dev Manager

Hi all,

We’ve just released a new version of JIRA Software Server v7.2.6, and we recommend all customers to install this version. For customers who are having license issues, we’re still working on a resolution, that’s why we are not closing this ticket yet. We will reach out to all impacted customers as soon as we resolve this problem. 

We appreciate your patience and apologize for any inconvenience.

-

Cheers,
Pawel Farid
JIRA Dev Manager

@Andre, see the Workaround section of this ticket. You can install the 7.2.4 version as is compatible with the 7.2.5 one.

Is there any ETA for 7.2.6 (or 7.2.5.1?) release which fixes this issue? There seems to be a number of customers left with partially functioning 7.2.5 who have to make a decision whether to downgrade or wait for the next release. It'd help to know whether we expect to wait for another couple of days or another month.

Some customers also have production freeze during the holidays and if not actioned this/next week, it could be another month until they can make any changes to the environment.

helder.tavares.silva287858558  I also made the upgrade around the middle of November and had a problem as described in this issue.  I followed a WorkAround found on answers Atlassian and I was able to get back online after deleting a jira-software-plugin.jar and uploading a new jira-software-plugin add-on orb with a URL to version on the Atlassian site.  The orb installed and when I restarted it was working fine.  

I am also receiving the warning "This version of JIRA is unrecognized by the Atlassian Marketplace. It might be a non-standard build or be too new to appear." and I would like a solution since our support period is expiring.

Thank you all for your feedback.

Hi everyone,

We are aware of the license issue you are having and working on a fix. We will let you know as soon as the fix is available. We apologize for any inconvenience this may cause you in the meantime.

–
Cheers,
Ignat
JIRA Bugmaster

Well, as I said, at least you can download add-ons from the marketplace and install them manually. Its not fun but you got a workaround if they don't give you the update!

Francis, but since your license is still valid enough time to be entitled to updates. So we a new version is released you can update to that version and your problem is solved.

My company license is due today, so any future releases can not be installed, leaving us with a "broken" version of Jira.

I got this problem and it when away when I bought a licence but now im stuck with the same problem as Helder : "This version of JIRA is unrecognized by the Atlassian Marketplace. It might be a non-standard build or be too new to appear." 

But I can still download plugins from the markteplace website and install them manually.

So if you navigate to Cog Icon -> Applications everything is normal?

Then you are in a far better situation because we cannot access our previously created issues in Software projects...

Atlassian should make availalbe the next update since this is crucial to continue business.

Best,

G.

@Georgios. I've made the upgrade around the 18th of November and did not have the problems described in this ticket.

But now I have the warning "This version of JIRA is unrecognized by the Atlassian Marketplace. It might be a non-standard build or be too new to appear." and I would like a solution since our support period is expiring.

This just reinforced that I should not update applications as soon as an update is released

@Helder Silva

What do you mean by "Upgraded and had no problems"??

Do you face the problem or not?

@Atlassian

Helder has asked an excellent question. What about those that there support license expires soon? Will they be entitled to the upgrade?

We are in a similar situation...Not expiring today but in the next 20 days.

Regards,

G.

Upgraded and had no problems. But I have a question regarding support.

It seems that downgrading at this point is not an option and we have our support license expiring today, so are we going to be entitled to at least an upgrade to the next version (7.2.6 or 7.3)?

So,

 what is the best way to treat this? Is it better to wait for 7.2.6 or is it better to perform the previously mentioned workarounds?

When is 7.2.6 expected to be released?

What about installing directly 7.2.4 on an affected system? Is it safe to do so or more problems could rise?

Best,

G.

joachim1569058516, 

Thanks for your comment. We are using all available considerations in making these calls. I appreciate you can advise the customers on this situation and that you were able to circumvent the issue. 

We did not find restarting JIRA Service on a Windows system to solve the problem in all circumstances. 

Leaving the 7.2.5 active on marketplace would cause other user's systems to request them to upgrade to that version. Since the 7.2.5 had the installation problems outlined above, we do not want other users to run into these problems.

I hope it makes things a bit more clearer, thank you for your patience.
Łukasz Włodarczyk, JIRA Release Manager

mark.finta709948468,

Thanks for the question, hopefully I can clarify things for you.

JIRA does not support data downgrades. If you have installed a new version of JIRA the upgrade tasks have  upgraded your data to the new version that is incompatible with the old version.

Your best bet is to restore the old data from a backup, which is the recommended best practice when performing upgrades. You can find a lot more detailed information in the upgrade documentation.

There is a good chance that a 7.2.x version is still compatible with your upgraded data. If you want to hold off until 7.2.6 is out, I'd recommend installing 7.2.4 instead.

Again, I apologise for the inconvenience we caused by pulling this release.

Please don't hesitate to reach out to support if you need further assistance.

@Lukasz Wlodarczyk

Do to this bug and figuring out there are API changes, we would like to perform a rollback to 7.1.9 until 7.2.6 gets released.  What is the process for being able to make this happen?  Am I allowed to just run a 7.1.9 installer on top of a 7.2.5 install?

I recently installed JIRA 7.2.5 and encountered the same problem. The message was along the lines of "JIRA software installed but not running". A simple restart of the JIRA Service (Windows) solved the problem. As for the procedure: I believe cancelling a release and subsequently removing the possibility to use the Marketplace is not acceptable. I have no real production instance running but I am evaluating the software for a customer. If this can happen any time - and apparently it can (V7.0.7) - this casts a cloud (no pun intended) over my otherwise very good impressions.

I upgraded from 6.3.14 through 7.0.0, with last step upgraded using just JIRA Core installer - Agile and JSD were installed from obr files (I wanted to be sure about installed versions, auto-updater cannot be trusted this far). This confirms the workaround, and I did not observe wrong behavior.

However, version 7.2.5 is not fully usable since cancellation. because it's not recognized by Marketplace.

Done too, then the service desk plugin update started and was completed fine.

i had that problem too but i just shutdown JIRA remove the plugin-cache, restared jira and then it works.

i updated JIRA from version 6.4.1-standalone to first jira7-installer and the to version 7.2.5-installer

Hi rmota@vsc-technologies.com,

Unfortunately a side effect of us withdrawing the JIRA 7.2.5 releases is, as you rightly pointed out, if you successfully upgraded to JIRA Software 7.2.5, UPM now can't find the related OBR for JIRA Software on Marketplace and so will display an error. JIRA Software should still work fine. If you have any another combination of JIRA such as JIRA Core 7.2.5 or Service Desk 3.2.5, you'll also find that UPM can no longer find the correct information for these, and this will result in UPM showing errors. They should also still be working fine as these builds did not contain any errors.

If they're not working, or if you've unsuccessfully tried to upgrade to JIRA Software 7.2.5 and you're having issues, please contact our support team so they can further assist you.

We're working hard to release JIRA Software 7.2.6 ASAP, and apologise for the inconvenience.

Thanks,

Warren Thompson, JIRA 

Hi,

We have updated our JIRA servers on 7.2.5 yesterday (without installer), and today, we can see your cancellation.

But we can see today on JIRA addons page a banner, upm failed to apdate, we can no more find new addon to upload from marketplace.

We are out of work hours. This is seriously bad.

Regards

Hi all,

We have withdrawn the 7.2.5 release, and 7.2.6 will be released as soon as possible.

The root cause for this issue was an error in our build system introduced in resolving JRA-62713. Our test regimes for installers didn't catch the corrupted installers either. There were otherwise no software errors in the 7.2.5 release. If you managed to successfully install it using one of the above mentioned workarounds, it is still a supported version. Please read on for a detailed explanation.

The build system that was modified to properly produce the source distribution for JIRA Software (JRA-62713) caused a malformed JIRA Software Application plugin to be bundled in the installers, but the subtle nature of the bug caused the marketplace distribution to be correct.

Our test regimes extensively test the JIRA Software functionality prior to the final release builds. At this point, we run the installers and check if the plugins that make up the JIRA Software product are present in the system after the installation. In this particular case, all the required plugins were installed and enabled in the system, but the aggregate application level information was corrupt. The result was that we didn't catch the faulty repackaging of JIRA Software because of a flaw in our tests, and the subtle nature of the error.

To avoid causing another embarrassing situation like this, we're taking the following actions right now:

1. We will tighten the testing to perform more detailed checks on the system composition (extra rigourous checks for the correct integration of the JIRA Software Application plugin).
2. We are developing alternative approaches to producing the source distribution, because of the issue that we encountered we are putting more work into more controllable processes. Source distributions are tricky things, and they need to be tested internally (replicating the situation whereby we wouldn't have intranet-level access to everything) to make sure you can do the same.
3. No pizza or soda for a month for the guilty devs. That'll teach 'em.
4. Our integration testing works by pulling JIRA and the application obr together, so at the integration level we didn't notice things were breaking if the installers were used. So to tighten up the "plugin system composition" tests, we're adding extra test regimes that will perform user level interactions with systems installed from the installer packages, targeted at specific core functionality that these installers provide.

I hope this makes things clearer, and we're truly sorry for any inconvenience caused. We always aim to ship world class products, but sometimes we miss the mark.

Thanks for your time,
Łukasz Włodarczyk, JIRA release manager

I have verified that it is indeed the faulty jira-software-application-7.2.5.jar file shipped with the tar.gz installation archive that causes this issue.

I tried doing a clean install again, but before starting JIRA I replaced jira-software-application-7.2.5.jar (in atlassian-jira/WEB-INF/application-installation/jira-software-application) with the corresponding file from the obr. This causes the install to work flawlessly. I think the jira-software-application-7.2.5.jar file shipped with the tar.gz installation archive is corrupt (see my earlier post).

This is how I got the workaround to work.

1. Upgrade to JIRA using the .exe.  It will work except it may error with the JIRA Software part in the Cog -> Applications -> Version & licenses. If this happens (like it probably has for most everyone that came to this ticket) continue on.
2. Stop JIRA
3. Go to the installed-plugins folder within the Home Directory -> Plugins folder and move all the .jar files that begin with jira-software and jira-greenhopper to another folder outside of the installed-plugins folder
4. Restart JIRA
5. Go back to the Cog -> Applications -> Version & licenses and select Upload an Application.
6. In there select the .obr file that you download from here: https://marketplace.atlassian.com/plugins/com.atlassian.jira.jira-software-application/versions
7. This should complete in full without error.
8. Restart JIRA one more time.  The reason to do this is because the error may return even though it says the install was successful.  This fixed that problem for me.
9. Obviously if something else happens that is outside of these steps then contact Atlassian support so they can help you out.

@Mark Finta: I had the same issue, I was pretty confused because there was a JIRA Software Application add-on, I tried to enable it and later disable it.

The solution to make the workaround work was to

• disable the add-on,
• allow JIRA to access the internet (added proxy setting in bin/setenv.sh - no idea if this was relevant for the solution),
• install the obr-file through Cog icon -> Applications -> Versions & licenses -> Upload an application and then
• restart the JIRA instance.

I have to say that this is an absolute nightmare from Atlassian - again. This version was online for one week. I almost never had an upgrade without major issues.

The .obr file that is considered part of the workaround is not a sure fire fix.  I don't know if this is the case for everyone, but it errors out with this error message when attempting to upload an application and point it at the .obr file: "An unexpected error occurred. Refer to the logs for more information"

In the logs it was giving this message.

2016-11-22 13:12:38,946 UpmAsynchronousTaskManager:thread-1 WARN 079928 792x116x1 qx8a1f 10.3.78.46 /rest/plugins/1.0/ [c.a.plugin.impl.AbstractPlugin] Unable to install plugin 'com.atlassian.jira.jira-software-application'.
com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to install bundle

Similar problems:
https://answers.atlassian.com/questions/32114176/jira-software-is-not-installed-after-upgrading-to-jira-7
https://answers.atlassian.com/questions/34637912/jira-software-is-licensed-but-not-currently-installed-after-upgrade

It seems that the version of the application from the Marketplace has different binaries than the ones distributed with the atlassian-jira-software-7.2.5.tar.gz installer. The jira-software-application-7.2.5.jar file in the obr installer contains more files (images folder and atlassian-plugin.xml). I suspect this is what is causing the default install to fail.