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

In 2.x only do CRL reload if FS watcher service is present

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: SERVER 2.8.0
    • Component/s: None
    • Labels:
      None
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      No Action

      Description

      The trapperkeeper watch service was intentionally not shipped/supported on Java 7 due to bugginess and instability of the underlying java file watcher library on that platform. When the CRL reload functionality was added to puppetserver 2.x and trapperkeeper-webserver-jetty9 in TK-149, it was with the intent to support a feature required in puppet enterprise, with ships with Java 8. However, the implication of shipping the feature in puppetserver 2.x is that it can/will be installed on environments running Java 7, as java 7 has been supported through the 2.x series. Only in puppetserver 5 is support for java 7 dropped.

      We have already seen test failures running the new crl reload functionality against java 7.

      The proposed solution is to only leverage the CRL reload functionality by default in PE for the server 2.x series, where we know Java 8 is present. We will do so by conditionally loading based on the presence of the trapper keeper watch service, and then not adding this service to the FOSS 2.x bootstrap config by default. Documentation should note that FOSS users of 2.x running java 8 can enable the functionality by adding the trapperkeeper watch service to their bootstrap config.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                moses Moses Mendoza
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support