Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.0.0
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server 2015-02-04, Server Jade 2015-04-15, Server Jade 2015-03-04, Server Jade 2015-03-18, Server Jade 2015-04-01, Server Jade 2015-04-29, Server Jade 2015-05-13

      Description

      Currently, we are generating the 404 upgrade message laid out in SERVER-148 every time a route that should get that error message is handled. Generating this includes grabbing the Puppet Version through JRuby, which is an expensive operation. This should be moved into startup and done once.
      ___
      Risk assessment: Medium (Devs believe there is a strong chance this will regress. QA to perform FR and to make an automated test.)
      Probability: High (code runs at every puppetserver service start operation)
      Severity: Low

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                erik Erik Dasher
                Reporter:
                preben Preben Ingvaldsen
                QA Contact:
                Erik Dasher
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support