Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Plugin updates via UPM fail in Jira server

shiming yan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 4, 2019

I can install only Jira-Core or Jira-Core+Jira-Software or Jira-Core+ServiceDesk in one instance,but I can't install them together. When I installed Jira-Core+Jira-Software,I try to install the Jira-ServiceDesk by Jira-Software application manager(settings>application>version and license) page.At right of this page have a button named try free to install the Jira-ServiceDesk.But whenever I click it ,the page always appear a tips window to tell me :"An unexpected error occurred. Refer to the logs for more information.".Then I find the error in logs,the error is follow:

2017-10-17 15:32:19,181 UpmAsynchronousTaskManager:thread-3 ERROR admin 932x75x3 1b3k4i7 10.60.2.117 /rest/plugins/1.0/ [c.a.u.c.r.resources.install.InstallFromUriTask] 
Error downloading plugin from https://marketplace.atlassian.com/download/plugins/com.atlassian.support.stp/version/3010042
2017-10-17 15:32:19,201 UpmAsynchronousTaskManager:thread-4 ERROR admin 932x79x2 1b3k4i7 10.60.2.117 /rest/plugins/1.0/ [c.a.u.c.r.resources.install.InstallFromUriTask] 
Error downloading plugin from https://marketplace.atlassian.com/download/plugins/com.atlassian.support.stp/version/3010042
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

First the time is too different from now.It makes me wonder.But I do still find resolvent in community.I've only found one solution follow:

Plugin updates via UPM fail in Jira server

Remove -Djsse.enableSNIExtension=false and TLS protocol parameters lower than v1.2 via JIRA startup options, and restart the application.

But I'm not find -Djsse.enableSNIExtension=false in my setenv.sh

 

My environment is:

CentOS 7.6

Jira-Core 8.5.1

Jire-Software 8.5.1

 

What should I do now? Who can help me?

         Thanks a lot!

1 answer

1 accepted

0 votes
Answer accepted
Juan Du Toit
Contributor
October 28, 2014

So, answering my own question....yes it does remove it from the sprint.  That status has to be available somewhere on the Rapid board to recognise it as part of the sprint.

What I did was to ad the "Waiting for UAT deployment "status in the last column.  So all issues will have a resolution of Resolved but a status of Waiting for UAT deployment.   

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events