[issues.jenkins.io] Jira - "The End of Life health check has failed in your system."

[dduportal]

Service(s)

Jira

Summary

The Jira instance at issues.jenkins.io which hosts most of the Jenkins project issues show a message (when authenticated) The End of Life health check has failed in your system.

We are curently using the version 8.13 of Jira, which end of life is in october 2022.
8.13.x baseline is the "previous LTS" as per https://confluence.atlassian.com/enterprise/long-term-support-releases-948227420.html

We should plan an upgrade to 8.20 (current LTS) which end of life is ocotber 2023 - https://confluence.atlassian.com/jirasoftware/jira-software-8-20-x-release-notes-1086411771.html.

This Jira instance is hosted by the Linux foundation : we have to

• Open a issue on their system to request the upgrade and decide, with them of a schedule
  • Usually morning in the US west coast (where their support/eng. team are), end of day in EU. But might be morning EU/afternoon Australia if they have a team there.
• Announce the maintenance to our users
  • On status.jenkins.io
  • On the mailing lists
  • On IRC/Gitter channels (#jenkins-infra , jenkins/jenkinsci at least)
  • On other social media (ping @jmMeessen @MarkEWaite )?
• Ensure the maintenance is performed by them and successful
• Close the maintenance windows

Reproduction steps

No response

[MarkEWaite]

This needs to be reported to the Linux Foundation through the Linux Foundation Service Desk. Project services is the correct location to report it as a "Get IT help".

I have permissions to do that, but would love to have someone else confirm that they can also do it.

[timja]

s/JIRA/Jira 😉 , updated for you

[timja]

This needs to be reported to the Linux Foundation through the Linux Foundation Service Desk. Project services is the correct location to report it as a "Get IT help".

I have permissions to do that, but would love to have someone else confirm that they can also do it.

It's public anyone can create a ticket for it

[dduportal]

Thanks folks ❤️

Please note that the issue has been added to the milestone "infra-team-synx-next", which means we'll discuss this task and its allocation during the next infra meeting (would be 2022-04-12).

It means that there are no emergency to do it today (the EoL in 6 month).

[dduportal]

Issue opened at https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23874

[dduportal]

Issue is waiting from the LF teams:

I'll provide more updates once I hear from the team

Removing milestone until we have more news.

[dduportal]

We just got a few dates. Friday 22th of April sounds the most interesting: waiting for timing confirmation before communciating in email/status.jenkins.io/etc.

[dduportal]

Changed due to logistical delays. Should be done the 26th of April, 02:00pm PST (09:00pm UTC). Gotta update status.jenkins.io.

[timja]

@dduportal it was already upgraded on Friday?

I had to click a button when I logged in on Saturday to confirm some post upgrade thing.

see
https://confluence.atlassian.com/enterprise/long-term-support-releases-948227420.html
for current lts version

[dduportal]

OK, sounds like that the LF teams still proceeded last friday as per @timja comment (thanks!):

For the people involved next time: LF teams are using PST timezone.

[timja]

Yeah that's the screen I saw