Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-14934

jenkins agent aws instances need manual intervention after reboot

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:
      None
    • Templates:
    • Story Points:
      0.75
    • Epic Link:
    • Team:
      SQuaRE

      Description

      The jenkins "swarm" client must use DNS based discovery of the master as multicast is not support on aws (or most public clouds). Presently, an /etc/hosts entry is injected by puppet during configuration but this is lost as a reboot because it is overwritten by cloud-init. Forcing the hostname via cloud-init is needed as aws seems to lack a way to set a hostname via dhcp options (custom magic could probably use the metadata service).

      A local /etc/hosts entry could be avoided by using a vpc private route53 zone, which is straight forward to setup via tf.

        Attachments

          Activity

            People

            • Assignee:
              jhoblitt Joshua Hoblitt
              Reporter:
              jhoblitt Joshua Hoblitt
              Reviewers:
              Joshua Hoblitt
              Watchers:
              Adam Thornton, Frossie Economou, Joshua Hoblitt
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel