Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2097

Disable dujour checkins for Puppet Server during CI runs

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 3.2.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2
    • Sprint:
      PuppetDB 2015-11-18

      Description

      Analyzing the dujour data for Puppet Server, we are starting to suspect that it is being artificially inflated by checkins from PuppetDB CI tests in AWS.

      In various CI jobs we've solved this in the beaker pre-suites by either setting a bunk entry for the dujour hostname in /etc/hosts, or by configuring the TK dujour client with a bunk server hostname.

      I believe that other teams that are using Puppet Server in their CI already have something like this in their pre-suites, but it's less of an issue for the other projects anyway because their tests run on our internal hardware, meaning that the dujour checkins would all share a small number of remote IP addresses and those are easy to filter out if some accidentally slip through. It's a much bigger problem with PuppetDB since the CI jobs are running in AWS; we have no way of differentiating between "real" AWS checkins and PuppetDB CI checkins.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                chris Chris Price
                QA Contact:
                Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support