Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-406

Investigate ruby command not found failures

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
    • Template:
    • Epic Link:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server Emerald 2015-03-04, Server Emerald 2015-03-18

      Description

      List of failing acceptance tests related to ruby not on the PATH:

      • cve-2013-1654_sslv2_downgrade_agent.rb
      • ticket_6857_password-disclosure-when-changing-a-users-password.rb

      Note, this is failing in a preliminary run [1] that assumes QENG-1841 and PUP-4057 have both been merged and are being employed by puppet-server.

      [1]: https://jenkins.puppetlabs.com/view/Puppet%20Server/view/aio/job/experimental_puppet-server_integration-system_full-aio/3/

        Attachments

          Issue Links

          blocks

          Task - A task that needs to be done. SERVER-438 Produce puppetserver 2.0.0-rc2

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          is blocked by

          Task - A task that needs to be done. PUP-4056 Audit acceptance tests for assumed ruby location

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

          Task - A task that needs to be done. SERVER-400 Try beaker from pr/719

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

          Web Link Pull Request

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jeff Jeff McCune
              QA Contact:
              Erik Dasher
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support