Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71394

Fedora 38 end of life warning should not be visible until 2024

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 2.407 shows the issue on Fedora 38, no plugins required
    • 2.409, 2.401.2

      Originally filed as https://github.com/jenkins-infra/jenkins.io/issues/6431

      Expected behavior
      No warning shown.

      Actual behavior
      Page shows warnings about operating system support end of life:

      > Operating system end of life monitor
      > You are running Jenkins on Fedora Linux 38 (Cloud Edition). Jenkins stopped supporting Fedora Linux 38 (Cloud Edition) as of 2023-05-18.

      > Please upgrade to a supported operating system.

      The date should be 2024 according to https://endoflife.date/fedora

          [JENKINS-71394] Fedora 38 end of life warning should not be visible until 2024

          Kris Stern added a comment - - edited

          Note for LTS release: According to markwaite, the original source of the issue was from 2.407 and was not included in 2.401.1.

          In the blog post announcing the operating system end of life monitor, he said that LTS users would first see it in the next LTS baseline after 2.401. That would likely be 2.412.1 or 2.413.1 (which ever is chosen as the next LTS baseline).

          Kris Stern added a comment - - edited Note for LTS release : According to markwaite , the original source of the issue was from 2.407 and was not included in 2.401.1. In the blog post announcing the operating system end of life monitor, he said that LTS users would first see it in the next LTS baseline after 2.401. That would likely be 2.412.1 or 2.413.1 (which ever is chosen as the next LTS baseline).

          Mark Waite added a comment -

          Thanks krisstern for checking if this should be backported. I should have updated the "environment" section of the report to show that 2.407 was the first release with the bug. Now that the change has been merged, it is also the only release of Jenkins core with the bug.

          Mark Waite added a comment - Thanks krisstern for checking if this should be backported. I should have updated the "environment" section of the report to show that 2.407 was the first release with the bug. Now that the change has been merged, it is also the only release of Jenkins core with the bug.

          Kris Stern added a comment -

          You are welcome markewaite!

          Kris Stern added a comment - You are welcome markewaite !

          Kris Stern added a comment -

          Thanks markewaite for fixing the `Released As` label for us! I completely omitted to do this earlier. 

          Kris Stern added a comment - Thanks markewaite for fixing the `Released As` label for us! I completely omitted to do this earlier. 

            Unassigned Unassigned
            zbynek Zbynek Konecny
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: