Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7524

Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • PUP 4.10.0
    • None
    • None
    • None

    • Puppet 4.10, Centos7

      • AIO comes with supported ruby version (2.4)
      • All tests are ok (including hiera5)
    • Needs Assessment

    Description

      As posted here https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/ Ruby has EOL'd at 1.4.2017. So no more security fixes for included AIO Ruby 

      root@SERVER # puppet -V
      		 
      4.10.0
      		 
      root@SERVER # /opt/puppetlabs/puppet/bin/ruby -v
      		 
      ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux]

      Attachments

        Issue Links

          duplicates

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PA-476 Update puppet-agent to use Ruby 2.4

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PUP-6893 Remove Ruby 1.9.3 support

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. PUP-7038 Deprecate ruby 2.0.0 support

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          links to

          Web Link Ruby 2.1.0 EOL statement

          Web Link Ruby branches and branch status

          Activity

            People

              Unassigned Unassigned
              elconas Robert Heinzmann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support