Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10648

puppet 6 agent doesn't honor usecacheonfailure setting when using server_list

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • PUP 6.17.0, PUP 6.18.0
    • PUP 7.0.0, PUP 6.19.0
    • None
    • Other
    • Other
    • Night's Watch
    • 2
    • NW - 2020-10-14
    • Needs Assessment
    • Bug Fix
    • Hide
      Previously, when server_list is used while no server is accessible puppet run will fail even if usecacheonfailure is set to true.

      After this commit, when server_list is used while no server is accessible puppet will use cached catalog if usecacheonfailure is set to true and fail only if usecacheonfailure is set to false
      Show
      Previously, when server_list is used while no server is accessible puppet run will fail even if usecacheonfailure is set to true. After this commit, when server_list is used while no server is accessible puppet will use cached catalog if usecacheonfailure is set to true and fail only if usecacheonfailure is set to false
    • Needs Assessment

    Description

      Puppet Version: 6.17.0 (PE2019.8.1)
      Puppet Server Version:  2019.8.0.37
      OS Name/Version: RHEL8

      Had a case where /etc/resolv.conf was accidentally removed and puppet agent hasn't recovered it for unknown reason.  usecacheonfailure is set to true

       

       

      Easy to reproduce, manage /etc/resolv.conf by puppet, remove the file, puppet agent will start failing and not recovering the file. The log entry :

       

      Could not run Puppet configuration client: Could not select a functional puppet master from server_list:

       

      Attachments

        Issue Links

          Activity

            People

              ciprian.badescu Ciprian Badescu
              vchepkov Vadym Chepkov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support