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

"current thread not owner" after Puppet Agent receives USR1 signal

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: PUP 3.4.2, PUP 3.5.1, PUP 3.6.2
    • Fix Version/s: PUP 3.7.5, PUP 4.0.0
    • Component/s: Catalog Application
    • Environment:

      Ubuntu 12.04.2 LTS
      Ruby 2.0.0 (patchlevel 353)
      OR
      Ruby 2.1.0 (patchlevel 0)
      CentOS 7
      Ruby 2.0.0 (patchlevel 353)
      OR
      Debian jessie (2014-11-14)
      Ruby 2.1.4p265
      puppet 3.7.2-1

    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-03-04, Client 2015-03-18

      Description

      We're running the Puppet Agent daemonised, with splay enabled. We use the USR1 signal to trigger an immediate reload and catalog run, bypassing the splay setting.

      This works fine in our other Ruby environment (1.9.3, various patch levels), but when testing under Ruby 2.0.0 and 2.1.0, we noticed that the signal would cause the catalog run to fail due to the following errors:

      Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner
      Could not autoload puppet/feature/external_facts: current thread not owner
      Could not autoload puppet/indirector/node/rest: current thread not owner

      A restart of the daemon is required to recover from this.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rylon Ryan Conway
                QA Contact:
                John Duarte
              • Votes:
                9 Vote for this issue
                Watchers:
                18 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support