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

File name missing in puppet-master error message about Forbidden request:

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.8.5
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
    • Template:
    • Team:
      Platform Core

      Description

      On my puppetmaster I have a few things configured in /etc/puppet/auth.conf for file serving, now I accidently applied wrong profile to a node, and that was not allowed to access some files.

      I found (expected) error messages like this in the logs:

      Jan 23 22:55:22 galen puppet-master[20]: Denying access: Forbidden request: erewon.example.com(2001:470:1234::44) access to /file_metadata/puppet_ssl_private_keys/user.pem [find] authenticated at :98
      Jan 23 22:55:22 galen puppet-master[20]: Forbidden request: erewon.example.com(2001:470:1234::44) access to /file_metadata/puppet_ssl_private_keys/user.pem [find] authenticated at :98

      there is a minor " " space to much, between "authenticated at", and then only the line of the file is given, but not the file name.

      There I have a few things configured in /etc/puppet/auth.conf for file serviing, now I accidently applied wrong profile to a node, and that was not allowed to access some files.

      looking at line 65 in
      /usr/local/lib/ruby/site_ruby/2.2/puppet/network/rights.rb
      I see where the extra space comes from, but I don't see, where it gets called from, where the missing information about the file is not fed in.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            buzzdeee Sebastian Reitenbach
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support