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

PuppetDB Docker DNS lookup requirement may break CI

    Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PuppetDB
    • Labels:
    • Template:
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Recent changes to the PuppetDB Docker image adds a requirement on DNS resolution for Puppetserver and Consul hosts linked to the PuppetDB.

      This has had the unfortunate effect of breaking our CI pipeline. In the pipeline we spin up PostgreSQL, PuppetDB and Puppetserver in Gitlab CI. Because Gitlab CI doesn't provide a local DNS server for "services" we inject a hosts file into each of the parts of the system so each container can resolve the IP of the other containers.

      I've added some comments on https://github.com/puppetlabs/puppetdb/commit/0319e96c4d759bb419ec6e53c711538a0d1ff405#r33804010 , and a few other users have chimed in saying that the change also broke their CI.

      IMO the best solution is to provide a flag set by an environment variable to select whether or not DNS name resolution should be used. Using it by default is fine, as long as it's possible to disable it easily.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              runejuhl Rune Juhl Jacobsen
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Zendesk Support