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

The pe_puppetserver service when run with ipv6 and ipv4 binds tcp to tcp6, and does not serve the healthcheck endpoint correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Froyo
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      relates to https://tickets.puppetlabs.com/browse/SERVER-248

       

      Deployed Puppet server in Centos7 with active ipv6 and the servcies on 8140 bound to tcp6. 
      introduced the fix from https://tickets.puppetlabs.com/browse/SERVER-248,

      the fix from server-248 when run post deploy updated the config and restarts the service but left the helthcheck endpoint indeterminate 
      we fixed it with a reboot

      to reproduce:

      deploy compile master on centos 7 with ipv6, apply hiera data from server-248 and run puppet agent, puppet will update configuration but leave /v1/simple endpoint unresponsive

       

      Can we add the data to the default java args so has to ensure the service is always attached to the tcp4. 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              adam.buxton Adam Buxton
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support