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

Filebucket resources fail when using server_list

    Details

    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      For the filebucket type, `server` and `port` no longer have explicit default values in the type definition. If server is not set, it defaults to the first entry in `server_list` if set, or `server` otherwise. If port is not set, it defaults to the port in the first entry of `server_list` if set, or `masterport` otherwise.
      Show
      For the filebucket type, `server` and `port` no longer have explicit default values in the type definition. If server is not set, it defaults to the first entry in `server_list` if set, or `server` otherwise. If port is not set, it defaults to the port in the first entry of `server_list` if set, or `masterport` otherwise.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version:
      puppet --version
      5.5.2

      From Vadym Chepkov:

      It (PUP-6823) might have fixed filebucket command, but not filebucket resource
      with server setting removed as recommended here in step 4
      https://puppet.com/docs/pe/2018.1/configure_high_availability.html#enable-a-replica

      Error: Could not back up /etc/cron.d/yum-update: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
      Error: Could not back up /etc/cron.d/yum-update: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known)
      

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  melissa Melissa Stone
                  Reporter:
                  josh Josh Cooper
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support